Salesforce Decode
Salesforcedecode
Back to questions
Salesforce ArchitectureArchitect (Hardest)post-acquisitionmulti-orgconsolidation

Design federated master org pattern for post-acquisition Salesforce consolidation

Real World Scenario

Private equity portfolio company acquires four SaaS firms each with Salesforce org; board wants unified pipeline reporting in 120 days without full org merge.

Expected Answer

• Designate master org or Data Cloud hub for consolidated reporting not transactional merge day one • CDC or replication feeds acquired orgs to warehouse with OrgId dimension • Harmonize Opportunity stage picklist and currency before cross-org dashboard • Retain acquired org autonomy for local sales process 18-month transition • Integration CoE owns cross-org API standards and identity mapping • Executive dashboard read-only federated; write stays local org • Phase 3 optional org merge decision gate with TCO analysis

Follow-Up Questions & Answers

Click to expand — each follow-up includes a direct, interview-ready answer

Main difference: use case and scale. Designate master org or Data Cloud hub for consolidated reporting not transactional merge day one. CDC or replication feeds acquired orgs to warehouse with OrgId dimension. Pick based on your integration pattern and team capability. Post-acquisition federation buys time—forced single org day 90 destroys acquired sales velocity. Document the decision in an ADR and align with enterprise standards.

Architect Perspective

Post-acquisition federation buys time—forced single org day 90 destroys acquired sales velocity.