Salesforce ArchitectureArchitect (Hardest)migrationorg-splitdata
Plan Salesforce org migration and split patterns
Real World Scenario
Divestiture requires splitting one Salesforce org into two within 6 months for legal separation.
Expected Answer
• Data classification: which records belong to retained vs divested entity
• Migration tooling: ETL extract transform load with validation reconciliation
• Metadata split: profiles flows integrations per entity ownership
• Historical data archive for shared customer relationships if any
• Cutover weekend plan with rollback criteria
• Integration rewiring both orgs post-split
• Legal review data transfer agreements and PII handling
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Data classification: which records belong to retained vs divested entity. Migration tooling: ETL extract transform load with validation reconciliation. Pick based on your integration pattern and team capability. Org split is M&A architecture specialty—start legal data classification before technical tooling. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Org split is M&A architecture specialty—start legal data classification before technical tooling.