Google Workspace and Zoom to Microsoft 365 Migration
CompleteOverview
Oversaw the company-wide transition from Google Workspace and Zoom to Microsoft 365 and Teams across US and Canadian offices — the user migration, the room licensing, and the physical conference room hardware that had to change with it.
Problem
The company ran split collaboration tooling: Google Workspace for productivity, Zoom for meetings and conference rooms. Consolidating onto Microsoft 365 meant more than a mailbox cutover — every conference room was Zoom-native hardware with Zoom licensing, and the rooms are what people notice. A migration can be technically complete and still be judged a failure if a leadership meeting cannot start on Monday morning.
The hardest single case was the largest event space, a divisible room with audio DSP and room-splitting capability, which was the most complex conference room in the company.
Approach
Ran the migration as a user track and a room track in parallel. The user track handled provisioning and licensing; the room track handled Teams Rooms licensing, hardware reconfiguration, and validation room by room rather than as a bulk cutover.
Rooms were converted and tested individually — a room only moved when it had been verified working, so at no point was there a floor of rooms in an unknown state. I handled deployment and validation directly for the local office and supported troubleshooting for headquarters rooms remotely.
The large divisible space was treated as its own mini-project because of the DSP and room-splitting behavior, which had to keep working across the platform change rather than being rebuilt after it.
Architecture
Identity and productivity consolidated into Microsoft 365. Meeting rooms moved to Teams Rooms with per-room licensing, retaining existing audio infrastructure where it could be repointed and reconfiguring where it could not. Room-splitting and DSP behavior in the large event space was preserved through the transition rather than reintroduced afterward.
Outcome
The cross-border migration completed with minimal operational disruption, unifying collaboration tooling across the organization. Conference rooms — including the most complex room in the company — came out the far side working, and I stayed the primary liaison for those systems afterward, maintaining 99% uptime and resolving 95% of critical issues within one hour.
Lessons Learned
In a collaboration migration, the mailboxes are the easy part. The rooms are what determine whether people believe the migration worked, because a broken room fails loudly in front of an audience that includes leadership. Sequencing room-by-room with verification gates cost more time up front and bought the entire project its reputation.