| FmPro Migrator - FileMaker Pro Advanced 19 Compatibility |
| Feature |
Status |
| FileMaker 20 Data Conversion |
Supported |
| FileMaker 20 Table Consolidation |
Supported |
| Microsoft Access to FileMaker 20 Conversion |
Supported |
| Visual FoxPro to FileMaker 20 Conversion |
Supported |
| FileMaker 20 to PHP Conversion |
Supported |
| FileMaker 20 to LiveCode Conversion |
Supported |
| FileMaker 20 to Access Conversion |
Supported |
| FileMaker 20 to Servoy Conversion |
Not Supported |
| FileMaker 20 to .NET Conversion |
Supported |
| |
|
Oracle Platforms Supported: All
Oracle Versions Supported: 8.0.5,8.1.5, 8.1.6, 8.1.7, 9.0.1,9.2.0,10g,11g,12c
MySQL Platforms Supported: All
MySQL Versions Supported: 3.23.50 - 5.7 [MySQL 8 is not currently supported.]
MariaDB 11
FileMaker 2.1, 3.0, 4.0, 5.0, 5.5, 6.0, 7.0, 8.0, 8.5,
9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20 are supported on macOS and Windows.
Due to the lack of a FileMaker 5/5.5/6.0 ODBC driver for
Mac OS X, the transfer of data between FileMaker and other databases
requires either running FmPro Migrator on a Windows computer (or Parallels/VMWare
onmacOS) or converting the older FileMaker files to FileMaker 7+..
FileMaker 7-13 now includse a FileMaker ODBC driver which makes the
direct transfer of data possible from macOS to other databases. [It is recommended that FileMaker Pro Advanced be used for gathering Table/Field info - but it is not required. FmPro Migrator can gather more info about Summary & Calculation fields when using FileMaker Pro Advanced. You may also consider the FmPro
Migration Service.]
Note: For extraction of images from FileMaker Pro 7
container fields, an upgrade may be required to FileMaker Pro 13+
for full functionality. The Image Export SQL feature is included with FmPro Migrator Platinum Edtion.
FileMaker 5.0/5.5/6.0 can be accessed via ODBC from FmPro Migrator on
Windows even if FileMaker 5.0/5.5/6.0 is running on macOS as long
as the Remote Data Access Companion is enabled.
FileMaker Pro Server does not support ODBC data transfer.
This feature is available with FileMaker Pro 6 Unlimited, desktop editions
and FileMaker Server Advanced 7+.
macOS 10.12+ - FmPro Migrator for macOS
Windows Windows 7/Windows 8/Windows 10/Windows 11- FmPro Migrator for Windows
Access Platforms Supported: Windows
Access Versions Supported: Access 97 and higher
Note: The Actual Technologies Access ODBC driver is a Read-Only driver.
Therefore it is necessary to run FmPro Migrator on Windows when converting
to Access, as the data needs to be written into the Access .mdb database
file.
Bento Platforms Supported: None - [Feature Removed]
SQL Server Platforms Supported: Windows
SQL Server Versions Supported: 6.5, 7, 2000, 2005, 2008, 2012, 2017, 2019
Sybase Platforms Supported: All
Sybase Versions Supported: 11 and higher
DB2 Platforms Supported: All
DB2 Versions Supported: 8.1
PostgreSQL Platforms Supported: All
PostgreSQL Versions Support: 9.x+
Lotus Approach (All)
[Import data into Microsoft Access, then transfer the data from Access using FmPro Migrator.]
FileMaker Table Consolidation - Requires FmPro Migrator
Developer Edition and FileMaker Pro Advanced 11 - 20, FileMaker Pro 19 [includes Advanced features]
FmPro Migrator Developer Edition for macOS uses the automation
features of AppleScript.
FmPro Migrator Developer Edition for Windows uses the automation
features of a compiled WinAutomation job file [provided at no cost].
Access to FileMaker 11+ migration [Windows and macOS]
On macOS, the Actual
Technologies Actual ODBC Driver for Access needs to be used (purchased
separately). But usually you will perform the data conversion on Windows first, then bring the file over to macOS for the GUI conversion.]
Firebird to FileMaker 11+ migration [Windows and macOS. On macOS,
a Firebird ODBC driver needs to be used (purchased separately). On Windows,
the free open source Firebird
ODBC driver can be used.]
SQL Server to FileMaker 11+ migration [Windows and macOS. On macOS, the Actual Technologies
SQL Server ODBC Driver needs to be used (purchased separately).]
