MirrorSync 7 introduces a powerful new method for distributing and updating your FileMaker solutions through the iOS SDK by packaging a single, lightweight launcher file inside your custom FileMaker iOS app. This launcher automatically downloads and updates your solution, providing a seamless, native app experience. Best of all, you can deploy updates to your users at scale without needing to rebuild or resubmit your app to Apple for approval. MirrorSync 7 is perfectly suited for both Mobile Device Management (MDM) distribution and Apple App Store deployments, giving you maximum flexibility and control. Watch the demo video to learn more.
MirrorSync is the fastest and most reliable way to sync offline FileMaker solutions on iPad, iPhone, macOS, or Windows PC. Seamlessly sync between FileMaker Pro, FileMaker Go, FileMaker Server, SQL databases, Salesforce, WordPress, cloud Databases hosted on AWS or Azure, and more.
To see it in action, check out our YWAM Case Study!
VersionWhat's New?
Own a license?
Download
current version.
Learn more about our
Portfolio License bundle!
What's New in MirrorSync 7
MirrorSync 7 packs in powerful features to optimize performance when syncing your solution.
-
Smart Updates
-
Non-blocking Internal Writes
-
Deferred Flushing
-
Optimized Clones
We benchmarked a real-life solution for LifeSource, Inc, a customer who uses MirrorSync heavily for their daily operations providing healthcare services. This large and complex solution is 33 gigabytes with 136 tables, and it took 28 minutes to run an initial sync with MirrorSync 6. With the performance optimizations of MirrorSync 7, the same database now runs the initial sync in just under 7 minutes, about 4x faster. See Smart Updates in action in this demo video.
MirrorSync 7 now supports deferred download links, which allow users to provide an e-mail address rather than waiting for downloads in their browser. This is impactful when MirrorSync is configured to perform an initial sync server-side before serving the file to the user. Users no longer need to wait, nor worry about their mobile device entering standby mode or suffering from connection loss. Once the server is finished processing the request, the user will receive a notification with an instantaneous download.
Instead of sending users complicated links that require multiple browser steps you can now deliver a simple launcher file that automatically downloads and opens the latest version of your solution to your users. This process streamlines user experience—especially in the case of multi-file solutions and provides you with a simple avenue for app updates no matter how you deploy your app.
How Does MirrorSync Compare?
| Feature | MirrorSync 6 | MirrorSync 7 |
|---|---|---|
|
Work offline in a FileMaker App hosted on FileMaker Server Access your FileMaker solutions using an iPad, iPhone, or macOS/Windows PC without a network connection. Work on your own offline FileMaker solution at the fastest possible speed, then sync your changes with FileMaker Server, or any other supported database, when you go back online. |
 |
|
|
Sync two or more FileMaker Servers maintain live copies of your databases across geographically distributed servers, enabling faster local access for remote teams, seamless data duplication, and solid disaster recovery failover strategies. |
|
|
|
Sync with non-FileMaker databases Seamlessly integrate FileMaker with web apps, reporting tools, e-commerce platforms, and enterprise systems using any compatible JDBC driver. |
|
|
|
Deploy Updates at-scale to App Store and MDM apps Use the MirrorSync launcher file, along with theDatabaseVersion field
to distribute updates to apps bundled with the iOS SDK
|
 |
|
|
MirrorSync Smart Updates MirrorSync intelligently determines when data needs to sync. Improving performance withReplace Field Contents and container fields
|
|
|
|
Take advantage of Latest FileMaker Features Utilize Deferred Flushing, Transactions, and optimized clones |
|
|
|
Deferred Download Links Users don't have to wait for server-side initial syncs, but receive notifications instead |
|
|
|
Non-blocking writes to internal sync data MirrorSync does not block when writing to its internal sync database, allowing many simultaneous writes without stalling |
|
|
|
Full API Control over MirrorSync Manage MirrorSync using our fully-featured JSON API |
|
|
|
Sync History Tracking Utilize an auxilliary solution hosted on FileMaker Server to track historical sync records across all of your FileMaker to FileMaker configurations and devices |
|
|
Videos
System Requirements
- Server:
- Windows Server 2019 or later / Mac OS X 10.12 or later / Amazon Linux 2 or later / Ubuntu 22.04 or later
- FileMaker Server 19.6 or later; FileMaker 21 is recommended to take advantage of all performance features
- FileMaker Cloud is not supported
- 4 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.12 or later, or Windows Server 2019 or later
- FileMaker Pro 18 or later
- Sync Client:
- Mac or Windows with FileMaker Pro 18 or later
- FileMaker Go 18 or later running on iPad, iPhone, or iPod Touch
What does the FileMaker community think?
FAQ
-
MirrorSync can sync directly between FileMaker Go and any supported server database, including MySQL, SQL 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,500. 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.
-
It depends on whether the spoke solution is a full copy or an empty clone, and how many tables, fields, and records it contains. The initial sync in ideal conditions is very fast, but in less ideal conditions, it can take several minutes, or even hours. 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.
-
No--The MirrorSync 7 script was re-written to use new features in FileMaker 20.3, and works best with version 21+, but is still compatible with versions of FileMaker as old as 18. If you are using FileMaker 17 or earlier, you will need to update in order to use MirrorSync
-
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.