HOW DO YOU MIGRATE? FileMaker Migration Assistant Tool vs. Manual: Best Practices to Migrate Changes to a Live FileMaker Server | 360Works

In the past, FileMaker developers haven't had many options for rolling out new changes to their live databases. Even if you were cautious, and did your development in a separate Dev copy of your production file, it was difficult to migrate these changes to your production file.

You could roll your own deployment workflow, scripting FileMaker imports for each table in your solution, and update this workflow whenever you added new tables or fields. These imports are slow and tedious though, and most of us would simply make the changes directly in the live file.

With the release of FileMaker 17, FileMaker came out with the FMDataMigration tool, completely replacing the need for using FileMaker native imports to move your data around. Here at 360Works, we built 360Deploy around the FMDataMigration tool to streamline and completely automate its use, making development changes a tedium free experience.

In today's article, we will walk you through how to do both options so you can determine which is right for you.

Stay updated with 360Works

360Works
General Questions: [email protected]
Need Support? Email: [email protected]