Business Applications · Restoration Services · Deployment · 2025
One CRM Across a Parent Company and Its New Subsidiary
A restoration business and its newly formed subsidiary
The challenge
The parent business wanted a real CRM rather than a shared inbox and a spreadsheet, and its newly formed subsidiary needed the same thing — except the subsidiary had no Microsoft tenant at all. Meanwhile the customer records both would need already existed inside the accounting system.
Where we came in
Two companies, one customer list, and a temptation to run the subsidiary as a department of the parent. Keeping the tenants separate costs a little more at setup and avoids the far more expensive untangling later, so we stood the subsidiary up properly while sourcing both CRMs from the same accounting data.
What we did
- Deployed Microsoft Sales Hub to the parent business
- Provisioned a full Microsoft 365 tenant for the subsidiary and migrated its domain
- Deployed Sales Hub to the subsidiary as a separate environment
- Migrated existing customer data out of the accounting system into both CRMs so neither started empty
Where it landed
- Both companies run Sales Hub, each in its own tenant
- Both CRMs were seeded from existing accounting records rather than requiring re-entry
- The subsidiary has its own identity and mail domain rather than operating inside the parent's
Technologies
- Dynamics 365 Sales Hub
- Business Central
- Microsoft 365
Delivered and closed out in our project management system. Outcomes describe the resulting state — we have not published a measured before-and-after for this engagement.
Back to all projects