Short answer
Salesforce org consolidation merges data, users and configuration from two or more Salesforce orgs into one, usually after a merger, acquisition or reorganization. It gives the combined firm one client view, one set of processes and one reporting model.
Why firms make this move
After an acquisition, running separate orgs doubles license, admin and integration costs and makes combined reporting hard. Consolidation requires deciding which org's design wins, how to merge overlapping clients, and how to keep regulated data separated where it must be.
What moves
- Accounts, households and contacts, deduplicated across orgs
- Opportunities, cases and activity history
- Custom objects and configuration from the source org
- Users, roles and sharing
- Integrations re-pointed to the target org
What to watch out for
- Overlapping clients and conflicting data
- Different data models for the same concepts
- Information barriers between business units
- Integrations and reports in both orgs
How Vantage Point runs the migration
- Assess both orgs and choose the target design
- Plan deduplication and survivorship rules
- Map and transform data
- Migrate configuration and automation
- Test loads and UAT
- Cutover by business unit
- Hypercare
Typical timeline
Typically 10 to 20 weeks, depending on org complexity.
Frequently asked questions
Should we merge orgs or keep them separate?
Merge when teams share clients, processes and reporting. Keep separate when regulatory or business separation requires it, and connect the orgs instead.
How are duplicate clients handled?
With matching rules and survivorship policies agreed with the business, so the best data from each org is kept.