Managing multiple instances of Salesforce is one scenario that a growing enterprise might encounter. Here, each Salesforce instance contains crucial business data and processes that may require consolidation. The most common situation where consolidation is required is a result of mergers and acquisitions. Aside from mergers, organizations might adopt Salesforce at varying stages of growth …
Here are highlights from article Planning a Salesforce Org Merge: Top 3 Risks to Avoid | Salesforce Ben
1. Salesforce consolidation involves merging multiple Salesforce instances into one unified organization.
– Objective is to enhance operational efficiency, data visibility, and process standardization while reducing costs.
– Can involve merging two instances or creating a completely new organization.
2. Typical Salesforce consolidation plan:
– Define business outcomes and goals.
– Create inventory of overlapping features and processes.
– Map and migrate data model.
– Plan for business continuity.
– Re-integrate or migrate processes with third-party integrations.
– Migrate and consolidate historical data.
– Test and validate the system.
3. Risk 1: Under-scoping data mapping, migration, and merging.
– Data dictionary is essential for deciding how to integrate, purge, or merge objects and records.
– Engage with stakeholders early on to consolidate input fields and plan data quality expectations.
4. Risk 2: Overlooking the importance of metrics, measurements, and reports.
– Salesforce offers reporting and dashboard functionalities, but visibility into utilization is limited.
– Alterations to metrics and reports can disrupt business management.
– Input from business stakeholders is necessary for prioritizing reports.
5. Risk 3: Insufficient planning for user training and adoption.
– Consolidation can introduce new processes and functionalities that require training and adoption by users.
– Plan for user training and provide ongoing support to ensure successful adoption of the unified Salesforce organization.
You can read it here: https://sfdc.blog/qYYqv
Source from salesforceben(dot)com