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:
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:
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.
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