If you have a Universal Backup database from a previous version of Universal Migrator, you will need to upgrade it by following the
Delta Migration Procedure.
Universal Migrator now includes Backup options for the following applications:
- Affinity Backup
- FilePro Backup
- NEOS(DB) Backup
- Omega Backup (Preview)
With this update, Universal Migrator now supports 2770+ migration paths.
New Utilities
Utilities > Database Detector
Sometimes clients say things like "I use Amicus" which can be confusing because there are multiple "Amicus" products (Amicus Attorney, Amicus Accounting, Amicus Cloud, etc.).
Database Detector solves this problem.
When provided a database, using AI, it will provide the actual name for the app that uses that database.
The following tools have been enhanced since the December 2024 update to Universal Migrator:
- ActionStep Backup
- Aderant Total Office Backup
- Amicus Attorney Backup
- Amicus Cloud Backup
- Amicus Small Firm Edition Backup
- Blue Dot AI Backup
- Caret Legal Backup
- Centerbase Backup
- Cerenade Backup
- Client Profiles Backup
- Clinic Cases Backup
- Clio Backup
- Coyote Analytics
- Docketwise Backup
- Documatics Backup
- Dropbox Backup
- FilePro Backup
- Juris Backup
- Justice Center Online Backup
- Keyhouse Backup
- Lawcus Backup
- Legal Files Backup
- Legal Suite Backup
- Litify Backup
- LeanLaw Backup
- Merus Backup
- MyCase Restore
- Neos Backup
- NetDocuments Backup
- Orion Backup
- PC Law Backup
- PerfectLaw Backup
- ProLaw Backup
- Soluno Backup
- Tabs3 Billing Backup
- Time Matters Backup
- TrialWorks Backup
- Zola Suite Backup
Remapped Fields
This field was only used by a small number of systems where Employer was not a contact but just a text string.
This field now maps as a custom field in systems that leveraged it.
Matters: ClientReference > Custom Field
This field was only used by a small number of systems.
This field now maps as a custom field in systems that leveraged it.
Matters: CustomNumber > Custom Field
This field was only used by a small number of systems.
This field now maps as a custom field in systems that leveraged it.
All Tables: Result_Raw_Content > Result_Content
The Result_Raw_Content field has been renamed to Result_Content for better symmetry with additional Result_* columns and the newly added Source_* columns.
Added Fields
All Tables: Source_Content
There used to be a Final_Raw_Content and Original_Raw_Content field. These fields contained duplicate copies of the raw data which was quite large and never modified.
The duplication has been removed and the data moved to Source_Content.
All Tables: Source_Content_Url
In supported systems, this includes a URL that will provide the Source_Content.
This makes it easy to quickly navigate between the DB and the "live" version of the source content in the legacy system.
All Tables: Source_View_Url
In supported systems, this includes a URL that will navigate to the human visible "view" URL for the Source record.
This makes it easy to quickly navigate between the DB and the web UI version of the Source_Content in the legacy system.
All Tables: Result_Content_Url
In supported systems, this includes a URL that will provide the Source_Content.
This makes it easy to quickly navigate between the DB and the "live" version of the Result_Content in the destination system.
All Tables: Result_View_Url
In supported systems, this includes a URL that will navigate to the human visible "view" URL for the Result record.
This makes it easy to quickly navigate between the DB and the web UI version of the Result_Content in the destination.