Ascension Technologies · Collaboration Migration
Google Workspace Migration
Supported users through a migration from Microsoft mail and collaboration to Google Workspace, focusing on onboarding, access provisioning, and adoption so that continuity held across mail, drive, and collaboration.
01
Context
Ascension Technologies was moving users off Microsoft mail and collaboration onto Google Workspace. Migrations of this kind succeed or fail on adoption — the technical cutover is only half the work.
02
Challenge
Move users to Google Workspace without losing productivity, with a mixed audience that had years of Microsoft habits, and provide the guidance needed for adoption to actually stick.
03
My role
Migration support technician handling onboarding, access, and adoption reinforcement during the transition window.
04
What I did
- Onboarded users to Google Workspace and provisioned account access.
- Oriented users to the collaboration tools they would use day to day.
- Triaged migration issues as they surfaced and routed them to resolution.
- Reinforced adoption with clear, task-focused guidance.
05
Workflow / approach
- 01
Provision account access
Confirm the user's Google Workspace identity and access.
- 02
Orient on core tools
Walk through mail, drive, and collaboration equivalents to what the user had in Microsoft.
- 03
Triage migration issues
Handle mail, calendar, and file continuity issues as they appear.
- 04
Reinforce adoption
Answer the day-two questions that decide whether the migration sticks.
06
Outcome and value
The migration held because users were supported through the adoption curve, not just the cutover. Mail, drive, and collaboration continued to work for the people who depend on them.
07
What this demonstrates
- Ability to support a platform change across an established user base.
- Cross-ecosystem fluency between Microsoft 365 and Google Workspace.
- Focus on adoption, not just cutover.
08