Migrate Collect workspaces

When you migrate a Collect workspace, using Archive, Restore, and Migrate (ARM) or Integration Points, Relativity moves workspace data but does not move data source credentials.

After the migration, you must re-enter credentials before you can run Collect jobs.

This behavior applies to all Collect data sources.

Migrate Collect workspaces

You can migrate Collect workspaces using ARM or Integration Points.

During a migration:

• Relativity restores the Collect workspace and its objects.
• Relativity does not restore data source credentials.
• Data sources appear in the restored workspace but are not connected.

Relativity does not provide a supported way to move or copy Collect credentials. This protects sensitive authentication information.

Credentials do not migrate

To protect from compromising sensitive authentication information, Relativity does not support moving or copying Collect credentials from migration.

After migration

Until you re-enter credentials, Collect cannot access the data sources.

After a migration:

• Data sources appear in the restored workspace.
  • The credentials will not work.
  • The connections are invalidated.
• You must re-enter the credentials for each data source and revalidate each data source.
• New collection jobs cannot be run until the data sources are connected again.

Considerations

Consider the following when using Microsoft or Google:

• Microsoft 365—the app created for Microsoft 365 data sources has a secret value which is only exposed on initial creation.
  • This secret value must be stored and re-entered correctly for the data source to work.
  • If the Secret Value is forgotten, please generate a new secret value.

• Google—for Google data sources, a refresh token is generated on the first Google data source that was set-up and used for subsequent Google data sources.

  • This refresh token value must be stored and re-entered in the data sources in order for the data sources to work.
  • If the token is invalidated or forgotten, please see Troubleshooting for instruction on generating a new refresh token.