Group of trading companies · 2025
Microsoft 365 migration for a multi-entity group
An illustrative example of consolidating several companies onto a properly structured Microsoft 365 tenant — with correct licensing, MFA and clean multi-domain mail flow.
Placeholder case study — replace with a real, permissioned write-up.
Illustrative example. This is placeholder content, not a real client project. Replace it with a real, permissioned case study before launch. See
README.mdfor how to add or edit a case study.
The situation
A group running several trading entities each had its own email accounts, scattered across a mix of providers and mailboxes. Staff shared logins, there was no MFA, and there was no reliable way to know who had access to what. Licensing had accumulated ad hoc and nobody could say whether it was correct.
What we did
- Mapped the existing domains, mailboxes, aliases and groups before touching anything
- Designed a single tenant structure covering the group and its entities
- Migrated mail, calendars and contacts with minimal downtime
- Configured Exchange Online, SharePoint, OneDrive and Teams
- Enforced MFA and conditional access, and retired legacy protocols
- Reviewed and right-sized licensing
- Documented the environment and handed it over with admin training
The outcome
The illustrative figures below show the shape of the improvement a migration like this typically delivers. Replace with real, measured results.
- [PLACEHOLDER: number of mailboxes / entities migrated]
- [PLACEHOLDER: sign-in security coverage, e.g. MFA enforced for all users]
- [PLACEHOLDER: licensing cost change]
- [PLACEHOLDER: migration downtime experienced by staff]