Salesforce ArchitectureArchitect (Hardest)post-acquisitiondivestituredata
Plan post-acquisition divestiture Salesforce data separation architecture
Real World Scenario
Spin-off business unit must exit parent Salesforce org in 9 months with clean data separation for buyer due diligence.
Expected Answer
• Data classification records belonging to divested entity legal sign-off
• Extract ETL divested subset to new org or buyer org
• Shared customer split survivorship rules documented
• Metadata clone strip parent-specific integrations flows
• Historical archive shared accounts contractually defined
• Cutover freeze weekend validation reconciliation
• Integration rewire parent org remove divested references
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Data classification records belonging to divested entity legal sign-off. Extract ETL divested subset to new org or buyer org. Pick based on your integration pattern and team capability. Divestiture is org split architecture—start legal data classification before ETL tooling. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
Divestiture is org split architecture—start legal data classification before ETL tooling.