Promote a release without overwriting live data
Move a tested schema to production while production records stay in place. That is the workflow teams usually mean when they say data migration.
Automated FileMaker migrations
Automate FileMaker data migrations — with a plan, not a prayer.
Server work gets risky when the steps live in someone's memory. FM Dojo Server Deploy turns migrations into repeatable plans — promote schema, preserve production data, transfer files server to server, and keep the full run history attached so rollback is a decision, not a panic.
Ronin and higherDev to testTest to productionProduction refreshMulti-file plansRun history
Server to server pipeline
A plan knows what to move, where it goes, and how each file finished.
Source server
Dev or test
Customers.fmp12
Orders.fmp12
Reports.fmp12
Migration plan
1. Pick source
2. Choose files
3. Preflight
4. Transfer
5. Verify
Target server
Test or production
Customers.fmp12
Orders.fmp12
Reports.fmp12
What it automates
The boring parts that should be boring
A migration is usually not one command. It is a sequence of choices, checks, file movement, backups, logs, and verification. FM Dojo turns that into a plan you can run again.
Available on Ronin, Ninja, and Sensei plans.
Refresh development from production
Replace a stale dev file with a clean production copy when you need realistic data for debugging, reporting, or training.
Transfer related files as one plan
Bundle multiple FileMaker files, order the run, stop on a risky failure, and keep the history together instead of chasing terminal logs.
Migration modes
Choose the safe direction for the job
Not every transfer means the same thing. Production releases need caution. Development refreshes need a clean copy. The plan type makes that intent explicit.
Preserve target data
New schema
Existing live data
Use this for test to production releases when the target data is valuable and must stay put.
Replace target file
Production copy
Fresh dev file
Use this when a development or training server needs a clean copy of a real file.
Beginner-friendly controls
Know what will happen before you press run.
Server work gets risky when the steps live in someone's memory. FM Dojo shows the plan, files, direction, failure behavior, and run status in one place.
Plan level: Ronin and higher.
Source and target servers are reachable
The target file name is explicit
Files run in the order you choose
Each file can stop the plan on failure
Backups and logs stay attached to the run
Rollback decisions use the recorded backup path
Run history
In progressContacts.fmp12
Completed
2m 14s
Backup saved
Invoices.fmp12
Completed
3m 41s
Data preserved
Reports.fmp12
Running
0m 58s
Verifying
Credentials stay scoped
Use saved server connections and database authorizations instead of passing credentials around for every release.
History stays attached
Each run keeps statuses, logs, timing, backup paths, and errors so review does not depend on memory.
Rollback is a decision, not a panic
When a backup exists, the run view keeps the path visible so a rollback can be deliberate.
Migration day backup plan
Moving production data? Bring a parachute.
Book consulting to review the migration path, check rollback options, plan the cutover, and make sure the scary part has a boring checklist.
Unblock a lesson
Review your approach
Plan the next build
Make migrations repeatable before the next release window.
Use Server Deploy for FileMaker data migrations, server to server file transfers, production refreshes, and release plans that need a clear audit trail. Server Deploy is included with Ronin, Ninja, and Sensei.