Salesforce ArchitectureArchitect (Hardest)post-acquisitionm-and-aharmonization
Design post-merger Salesforce org harmonization playbook for 100-day integration
Real World Scenario
Merger integration office mandates 100-day Salesforce harmonization between two $500M revenue sales organizations.
Expected Answer
• Day 1-30: inventory orgs users integrations data volume license
• Day 31-60: harmonize lead opportunity account definitions cross-company
• Day 61-90: federated reporting pipeline visibility both orgs
• Day 91-100: quick-win unified SSO and shared integration patterns
• Defer full org merge until year 2 unless regulatory requires
• Retain acquired brand Experience Cloud sites interim
• Weekly steering committee architecture blockers escalated
Follow-Up Questions & Answers
Click to expand — each follow-up includes a direct, interview-ready answer
Main difference: use case and scale. Day 1-30: inventory orgs users integrations data volume license. Day 31-60: harmonize lead opportunity account definitions cross-company. Pick based on your integration pattern and team capability. 100-day playbook sets expectations—full harmonization is multi-year; report federated wins early. Document the decision in an ADR and align with enterprise standards.
Architect Perspective
100-day playbook sets expectations—full harmonization is multi-year; report federated wins early.