Convert MySQL to dBase

Making migration easy for you

Full Convert is a fully self-tuning software. Your migration will work as expected without you needing to adjust anything.

Data types are different in dBase compared to MySQL. We automatically adjust them as we copy the tables so you don't have to worry about it. You can adjust the mapping rules if you wish to change the following defaults:

• bigint numeric(20)
• bigint unsigned numeric(20)
• binary varbinary(10) (if version is 3)
• binary varbinary(4) (if version is vfp)
• bit logical(1)
• datetime date(8) (if version is 3)
• decimal numeric
• enum char(255)
• float double(8)
• geography text(10)
• geometry text(10)
• int integer
• int unsigned integer(4)
• json text(10) (if version is 3)
• json text(4) (if version is vfp)
• longblob varbinary(10) (if version is 3)
• longblob varbinary(4) (if version is vfp)
• longtext text(10) (if version is 3)
• longtext text(4) (if version is vfp)
• mediumblob varbinary(10) (if version is 3)
• mediumblob varbinary(4) (if version is vfp)
• mediumint integer(4)
• mediumint unsigned integer(4)
• mediumtext text(10) (if version is 3)
• mediumtext text(4) (if version is vfp)
• nchar char
• nvarchar char
• set char(255)
• smallint integer(4)
• smallint unsigned integer(4)
• time char(5) (if version is 3)
• time datetime(8) (if version is vfp)
• timestamp date(8) (if version is 3)
• timestamp datetime(8) (if version is vfp)
• tinyblob varbinary(10) (if version is 3)
• tinyblob varbinary(4) (if version is vfp)
• tinyint integer(4)
• tinyint unsigned integer(4)
• tinytext text(10) (if version is 3)
• tinytext text(4) (if version is vfp)
• varchar char
• year integer(4)