You can't directly export FileMaker DB structure/schema to anything except a DDR.
sorry but what is a DDR?
Database Design Report.
An HTML or XML expression of the schema.
This will not allow you to import or create the schema for MySQL. MySQL accepts: .csv (with columns) or .sql There is no direct method to create the .sql in FileMaker
While this file is basically TEXT, there is no "export as sql" from FileMaker. The file could (in theory) could be created with FileMaker functions. It would contain the calls to create the tables and columns and include INSERTs to push the data. No summary or calculation or container fields would transfer to the text. Summary and calculation fields in FileMaker could be evaluated equivalents at the time of export.
However, even as MySQL DBA, I never attempted this. It can be a fairly complex document and prone to errors. I always exported from FM as .mer (merge) so that the top row was the column/field names. Change the export extension to .csv and MySQL will import just fine. Specify comma as the delimiter between columns and the double-quote as the separator for text upon import into MySQL.
CAVEATS: (other than the types of fields)
- the naming of tables and columns may not be as lenient in MySQL as in FileMaker.
- the length of some of the data may be excessive
- the data types (int, float, dates, etc.) may be difficult to convert or incorrect for your usage
- there is no direct relationship building, although you can assign primary and foreign keys.
In theory it's also possible to export each table as XML and using XSLT to transform into the TEXT of a .sql, but i wouldn't do this either!
I'm not saying don't do this, I'm saying be very careful!!
But the DDR definitely will NOT help you create and insert into MySQL!
There is a tool called FmPro migrator, but the only person I know who used it did not like it much. I think the fastest approach would be just manually recreating the table structure.