This site uses tracking cookies. By using this site, you agree to our Privacy Policy. If you don't opt in, some parts of the site might not function.
Home / Blog / FileMaker / Introducing FileMaker 17’s FMDataMigration Command Line Tool
15May 2018

Introducing FileMaker 17’s FMDataMigration Command Line Tool

About the Author

Matt Hintz Matt Hintz

Matt is a Senior Application Developer at Soliant. He is FileMaker 11, 12, 13, 14, 15, 16, and 17 certified developer. When Matt is not working in FileMaker he enjoys taking his dog Zeppelin for walks and playing in a local rock band.

Comments (4)

Neil - May 17, 2018

Hi Matt, Great article an associated demo video and really looking forward to getting my teeth into this new tool. Do you know if it is possible to use this within the iOS SDK for running app upgrades? I have an app that consists of a Launcher file and the main app file and it would be great to use this to allow for updates.

    Matt Hintz
    Matt Hintz - May 18, 2018

    Hi Neil! Thanks for the feedback and question. In terms of the FileMaker iOS SDK, FileMaker’s Data Migration Tool only runs on windows and Mac through their respective command line prompts. So my assumption is these commands cannot run from within a sandboxed iOS application, including FileMaker’s iOS SDK. The launcher file method that you mentioned is the only way I am aware of to make updates to a file in FileMaker’s iOS SDK. Cheers!

David Wikström - July 12, 2018

Great sample file!
I seem to be having an issue with getting the output written to a file on Windows when the path to the executable contains a space (and probably any other character that would require escaping the path). Simply enclosing the path to the executable in quotes did not work (at least not a first attempt).
For many uses, this is of course a non-issue as you can make sure the exe is not in such a location, but I’ve got my own variation of a FileMaker-database driving data migration, where the migration can run server-side (on FileMaker Server using PSoS), and I’d prefer having the migration tool under FileMaker Server\Data\Documents or \Scripts if possible – rather than e.g. directly under C which is what I currently do – so I’d be interested to hear if you have any ideas on workarounds…

    Matt Hintz
    Matt Hintz - July 13, 2018

    Hi David! Thanks for the feedback. Correcting the path for windows is on my list for a next version of this tool but I just haven’t had time to complete this change. I will update you once I have had a chance to complete this update.

Leave a Reply