In short, Full Convert migrates tables, indexes, foreign keys and data.

Tables

• All datatypes are mapped to the closest matching datatype in target database. You can override mapping per-table in Customize Table dialog, or globally in our options
• Commonly used default values, like GETDATE(), are translated to equivalents in target database. Not all functions are translated.
• If source database is relational, you can use native SQL expressions to transform data on the fly. An example would be0: trim(first_name + ' ' + last_name)

Indexes

• We migrate primary keys, unique indexes, all standard indexes (except currently for Paradox, where only PKs are converted)
• Multi-column indexes are fully supported
• Descending indexes are supported

Foreign keys

• Relationships between tables (foreign keys) are fully supported
• If you start getting unexpected errors in foreign keys migration:
• Check that your source data conforms to FKs
• If source database is case-sensitive, you probably have target with case-insensitive collation. Fix that.

Data

• We support tables of literally unlimited size. Hundreds of millions of records. Hundreds of gigabytes. Our customers proved that many times. For such huge tables we require that they have primary or unique key defined if source database is relational.
• BLOB and memo fields are fully supported
• We take advantage of BULK inserts, LOAD, Oracle fast loader and all other available speedup methods to achieve as fast conversion as possible, with no risk of data corruption
• We achieved data throughput of more than 30 thousand records per second in internal testing