Projects and migrations
Google Workspace to Microsoft 365
Mail, Drive and identity moved across from Google — with the shared-drive structure mapped deliberately rather than emptied into whoever ran the migration.
What the work involves
- An inventory of users, shared drives, and how sharing is actually being used.
- Mapping identities, including the accounts that turn out to belong to people who left.
- Migrating mail, calendars and contacts.
- Moving Drive content into SharePoint and OneDrive, with shared drives mapped to a structure that makes sense in Microsoft 365.
- Cutting over mail routing, and keeping a route back until it is proven.
What it depends on
User count sets the mail timeline. Drive volume and how tangled the sharing is set everything else, and the second one is harder to estimate from the outside.
Commonly underestimated
Shared drives do not map one-to-one onto anything in Microsoft 365. Deciding what becomes a SharePoint site, what becomes a Team, and what should simply not survive is a business conversation, not a technical one.
Sharing links. Google links scattered through years of email and documents stop working, and there is no clean way to rewrite them.
Native Google formats. Docs, Sheets and Slides convert imperfectly, and anything with heavy formatting or scripts needs checking rather than assuming.
How we scope this
We do not quote this work before seeing your environment. How long it takes and what it costs depend on what you already have, how much of it there is, and how quickly your side can make decisions — and a number produced without knowing those is a guess you would end up budgeting against.
What we will commit to is a start: work begins within five business days of signature. If a particular engagement cannot start inside that window, we say so before you sign.
More on this in what it costs. Ongoing support for this sits under our services.
Other projects
-
Azure Virtual Desktop
A full Windows desktop delivered from Azure, so staff get the same environment from any device, anywhere, and it stays under your control rather than living on a laptop. Access is built on identity and conditional access rather than a VPN nobody wants to use.
-
On-Premises to Microsoft 365
Email, files and identity moved off your own servers into Microsoft 365, including the part most migrations underestimate — deciding what does not come with you.
-
Microsoft 365 Commercial to GCC High
The migration a defense contractor makes when CUI enters the picture. It is a tenant-to-tenant move, not an upgrade, and the CUI boundary has to be designed before anything is copied.
Talk it through
Tell us what you're moving and what you're moving it from. Twenty minutes, no obligation.
Schedule a call