With this new tool from FileMaker, once development is complete in the Dev copy of the file and the developer is ready to migrate the data, he or she can use FileMaker’s tool to migrate the data more quickly and easily. Until the introduction of FileMaker’s new FM Data Migration Tool, developers had to manually import data from one file to another table by table - a long, laborious, potentially error-prone, and certainly time-consuming process. You can then migrate all of the current and up-to-date data in the live file to the fresh clone of the Dev file.Īfter the live file data is imported into the cloned file - it now becomes the new live life file and can be put on the production server. This clone will include all of the schema updates from the dev copy but none of the old, outdated data. Once development is complete and it is time to 'go live' with the latest schema changes, you need to then clone the Dev file. You can use this copied file as the development (Dev) copy for your scripting work and schema modifications.

This copy includes all the data from the live file.

Here's how the development process works:īefore doing development on an existing company file, you, the developer, need to make a copy of the live file where the data entry is being done. NOTE: the FM Data Migration Assistant is now compatible with FileMaker 19 and macOS 10.15 Catalina. Developers will need to download this tool before they can use our free FM Data Migration Assistant.

The FileMaker Data Migration tool is available through the FileMaker Developer Subscription and to FBA members.

Chief among these new tools was the FM Data Migration Tool, which helps developers import data from one FileMaker file to another. When FileMaker 17 was released it came with a bevy of new development tools and features.

Filemaker pro cloud migration