Projects and migrations
On-Premises to Microsoft 365
Email, files and identity moved off your own servers and into Microsoft 365 — including the part most migrations skip, which is deciding what does not come with you.
What the work involves
- An audit of mailboxes, file shares and who actually uses what.
- Deciding what migrates, what gets archived, and what is simply switched off.
- An identity decision: synchronise with your existing directory, or move to cloud-only.
- Mailbox migration, staged or in one cutover depending on size and tolerance for disruption.
- File shares into SharePoint and OneDrive, with the folder structure reconsidered rather than copied.
- Decommissioning the old servers, deliberately, once nothing depends on them.
What it depends on
Mailbox count and size set the timeline for the mail half. File shares set it for everything else, and they are usually the messier of the two.
Whether you keep an on-premises directory changes the shape of the whole project. Cloud-only is simpler and is not available to everyone.
Commonly underestimated
Permissions on file shares. Years of ad-hoc access grants do not map cleanly to SharePoint, and lifting them across unexamined recreates a mess in a new place.
PST files. They are scattered across desktops, they contain things people need, and nobody has an inventory of them.
The server nobody documented that turns out to be doing something important. There is almost always one.
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.
-
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.
-
Google Workspace to Microsoft 365
Mail, drive and identity moved across from Google, with the shared-drive structure mapped properly instead of dumped into someone's OneDrive.
Talk it through
Tell us what you're moving and what you're moving it from. Twenty minutes, no obligation.
Schedule a call