Documentation & Help

Supported database pairs, known limitations, and migration guides

Stored Procedures & Triggers

Converted using deterministic rule-based rewrites. Complex logic may still require manual review and targeted SQL adjustments.

Views

Parsed and converted for every SQL target, in dependency order — names, string concatenation (with the source's NULL handling) and date functions are rewritten per engine, and certification compares each migrated view's rows with the source's. A view that cannot be expressed on the target is not created; it is listed for manual review with the reason.

ENUM / SET types

MySQL ENUM → TEXT with CHECK constraint or CREATE TYPE (PostgreSQL). SET → TEXT[] (PostgreSQL) or TEXT (others). Type enforcement may be weaker.

Geospatial types

MySQL GEOMETRY/POINT → PostGIS geography or GEOGRAPHY (SQL Server). Oracle SDO_GEOMETRY maps to TEXT in non-Oracle targets.

Auto-increment / Sequences

Auto-converted between SERIAL (PG), AUTO_INCREMENT (MySQL), IDENTITY (SQL Server). Sequence values are reset post-migration.

Binary / BLOB data

BLOB → BYTEA (PG), VARBINARY(MAX) (SQL Server), LONGBLOB (MySQL from other engines), BLOB (Oracle). Copied byte for byte — every byte value, invalid UTF-8, empty values and 1 MB values are certified on every SQL pair. Oracle cannot store a zero-length binary value, so an empty value becomes NULL there.

MongoDB schemas

Schema is inferred by sampling documents. Nested objects → JSONB/JSON. Arrays → JSON. ObjectId → VARCHAR(24). Some structure may be lost.

Character sets & Collation

Collation mapping is best-effort. UTF-8 is used as default for targets. Special collations (e.g., Turkish, Japanese) may need manual configuration.

Foreign Key circular dependencies

Detected automatically. FK constraints are deferred until after data load. Circular dependencies are resolved via dependency-order analysis.

Large databases (>1M rows)

Dynamic batch sizing adjusts per table. Tables with BLOB columns use streaming. Parallel migration for independent tables. Memory monitoring throttles on pressure.

Need more help? Use the migration guides or the error reference, or contact your workspace administrator for support.