Salesforce Decode
Salesforcedecode
Back to questions
Salesforce ArchitectureArchitect (Hardest)multi-orgsingle-orgstrategy

Design single org vs multi-org enterprise Salesforce strategy

Real World Scenario

A conglomerate acquired five companies each with Salesforce orgs. CEO asks whether to consolidate into one global org or federate.

Expected Answer

• Evaluate drivers: data residency, autonomy, release cadence, licensing, and shared processes • Single org benefits: unified customer view, lower integration tax, shared automation • Multi-org benefits: blast radius isolation, regulatory separation, acquisition speed • Hybrid: divisional orgs with Data Cloud or MDM federation for 360 view • Consolidation TCO includes data migration, retraining, and multi-year change program • Decision matrix scoring legal, operational, and technical dimensions—not religion • Exit criteria and review gate at 3 years if strategy underperforms

Follow-Up Questions & Answers

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

Main difference: use case and scale. Evaluate drivers: data residency, autonomy, release cadence, licensing, and shared processes. Single org benefits: unified customer view, lower integration tax, shared automation. Pick based on your integration pattern and team capability. Single org is not always virtuous—architects quantify federation cost honestly and revisit as business evolves. Document the decision in an ADR and align with enterprise standards.

Architect Perspective

Single org is not always virtuous—architects quantify federation cost honestly and revisit as business evolves.