That said, many people will want to at least try a straight conversion. Many companies invest in creating an entirely new database and only move the data from the old database into the new solution. Taking advantage on these new features such as multiple tables in one file, new security, and fully relational capabilities is called database migration and can be a much more costly proposition. Straight conversion of the files may be relatively simple, but it doesn’t guarantee the database will retain all the functionality it originally had…and it certainly won’t be optimized for using any of the new features available. So, if you have an old format database what do you do? Modern versions of Mac OS (after 10.6 Snow Leopard), no longer support running FileMaker 6 or earlier…and so this is forcing these databases to be brought into the newer file formats just to be operational.

fmp12 and we expect that format will last for many more years to come. The current FileMaker database file format is. Version 7 was good until the release of FileMaker 12 in 2012. In 2004, FileMaker completely rewrote FileMaker with version 7 and changed the file format to. fp5 (Version 5 of FileMaker) but this file format lasted through FileMaker version 6. We’re finding that there are still several organizations using FileMaker databases that were created many years ago with the old version of FileMaker. See our latest updated process for migrating your FileMaker database to the latest version of Claris FileMaker here.

Filemaker fmp12