The Migration Manager is an administrative tool that helps you simply and securely migrate large quantities of data to Cloud. Organizations who want to use the Migration Manager must contact Caseware Support with the following information:
Intended migration date(s)
Size of active client data
Size of inactive client data
Number of files to migrate (current and prior year)
Number of users
Additionally, your organization must confirm that they will not attempt to migrate files that have been associated with a different organization.
Prerequisites:
Your organization must be using Working Papers 2019 or later.
Your organization must have Working Papers with SmartSync technology. If you do not have SmartSync, see Differences between SmartSync and non-SmartSync, and contact your local distributor for more information.
Your organization must have a Caseware Cloud site. If you do not have a Cloud site, you can request an invite.
You must have an internet browser that supports TLS 1.2 or later. For more information, see Disabling access to Caseware Cloud for older and unsupported browsers.
You must install the Migration Manager on the computer or server containing the data to migrate.
An administrator must operate the Migration Manager on behalf of the organization (administrative privileges are required).
You must connect the Migration Manager to your Cloud site to access all migration options. On the main menu, click Log In and enter your Cloud site URL and administrator credentials. You do not need to include the web protocol (http:// or https://) in the URL.
Note: If your organization's Cloud site is set up as part of a business unit, you must connect the Migration Manager to the URL of an individual business unit, rather than the URL of the top-level Cloud site (where staff members typically sign in). During the migration process, data will migrate to the to the individual business unit and only be accessible to the business unit's users. You can then repeat the process with the URLs of other individual business units.
Recommendations:
Validate the health of your files prior to migration. See Validate engagement files for more information.
Where possible, ensure that the engagement properties in your files contain as much information as possible to assist in the auto-map process. See Upload entities to Cloud for more information.
Compress all parent files prior to migration to reduce migration times. Ensure you include all subfolders during compression.
Back up all parent files prior to migration. The original files on your server will be migrated to Cloud.
Run only one instance of the Migration Manager at a time. Multiple instances will not speed up the processing time and can negatively impact Cloud performance.
Restart self-hosted SmartSync Servers after a migration to clear the engagement file list. If you migrate your data in stages, restart the server after each stage.
Firms who seek to leverage Caseware Sherlock's practice management capabilities, while still using an on-premise SmartSync Server, can integrate their engagement files with Cloud directly through the Migration Manager. This feature enables firms to integrate historical files, extract historical data, and then use that data in Caseware Sherlock.
Notes:
To integrate engagement files from a SmartSync Server:
The files are integrated with Cloud and the integration results display. For more detailed information, view the automated log file by clicking the link provided. Click CLOSE to return to the main menu.
Important: Before your staff open any child sync copies of the files, you must delete the parent file copies.