{"id":1002,"date":"2025-07-15T09:00:00","date_gmt":"2025-07-15T09:00:00","guid":{"rendered":"https:\/\/admeliora.pl\/?post_type=case_study&p=1002"},"modified":"2025-07-15T09:00:00","modified_gmt":"2025-07-15T09:00:00","slug":"northwind-m365-migration","status":"publish","type":"case_study","link":"https:\/\/admeliora.pl\/?case_study=northwind-m365-migration","title":{"rendered":"Unifying two M365 tenants without downtime"},"content":{"rendered":"\n

Northwind Retail had grown by acquisition. Two business units, two cultures, two separate Microsoft 365 tenants \u2014 and a board mandate to operate as one company by year end. The IT director had been told this would be a six-week project. It was not a six-week project.<\/p>\n\n\n\n

The challenge<\/h2>\n\n\n\n

Migrating M365 tenants is technically well-documented. Migrating them without breaking the business<\/em> is a different problem entirely. Northwind had 340 mailboxes, 18 active SharePoint sites, 1,200 Teams channels, and a finance team mid-audit who could not afford a single missing email.<\/p>\n\n\n\n

Beyond the technical surface, there were cultural questions no Microsoft documentation answers: which tenant’s naming conventions win? Whose retention policies stick? How do you tell a colleague their address is changing without making them feel like the acquired one?<\/p>\n\n\n\n

Our approach<\/h2>\n\n\n\n

We split the project into four waves over twelve weeks, sequenced by business risk rather than department size. Finance moved last; their audit window was sacred. Marketing moved first; they were the most tolerant of friction and the most enthusiastic about a fresh start.<\/p>\n\n\n\n

For each wave we ran a three-step pattern: shadow week (everything mirrored, nothing live), cutover weekend (the technical move), and stabilisation week (a senior consultant embedded with the wave’s team). The shadow week was the unglamorous secret \u2014 it caught 80% of the issues before users ever saw them.<\/p>\n\n\n\n

We also wrote, for each wave, a one-page note from the IT director explaining what was changing and why. Plain language. No jargon. Signed by a human. Adoption was easier because of that page than because of any tooling.<\/p>\n\n\n\n

Results<\/h2>\n\n\n\n
    \n
  • 340 mailboxes migrated, zero data loss, zero recovered-from-backup events.<\/li>\n
  • Zero hours of business-impacting downtime across the entire project.<\/li>\n
  • All 1,200 Teams channels consolidated; 380 stale channels archived in the process.<\/li>\n
  • Audit completed on schedule with no migration-related findings.<\/li>\n
  • Project delivered two weeks ahead of the revised timeline, on the original budget.<\/li>\n<\/ul>\n\n\n\n

    Northwind now operates from a single tenant with unified governance, and the IT director has the case study printed on her office wall \u2014 which we take as the highest possible review.<\/p>\n","protected":false},"excerpt":{"rendered":"

    Two legacy tenants, two cultures, one calendar. A phased migration kept every mailbox, channel and shared file in place \u2014 and not one minute of business-impacting downtime.<\/p>\n","protected":false},"featured_media":0,"template":"","meta":[],"class_list":["post-1002","case_study","type-case_study","status-publish","hentry"],"_links":{"self":[{"href":"https:\/\/admeliora.pl\/index.php?rest_route=\/wp\/v2\/case_study\/1002","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/admeliora.pl\/index.php?rest_route=\/wp\/v2\/case_study"}],"about":[{"href":"https:\/\/admeliora.pl\/index.php?rest_route=\/wp\/v2\/types\/case_study"}],"wp:attachment":[{"href":"https:\/\/admeliora.pl\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1002"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}