Sync FileMaker in both directions, online or off.
Full-featured, and free for one device.
Too busy to set up MirrorSync? Try the live 'Tasks' starter solution from Mac, Windows, or iOS in seconds, with nothing to install. Just download the FileMaker file and see it work.
Bidirectional sync
MirrorSync detects inserts, updates, and deletes in all devices, and syncs all the changes to all other devices / servers.
Resolve conflicts
If the same record is changed on multiple devices, MirrorSync can usually merge the changes. If it can't, you have many choices for how they are resolved.
Free
MirrorSync is 100% free for one device and one server. This is not a trial or time-limited. If all you need is one offline copy of your database, you pay nothing!
Simple setup
MirrorSync works with the primary key and timestamp fields you probably already have, one blank layout per syncing table, and three copy-paste operations.
Customizable
Use simple FileMaker scripting to control which users get which records, and custom actions to take during the sync. You control which tables sync, which direction each table syncs, and how conflicts are resolved for each table.
Optimized for speed
No-change syncs usually take less than 2 seconds to complete, and changes are usually written at 5-50 records per second. Try our live demo and see for yourself!
Videos.
Ship updates without resubmitting to Apple.
Distribute and update your FileMaker solutions through the iOS SDK. Package a lightweight launcher file inside your custom iOS app, and it downloads and updates the solution on its own, for a native app experience. Push updates to users at scale without rebuilding or resubmitting to Apple. It fits both MDM distribution and App Store deployment.
Initial syncs, about 4× faster.
We benchmarked a 33 GB LifeSource solution with 136 tables. An initial sync that took 28 minutes in MirrorSync 6 now runs in 5:50 in MirrorSync 7, about 4× faster.
- Smart Updates: sync only what actually changed
- Non-blocking writes to internal sync data
- Deferred flushing
- Optimized clones
Deferred download links.
When MirrorSync runs the initial sync server-side, users don't have to wait in the browser. They enter an email address instead, and once the server finishes, they get a notification with an instant download. No standby-mode or dropped-connection worries.
Simpler solution downloads.
Skip the complicated multi-step links. Hand users a single launcher file that downloads and opens the latest version of your solution on its own. It is cleaner for multi-file solutions, and it gives you one consistent way to push updates however you deploy.
How does MirrorSync compare?
| Feature | MirrorSync 6 | MirrorSync 7 |
|---|---|---|
| Work offline in a FileMaker app hosted on FileMaker ServerUse your solutions on iPad, iPhone, or a Mac/Windows PC with no network connection. Work offline at full speed, then sync your changes when you reconnect. | ✓ | ✓ |
| Sync two or more FileMaker ServersKeep live copies across geographically distributed servers for faster local access, data duplication, and disaster-recovery failover. | ✓ | ✓ |
| Sync with non-FileMaker databasesIntegrate 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 appsUse the MirrorSync launcher file with the DatabaseVersion field to distribute updates to apps bundled with the iOS SDK. | — | ✓ |
Smart UpdatesMirrorSync determines when data needs to sync, improving performance with Replace Field Contents and container fields. | — | ✓ |
| Take advantage of the latest FileMaker featuresUse deferred flushing, transactions, and optimized clones. | — | ✓ |
| Deferred download linksUsers receive a notification instead of waiting for a server-side initial sync. | — | ✓ |
| Non-blocking writes to internal sync dataMirrorSync doesn't block when writing to its internal sync database, so many writes run at once without stalling. | — | ✓ |
| Full API control over MirrorSyncManage MirrorSync through a full JSON API. | — | ✓ |
| Sync history trackingTrack historical sync records across all your FileMaker-to-FileMaker configurations and devices, via an auxiliary solution hosted on FileMaker Server. | — | ✓ |
Configurations and devices.
MirrorSync pricing has two parts, configurations and devices. Every price is monthly, billed annually. A configuration is one sync pair: the two platforms syncing with each other. A device is a FileMaker Pro or Go client that syncs. Devices share one pool across all your configurations. Your first Server-to-Pro/Go configuration and one device are free, for everyone.
| Configurations | Monthlybilled annually |
|---|---|
| Server to serverFileMaker Server or a non-FileMaker SQL database on each end | $115 |
| FileMaker Server to FileMaker Pro/Goor $83.33 for unlimited Server-to-Pro/Go configurations | $15 |
| Non-FileMaker SQL to FileMaker Pro/Go | $115 |
| Other or custom setupsTopologies beyond the standard pairs | Talk to us |
| Devices (price per device) | |
| 1+ | $7.50 |
| 10+ | $6.50 |
| 20+ | $6.00 |
| 50+ | $5.00 |
| 100+ | $4.00 |
| 200+ | Call us |
What customers say about MirrorSync.
“My hats off to you… Although I am still tweaking, today I really tested heavily MirrorSync, and man … I've got to say WOW. It's quite impressive how well it works!!! And pretty darn quick as well. I just wanted to give you a pat on the back for it … very impressive!”
“We now have 5 servers with 360Works, and were converting over 40 of our clients to MirrorSync 6… we also used 360Deploy to migrate all our data from one server to another. Above all, I would commend Junior… he was VERY responsive and truly went 'above and beyond.' So far it's been fairly seamless for our users.”
“Thank you to your team for getting these deployments over the line, and a special thanks to Adam and Jesse for analysing the logs in real time to hone performance down to an amazing 3-minute cycle. Not only will we have a very happy client, we now have a much better understanding of MirrorSync.”
“We love MirrorSync, want to update our email to CloudMail....looks like it's going to solve more of our problems for us, Thanks!”
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
Common questions.
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.
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.
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.
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).
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.
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.
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.
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
Need help setting up one of our products?
We are experts in FileMaker, Java, and Amazon Web Services. If you need a customized plugin, modifications to an existing plugin, or full plugin and web-app integration services, we can perform these services for you. Please reach out to us to discuss your solution needs and create an estimate.