Universal Migrator's best practices are generally optimized around doing migrations as quickly as possible. This is the ideal scenario, however, sometimes providers implement restrictions that force data to move much slower than technically possible.
The following guidelines should be used when transferring data from a slow provider.
The process described in this article is for use when migrating a customer from a system with very slow APIs.
Process
1. Create a Complete Backup from the Source System
You should take a complete backup of the source system - including documents. Depending on the amount of data, this may take a long time.
2. Freeze Contacts and Matters from the Source System
You should inform the client that, effective immediately, they may not add or edit any contacts or matters in the source system. They may still create and edit documents, time, expenses, etc. for existing contacts and matters in the source system, however, no new contacts and matters should be created in it.
At this point, the client should be "live" in the new system; all new contacts and matters should be created in the new system and all work related to these new contacts and matters should be performed in the new system.
3. Transfer Contacts and Matters from the Source System.
You should then create a backup of all contacts and matters from the source system and restore them into the new system. This backup should only contain the minimal information related to the contacts and matters.
4. Freeze All Data in the Source System
Once the restore is complete, effective immediately, the client should not create or edit any records at all in the legacy system. The client may still view data from the source system, but they should not add or edit any data in it whatsoever. At this point, the client should be fully "live" in the new system for all data. If a client needs to edit a document, they may open it from the source system, make any changes, and then simply ensure they save it to the new system and not the old.
5. Transfer all Outstanding Records
You should then take a final backup of the source system and transfer all remaining records to the new application.
The above information is the best practice for migrations from slow providers. Some firms may find this inconvenient and request an alternate process, however, you should inform them that, because they are leaving a provider who intentionally makes migrations slow, this is the only process that reliably works.