Salesforce ArchitectureArchitect (Hardest)post-acquisitionconsolidationmulti-org
Architect Salesforce org consolidation wave planning for acquired subsidiaries
Real World Scenario
Five acquired orgs over 3 years; program office wants wave plan minimizing sales disruption and integration cost.
Expected Answer
• Wave criteria: regulatory compatibility data quality integration complexity
• Wave 1 smallest org pilot lessons learned
• Parallel run 90 days federated reporting before cutover
• User training wave-specific change champions
• Integration remapping per wave not big-bang all interfaces
• Rollback criteria per wave executive pre-approved
• License optimization post-wave true-up
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Direct answer: Wave criteria: regulatory compatibility data quality integration complexity Also consider: Wave 1 smallest org pilot lessons learned In practice: Parallel run 90 days federated reporting before cutover Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Consolidation waves reduce blast radius—pilot wave mandatory before acquiring org 2 through 5.