FileMaker Server Migration Checklist

With recent social distancing measures, many organizations are migrating to the cloud in order to access workplace applications remotely. Similar to our Security Checklist, we’re publishing our own proven plan for easy FileMaker server migrations from on-premises to cloud servers. This method is aimed at preventing problems and minimizing downtime. 


  1. Have compatible SSL certificate files and the correct private key password on hand. 
  2. Make sure you have the right database encryption keys for files encrypted at rest (EAR).
  3. Create a new cloud instance.
  4. Install, configure, and test FileMaker Server on the new instance.
  5. Update FileMaker Server’s default PHP installation to one that’s currently supported. We have blog posts on this subject for Windows and MacOS.
  6. Install and test the SSL certificate on the new instance.
  7. Create a backup of the FileMaker file(s) on the on-prem server and import it to the cloud server for testing.
  8. Secure your FileMaker file per our Security Checklist.
  9. Open the files on the FileMaker server in the cloud.
  10. Import the script schedules to the cloud server, and check that they’re configured and working properly.
  11. Test the databases wherever they’re used (FileMaker Client, WebDirect, Data API, xDBC, PHP, etc.). If you are using PHP, check that you are ready for PHP 7.
  12. Have a main user connect to the new server and verify that it’s performing as expected.
  13. Modify the database to lead all users to a page saying something like “Connection success” without being able to navigate to another layout.
  14. Distribute launcher files or shortcuts to the database to all users. Ask all users to test the file and confirm that they saw “Connection success”.
  15. Now that you’ve completed a dry-run of the migration, you will have a time estimate for the actual migration.  Ask stakeholders to approve a maintenance window for completing the migration outside of business hours.

Migration day

  1. Ensure users are disconnected from the on-prem server.
  2. Close database files on the on-prem server and stop the server and its processes. Upload database files in the fastest available method (i.e. Google Drive or Jump Desktop) to the cloud server. Compressing files with 7zip can save time if internet is slow.
  3. Open database files on the cloud server (admin console or CLI).
  4. Verify that the script schedules are properly configured.
  5. Run a backup schedule and ensure the backup works.
  6. Test the databases wherever they’re used (FileMaker Client, WebDirect, Data API, xDBC, PHP…).
  7. Ask the stakeholder(s) to test the database(s).
  8. Set the on-prem FileMaker server to not start automatically, and disable the FileMaker service. This will prevent users from accidentally connecting to the wrong copy of your database.


  1. Be ready to support users and stakeholders.
  2. Debrief your team. 
  3. Obtain feedback from stakeholders as you assist with change management.
  4. On the old server, migrate backups to the cloud or other location before decommissioning the on-prem server. We strongly suggest waiting at least two weeks before decommissioning the on-prem server, in case a rollback is needed.

Migrations are complicated and can fail without sufficient planning. If you are uncertain about completing this process on your own, AppWorks is happy to assist you. Email to schedule and discuss migration.