MirrorSync

The best way to sync FileMaker databases on an iPad, iPhone, or laptop without a network connection. Sync between any combination of FileMaker Pro, FileMaker Go, FileMaker Server, SQL databases, Salesforce, WordPress, and Amazon databases.

VersionWhat's New?

Own a license?
Download current version.

Learn more about our
Portfolio License bundle!

Full-featured and free!

If you’re too busy to set up MirrorSync right now, we’ve set up a live demo of the 'Tasks' starter solution. You can try MirrorSync in seconds from Mac, Windows, or iOS without installing anything by downloading this FileMaker file:

Live Demo

Features

Work in FileMaker Offline

Access your FileMaker databases on an iPad, iPhone, or laptop without a network connection. Work on your own FileMaker offline database at the fastest possible speed, and sync your changes with FileMaker Server when you have working network access. With MirrorSync, you can work from anywhere with stability and ease! Learn more about the fast speeds.

Fast and Easy Setup for Syncs

MirrorSync’s amazing speed is powered by a multi-threaded processing core that runs on your server to almost instantly detect all changes between client and server! The integration process is so easy that most developers are able to complete their first successful sync within an hour of installing MirrorSync. Learn more about the easy integration process.

Sync Multiple FileMaker Servers

Sync multiple FileMaker Servers for load balancing and clustering or to speed up slow connection to FileMaker Server. Using MirrorSync to cluster FileMaker Servers running side-by-side can increase server availability for your mission critical solution. Through data replication, you can ensure server reliability by balancing loads and handling server failure.

Sync Virtually Any Database with FileMaker

MirrorSync can sync just about anything to anything else. Sync FileMaker to popular platforms like WordPress, Salesforce, Amazon RedShift, and Amazon DynamoDB. MirrorSync can sync with Oracle, MySQL, SQL Server or any other JDBC compatible database. If you can think it, we can sync it! Learn more about the Server-to-Server sync options, customizations, or scalability.

Need help setting up one of our products?

We are experts in FileMaker, Java, and Amazon Web Services. If you need a customized plug-in, modifications to an existing plug-in, or full plug-in/web app integration services, we can perform these services for you. Please fill out our Quick Form and we will contact you to discuss your solution needs and create an estimate.

Videos

10 Minute Setup for MirrorSync 6!
FileMaker For the Enterprise
Sync Wordpress with FileMaker
MirrorSync 6 All about developers

About

MirrorSync is the best way to sync FileMaker databases on an iPad, iPhone, or laptop without a network connection. Work on your own FileMaker offline database at the fastest possible speed, and sync your changes with FileMaker Server when you have working network access. With MirrorSync, you can also sync multiple FileMaker Servers for load balancing and clustering or to speed up slow connection to FileMaker Server. With MirrorSync you can sync your FileMaker Go files, handle FileMaker offline sync, and sync virtually any database, like Salesforce or WordPress, with FileMaker!

Using our award-winning MirrorSync, your users can work efficiently at a job site, their house, a coffee shop, or even an airplane, all without worrying about slow or non-existent wifi or cellular network access. See how you can even sync FileMaker Go or Pro on a SHIP in our YWAM Case Study!

What Can You Do with MirrorSync?

Work offline in a FileMaker App hosted on FileMaker Server check
Improve FileMaker speed over WAN by working on local copies, then syncing check
Sync two or more FileMaker Servers check
Sync Salesforce and FileMaker check
Sync WordPress and FileMaker check
Sync Oracle, MySQL, SQL Server or any other JDBC compatible database check
Customize your workflow - sync specific tables, records, fields, and choose sync direction check
Sync FileMaker fast with speed powered by a multi-threaded processing core check

System Requirements

  • Server:
  • Windows Server 2012r2 or later / Mac OS X 10.12 or later / Linux running Tomcat 6 or 7.052 or later.
  • FileMaker Server 17 or later is recommended; FileMaker Server 18v3 or later is recommended. MirrorSync 6.21 or later requires FileMaker Server 18 or later.
  • FileMaker Cloud is supported, although it cannot support all MirrorSync features (See special instructions in documentation for syncing with FileMaker Cloud).
  • 3 gigabytes or more of RAM. 8 gigabytes or more are recommended for large databases with hundreds of thousands of rows, or for more than 10 simultaneous sync operations.
  • Configuration Utility:
  • OS X 10.8.3 or later, or Windows Server 2012v2 or later.
  • FileMaker Pro 17 or later.
  • Sync Client:
  • Mac or Windows with FileMaker Pro 17 or later OR
  • FileMaker Go 17 or later running on iPad, iPhone, or iPod Touch.

What does the FileMaker community think?

...MirrorSync install has been absolutely rock solid for the last several months. Not only that, but it is amazingly fast. I just added time data records to the sync. The screen shot shows the result from the first subsequent sync. 77 seconds to insert 41,762 records is pretty amazing. Thanks for a great product!

Ian Jempson, Brightsource

We are syncing 21 tables in our solution with MirrorSync. It is a combination of 16 core data tables with 5 join tables. There are roughly 750,000 records in those tables. I have been updating my iPad every few days and it has been working very well.

Paul Costanzo, Recruiting Pro Software

FAQ

  • MirrorSync 5 and earlier will work with FileMaker Server all the way back to version 10. The MirrorSync 6 script was re-written to use new features in FileMaker 17, so it requires that version or later. When you purchase a MirrorSync license, it will also work on older versions, so to sync with an old version of FileMaker Server, purchase MirrorSync 6 and then contact support@360works.com to have us send you an older version to use.

  • MirrorSync will detect this conflict and resolve it. It the two users changed different fields (for instance, one user changed the email address field, and the second user changed the phone number field), then MirrorSync can merge these changes together. If the users changed the same field (for instance, they both change email address), then MirrorSync can be configured to either assume that the most recent change is correct, or it can ask a user or administrator to resolve the conflict in a color-coded, mobile-friendly web interface. The user’s conflict resolution choices will then be applied to the next sync.

  • Yes. MirrorSync is compatible with UUID keys (select ‘Developer-managed keys' during configuration’), as well as serial numbers (select ‘MirrorSync-managed keys’ during configuration). It can even sync a mixed environment, where some tables use UUIDs and others use serial numbers.

  • No, MirrorSync does not support peer-to-peer synchronization. FileMaker Pro / Go can sync with FileMaker Server or any other supported database server (see previous question).

  • Almost none; the Data API is used to initiate the MirrorSync script on the server. After that the actual data transfer is done between the MirrorSync script on FileMaker Server and the MirrorSync web application using the Insert from URL script step.

  • MirrorSync can sync directly between FileMaker Go and any supported server database, including MySQL, Sequel Server, Oracle, DynamoDB, Amazon RedShift, Salesforce, and any JDBC-compatible database. You will need FileMaker Server running for the configuration process, but the actual synchronization script will communicate from FileMaker Go <-> MirrorSync server <-> Any supported database server. Even container fields are supported; they are stored as BLOB data on an SQL server, or on S3 for DynamoDB.

  • Pricing for that configuration is $1,600. Contact support@360works.com to request a free, 30-day trial license so that you can set up the sync and evaluate it for yourself.

  • The first time a database is copied to a new device and synced, that usually takes somewhere between 20 seconds and several hours, depending on the size of the database and how many records need to be written. After that initial sync, syncs are incremental (meaning only the changes are transferred). Incremental syncs with no changes usually take less than 5 seconds. Incremental syncs with a modest number of changes ( < 100 records) are usually less than 30 seconds. Incremental syncs can take a very long time if tens of thousands of records have been changed, especially if they have container data.