Companies are Merged: How to Reconfigure Riva

Article ID: 389
Last updated: 10 Dec, 2018

When multiple email and CRM systems are merged together as part of a corporate merger and acquisition, the Riva CRM configuration policy needs to be adjusted for the new syncing users.

Two typical scenarios need to be supported:

  • The Riva On-Premise server is deployed to two or more companies that are being merged.
  • Users are being migrated from an environment where the Riva On-Premise server is not deployed.

Merging Different Riva On-Premise Server Environments

In this scenario, two or more companies or organizations will be merged together. Each of those environments has a unique Riva deployment that includes a set of unique email and CRM connections and a Riva license. Under these circumstances:

  • Source environment: Includes the email system and CRM connections, the CRM sync policy, and the corresponding Riva license for that environment. The source environment is where syncing user accounts are being migrated from. Eventually, the source environment and the corresponding Riva deployment will be permanently dismantled.

  • Target environment: Includes the email system and CRM connections, the CRM sync policy, and the corresponding Riva license for that environment. The target environment is where syncing user accounts are being migrated to.

The major concerns with this scenario involve transferring the license counts for the source environment to the target environment Riva server deployment. We recommend contacting the Riva Success Team and engaging in a project to ensure a smooth transition of licenses between the affected Riva deployments.

For detailed instructions to correctly migrate users between Riva deployments, see Migrating between Exchange systems or services: how to reconfigure Riva.

Migrating Users from Non-Riva Environments

In this scenario, two or more companies or organizations will be merged together. None of the source environments has a Riva deployment for the users. In this scenario, the users are considered as new accounts to the target environment.

  • Source environment: Includes the email system and CRM services that host the user accounts. The Source environment is where syncing user accounts are being migrated from. There is no source Riva server deployment to manage or dismantle.

  • Target environment: includes the email system and CRM connections, the CRM sync policy, and the corresponding Riva license for that environment. The target environment is where user accounts are being migrated to.

The major concern with this scenario involves increasing the license counts in the target Riva server deployment. We recommend contacting the Riva Success Team and engaging in a project to ensure a smooth upgrade to existing licenses for the target Riva server deployment.

For detailed instructions to correctly migrate users from non-Riva source environments, see Adding users to an existing Riva On-Premise server.



Article ID: 389
Last updated: 10 Dec, 2018
Revision: 5
Views: 6115
Also read
item How to Rename Users in Riva Sync Policies when Email Domain Names Change
item Add Users to an Existing Riva Sync Policy
item Migrating Users from GroupWise to Exchange: How to Reconfigure Riva

Prev     Next
Modify a Riva Sync Policy to Change the Email Domain Name       Planning for Exchange System Changes: How to Reconfigure the...


Back to Top