The SQLyog Migration Tool as of SQLyog 4.1 and later will import

DATA

and it will - of course - create the type definitions for the table columns in the process. Note that the ODBC-driver will 'propose' a transformation of the datatype when importing a datatype from the ODBC-database if the corresponding MySQL datatype is not completely identical. For instance a MS SQL Server varchar-type is too long to fit into a MySQL 4.x varchar. It must be transformed to a MySQL text or blob type. However the SQLyog Migration Tool gives you the option to 'override' the 'proposal' of the ODBC-driver. So for instance: if the driver says blob you can choose mediumtext instead if you like.

METADATA that is

• (ordinary) indexes, including – of course – unique indexes
• primary keys
• foreign keys

It does not attempt to import

OBJECTS such as

• Stored Procedures and Functions
  
• Triggers
• Views

Also note that the ODBC-import Tool as of SQLyog version 4.0 and before only imports DATA themselves.