This is a quick reference guide for migrating from on premise iManage to Cloud iManage.

Migration to Cloud iManage

This guide is aimed at existing CAM customers that are looking to migrate to Cloud iManage from their on-premises or iManage.Work instances. There are two main scenarios:

1. Lift and shift migration. In this type of migration, iManage metadata, user IDs, groups, document IDs, workspaces, and iManage databases remain the same. Most firms can use this method.

2. Nuanced migration. In this type of migration, customers may want to create a new database or consolidate databases, change IDs, update workspaces and/or libraries, and update metadata. In making these changes, a different migration approach is necessary for CAM to function the same way.

Lift and Shift Migration

If the information is kept as-is between the on premises or iManage.Work iManage system and the new Cloud iManage system, the firm should complete the following steps.

1. Navigate to Administration.

2. Click on External System Configuration.

3. Click on the iManage tab.

4. Click on Edit for the repository to which you wish to migrate.

5. Update the URL. The URL should be like https://servername-mobility.imanage.work for cloud systems

1. Reauthenticate by clicking on the Validate button.

2. Click on Update.

Note:  Keep all the other settings the same.

Nuanced Migration

If the firm is changing the data (e.g. matter numbers, unique metadata, metadata names or field value types) of the cloud system that differs from the on-premises/iManage.Work system, then a nuanced migration is an appropriate option rather than a lift and shift. The best option is to create a brand-new external system configuration, redo the mapping for the new database, and relink the workspaces.

1. Navigate to Administration.

2. Click on External System Configuration.

3. Click on the iManage tab.

4. Click on the +Add New Button.

5. Add the new server URL, validate it, and click

Save.

Once the new server has been configured:

1. Run the auto-discovery of metadata mapping for the Cloud iManage libraries.

2. Review/check the templates if any changes have been applied with their move from on-prem to Cloud iManage. You will have to remap the metadata for all folders.

   1. Also, any previously created metadata on a template that has the database or server configured must be modified to the new server or database. E.g., if the metadata "class” has the server and database set to the on-premise location, change to the cloud location.

3. Update/review the Data Uploader versioning and apply changes to the config.file to reflect the Cloud iManage libraries.

4. Review the Data Uploader scripts and change the server name to match the new server.

5. Update/review the workspace provisioning scripts to target the Cloud iManage libraries.

6. Update/review the Active Directory (AD) sync process to target the Cloud iManage libraries.

Note:         If databases change or get consolidated, or if any document, project, or workspaces ID change, a resync will be needed.

7. Update the Default System global setting for Service Desk under Administration>Settings.

8. Review/test workspace provisioning and AD sync before scheduling the process on a time-basis.

9. Review the Content Mover configurations and edit the systems on any content mover jobs that might be set for iManage.

10. Finally, review any policies in Control Center that are set for the iManage systems that need editing.

Note:         Re-linking of workspaces will happen automatically upon running the job. In case the firm needs to manually re-link some of the workspaces, reach out to Litera for assistance.

Caution:     Until the migration is complete, make sure the old server is still working. Once the migration is complete, stop the old server and delete it from the external system configuration. This will ensure the firm does not “accidentally” enter data in the old on-premises system.