360Works MirrorSync Support Announcement
We are continuing to innovate and improve MirrorSync. Therefore, we will be focusing our efforts on providing support for version 3 only. We want to ensure users are operating on the fastest, most reliable sync framework possible. As of January 31st, 2017, MirrorSync 1 and 2 will no longer be supported.
Since the release of MirrorSync 3, we have received a significant amount of reports on speed and scalability improvements. Existing users are experiencing a more reliable and powerful sync, robustly handling even hundreds or thousands of offline devices. Many businesses in the medical IT field are relying on MirrorSync 3 to transfer large amounts of sensitive data, such as electronic medical records, photos, electrocardiograms, and patient care reporting for up to 500 offline devices. Other industries, such as inspection, media, and education fields, are using MirrorSync 3 to quickly sync mission critical data.
If you are currently using an older version of MirrorSync, we recommend upgrading to MirrorSync 3 to experience better performance. MirrorSync 3 can sync between any combination of FileMaker Pro, FileMaker Go, FileMaker Server, SQL database (MySQL, Oracle, SQL Server, or any database that supports JDBC), Salesforce, and Amazon RedShift. MirrorSync is only installed on the server computer, and very easy to set up. It is not a plug-in, and does not require any software installation on client devices.
Version 3 introduced many new features such as support for setting up simultaneous and multiple sync configurations per database, Salesforce and Amazon RedShift integration, as well as significant speed, reliability, and memory improvements. Read the complete changelog here. If you?d like to try out the server-to-server features of MirrorSync 3, please send us an email at firstname.lastname@example.org and a free 14-day trial license will be issued.