A 60-person manufacturing firm headquartered in Cranberry Township came to us with a problem familiar to any operations leader in Western PA: their on-premises Exchange server was past end-of-life, two acquisitions had left them with three different email tenants, and a Department of Defense prime contractor was asking about CMMC Level 2 readiness on the next purchase order. They needed a Microsoft 365 migration in Pittsburgh that consolidated identities, preserved a decade of mailbox and file history, and ended with a tenant that could actually pass a compliance audit — not just "work."
This is the engagement we want to walk through, because it captures what most mid-market Pittsburgh buyers are really asking when they search for a Microsoft 365 migration partner. They're not buying mailboxes. They're buying a clean cutover, a defensible configuration, and someone who picks up the phone at 6 a.m. on go-live day.
The challenge
The client had roughly 60 mailboxes across the legacy Exchange box, plus 18 mailboxes in a Google Workspace tenant inherited from a 2022 acquisition in Washington County, plus a small M365 tenant a previous IT vendor had stood up for the executive team. File shares lived on two aging Windows servers in the Cranberry office, with a satellite plant in Westmoreland County reaching back over a flaky site-to-site VPN.
The constraints were specific:
- A CMMC Level 2 assessment window roughly five months out, which meant the destination tenant had to be GCC-eligible architecture with conditional access, MFA enforcement, and audit logging configured from day one.
- Zero tolerance for email downtime during business hours — the company quotes and ships daily, and a stalled inbox costs real revenue.
- Roughly 4.2 TB of file-share data, much of it engineering drawings with deep folder paths that break naive OneDrive sync tools.
- A leadership team that had been burned by a prior "lift and shift" where shared calendars, distribution groups, and public folders all silently broke.
The hard part of a Microsoft 365 migration in Pittsburgh is almost never the mailboxes — it's the identity, compliance, and file-permission work nobody quotes for upfront.
How it was solved
We ran the project in four phases over about ten weeks.
Phase 1 — Tenant design and identity. Rather than migrating into the existing executive tenant, we built a new tenant aligned to the compliance roadmap, with Entra ID Connect against a cleaned-up on-prem Active Directory. Conditional access policies, named locations for the Cranberry and Westmoreland sites, and a break-glass account were configured before a single mailbox moved. Licensing was sized to Business Premium for general staff and E5 Compliance add-ons for the engineering and finance groups handling controlled unclassified information.
Phase 2 — Mail coexistence. We staged a third-party migration platform with hybrid coexistence so that the Exchange, Google Workspace, and legacy M365 users could all free/busy each other while cutovers ran in waves of 10–15 users per night. No user lost a calendar invite or a shared mailbox during the transition.
Phase 3 — Files and Teams. The 4.2 TB of file data was assessed for path length, illegal characters, and permissions sprawl before anything moved. We migrated to a SharePoint and Teams architecture mapped to actual departments — not a one-to-one mirror of the old H: drive — and kept a read-only archive of the legacy share for 90 days as a safety net.
Phase 4 — Compliance hardening and handoff. Purview data loss prevention policies, retention labels for ITAR-adjacent engineering content, Defender for Office 365 with safe links and safe attachments, and a documented System Security Plan aligned to the NIST 800-171 controls the CMMC assessor would test against.
Outcomes
At cutover the client had a single Microsoft 365 tenant, one identity per employee, MFA on every account, and a documented control set their compliance consultant could hand directly to the C3PAO. Helpdesk ticket volume in the two weeks following go-live stayed within the normal weekly band — meaning users were not flooding us with "where did my files go" tickets, which is the real measure of a clean migration.
The Westmoreland plant, which had previously relied on the VPN to reach file shares, now worked directly against SharePoint and OneDrive, and the site-to-site tunnel was decommissioned along with two physical servers and their associated maintenance contracts.
A migration is successful when the Monday after cutover looks like an ordinary Monday.
Takeaway
TL;DR: A Microsoft 365 migration in Pittsburgh should be scoped against your compliance obligations and your identity mess, not just your mailbox count.
Most of the Microsoft 365 migration projects we get called into across Allegheny, Butler, Washington, and Westmoreland counties look structurally like this one. The industries vary — manufacturing, legal, healthcare, professional services — but the underlying pattern repeats: fragmented tenants from acquisitions, an aging on-prem footprint, a looming compliance driver (CMMC, HIPAA, the SEC cyber disclosure rules, or a cyber-insurance renewal), and a leadership team that wants the project to be boring.
If you are evaluating a Microsoft 365 migration in Pittsburgh and any of the following are true — you have more than one email tenant, you handle CUI or PHI, you have file shares older than five years, or your last migration left scars — the scoping conversation is worth having before you accept a fixed-price quote from anyone. The cheapest migration is almost always the one that gets done correctly the first time.
Talk to a Pittsburgh migration engineer
PGH Networks is based in the Pittsburgh metro and serves clients within roughly 75 miles of the city, including Cranberry Township, Monroeville, Robinson, Greensburg, and Washington. We will scope your tenant design, identity cleanup, and compliance posture before we quote the migration itself. Call us or request an assessment through pghnetworks.com to start the conversation.