Single org = one Salesforce instance for the entire enterprise. Multi-org = separate orgs, often by region, business unit, or regulatory boundary.
Reasons to favor single org:
- Unified customer view — one Account record per customer across all touchpoints.
- Simpler licensing — fewer Salesforce contracts.
- Lower integration overhead — most workflows happen in-org, not cross-org.
- Easier reporting — one place for analytics.
- Simpler governance — one set of standards, one CoE.
Reasons to favor multi-org:
- Regulatory — financial services where one division can't share data with another by law.
- Data residency — EU data must stay in EU; create EU org.
- M&A — newly acquired company on its own Salesforce, not worth migrating.
- Independent business units — autonomous BU with completely different processes.
- Performance / scale — extreme transaction volume splits across orgs.
- Risk isolation — one org's outage doesn't affect another.
Hybrid patterns:
Hub-and-spoke:
- Central org as source of truth.
- Spoke orgs for specific BUs / regions.
- Mulesoft connects them.
- Hybrid of single-org consistency and multi-org flexibility.
Federation via SSO:
- Multiple orgs, single user login experience via SSO.
- Cross-org reporting via Data Cloud / Snowflake.
Cross-org features:
- Salesforce-to-Salesforce — built-in cross-org connector. Limited but free.
- Mulesoft / iPaaS — for serious cross-org orchestration.
- Heroku Connect — for sync to Postgres/data warehouse.
- Data Cloud — unifies customer data across orgs.
Decision criteria:
| Factor | Favors Single | Favors Multi | |---|---|---| | Regulatory split | No | Yes | | Data residency | No | Yes | | Independent BUs | No | Yes | | Customer is shared | Yes | No | | Single-source-of-truth needed | Yes | No | | Licensing budget | Yes | No | | Outage isolation needed | No | Yes |
Common pitfalls:
- Defaulting to multi-org because that's how the company is structured. Sometimes single-org would work fine; multi-org is just inherited complexity.
- Defaulting to single-org in regulated industries — sometimes you legally can't.
- Underestimating multi-org cost — every cross-org integration is engineering work.
Senior architect insight: multi-org is a one-way street. Once split, very hard to merge back. Be sure before committing.
Many enterprise orgs evolve from single -> multi after acquisitions. Plan for that evolution rather than assuming single forever.