The Original FileMaker Community
Business Templates - Demo Apps - Video Tutorials -Samples - Help - 46000 Member Forum

The Leading Filemaker Developer Tools

YADMT (Yet Another Data Migration Tool) for FileMaker

When FileMaker 17 came out, Claris also released a new tool called the FileMaker Data Migration Tool (DMT). My colleague Matt Hintz wrote a nice overview of how to use it and explained how it made deploying FileMaker solutions a lot easier than with previous methods. More recently, Mislav Kos posted about how running concurrent copies of DMT can speed up the migration of a multi-file solution. In this post, I want to provide a brief overview of some of the tools that make DMT easier to use, and I also want to introduce a new command-line tool we developed.

Existing DMT Tools

Over the last two years, there have been some wonderful tools to help developers use the DMT. This is not an in-depth review of these tools but rather a quick overview of the current landscape.

The first class of tools I want to talk about are the FM Data Migration Assistant by Productive Computing, FMDataMigration by Lesterius, FM Data Migration Companion by DB Services, and the FileMaker Data Migration Tool Demo that was created by Soliant’s own Wim Decorte. Each tool is a FileMaker file that provides a very easy GUI to migrate your database files. They are by far the easiest way to get up and running with DMT and are a great starting point for anyone who wants to experiment with DMT without having to use the command line.

If you are comfortable with command-line tools, or if you don’t want to run FileMaker Pro to convert the files, you might want to write a bash or batch script to run DMT. If you frequently migrate the same files, this might be a good solution for you as it does not require you to install or buy any extra software like FileMaker Pro or one of the tools I talk about next.

The next class of tools I would like to cover includes 360Deploy by 360Works, Otto by Geist Interactive, and base72 by 27solutions. These tools are more than just something to help you run DMT as they also help with creating clones on your development server and with moving those clones to the production server. These tools require some setup, but their goal is to make deployments as simple as pushing a button.

Multi-File Deployments

As Mislav posted, one of our clients wanted to have deployments run as quickly as possible, because due to the 24×7 nature of their business, all FileMaker outages, including those caused by deployments, had a serious business impact. In addition to speed, security was a major concern – they didn’t want the full access password stored in either clear text or a reversible manner as is required by all other tools (except a batch file that prompts for and then stores the password in a variable). A sufficiently sophisticated system script could accomplish all of these requirements, but the development effort requires a specialized skillset.

We ended up creating a simple application that we are releasing here. We have since tested it on a few other projects and wanted to share it with the wider FileMaker community.

YADMT (Yet Another Data Migration Tool)

YADMT (Yet Another Data Migration Tool) is a command-line tool written in .NET. It essentially acts as a DMT wrapper and is intended for running DMT on more than one database file (although it will work fine if used with just one file). The tool has been mainly tested on Windows and minimally tested on macOS using Mono. YADMT is intended for situations where there are at least two files to migrate, the overall size of the solution files is large, and the migration time needs to be made as short as possible. You can select to have YADMT run anywhere from 1 to 9 concurrent DMT processes. YADMT will process files from largest to smallest to run the parallel jobs as efficiently as possible. When you run the tool, it will prompt you with several questions; however, these inputs can also be specified using an ini file. YADMT is dependent on the context you run it from as the clone files, source files, ini, and logs are all based on the current command line directory.

Below is an example of how you can set up your folder structure for use with YADMT. In this example, we organized our deployment using a timestamped folder (2020-01-01) and “clone” and “source” subfolders.

On this site we promote, share and showcase material from Soliant Consulting one of the BEST consulting company’s in FileMaker.

We encourage you to visit their site and to inquire about their services. FMT is proud to deliver and promote FileMaker for Small Business Owners Worldwide since 1997. Our Forum The Original FileMaker Forum has 45,700+ members.

This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Accept Read More

Privacy & Cookies Policy