Moving from Google Workspace to Microsoft 365 is two projects wearing one name. The first is the data: mail, Drive, shared drives, calendars and contacts. That part is mechanical.
The second is the sharing model, and the two platforms do not agree. Google Drive is built around per-file permissions and links; SharePoint is built around sites and inheritance. A folder shared with “anyone with the link” has no clean Microsoft equivalent. A file owned by an individual in Drive may need to become a document in a site with a completely different owner.
Decide that mapping before the move and the migration is boring, which is the objective. Decide it afterwards and you have recreated Google’s model badly inside Microsoft 365, which is the outcome we are usually called in to unpick.
“They created an environment for what I would call a left-seat, right-seat transition. We were still running on Google and still operating as a company while we moved across. Downtime was minimal — including moving our phone systems over, which our guests never noticed.”
“We made some mistakes as a company, because it was the first time we had done a migration like this. IT Partner helped us formulate a better system for how we store our data in SharePoint. There was no downtime at all, and it was seamless. They were on it — we were never delayed.”
Read-only assessment of the Workspace tenant: users, volumes, groups, shared drives and every external sharing relationship.
The stage that decides whether this project is easy or painful. Each Google sharing pattern gets a Microsoft 365 equivalent, agreed with you.
Microsoft 365 tenant prepared: users, licences, groups, sites and libraries built to the agreed structure.
Content moves while people keep working in Workspace. Large Drives run in the background.
Domain moved, MX and autodiscover repointed, Workspace made read-only.
Incremental pass for anything that arrived during the window, plus elevated support for the first working week.
Tell us the user count and roughly how much sits in shared drives. You get back the sharing questions that need deciding, the realistic window, and a fixed price.
From £800 / €950 / $1,000 · 3–8 weeks“We had been constantly battling with Google: running out of space, emails mysteriously disappearing, archiving that never freed up enough room. Every email we tracked was brought across, and we did not lose any of our archives. Since we converted, not a single person has had an issue with email — and we are saving money each month.”
“I have been in apparel for over thirty years and done seven or eight system conversions. There is always an issue. This was by far the easiest exercise I have ever gone through.”
Yes, Docs, Sheets and Slides convert to Office formats. Simple documents convert cleanly; complex ones can shift in layout. We sample the complicated ones during scoping so nobody is surprised.
They are listed and decided individually. Microsoft 365 can approximate the behaviour, but the security posture is different, so this is a conscious choice rather than an automatic translation. Most organisations use the move to retire links they did not know existed.
They map to folders, with a rule agreed beforehand. Because a message can carry several labels but live in only one folder, some information is lost by definition. The rule is decided rather than discovered.
Three to four weeks for under 25 users. Four to eight weeks for 25 to 100. Two to three months for a few hundred. The sharing model review, not the data volume, is what varies most.
From £800 / €950 / $1,000, scaling per user. Fixed price after the inventory, and scoping costs nothing.
Yes, and most do. Coexistence during the transition covers mail routing and free/busy. It is transitional by design; the plan states what works across the boundary and what waits for cutover.
Scoping costs nothing
Answer the form or write to us. You get back a written scope, a sequence and a fixed price — usually within one business day, and nobody rings you unless you ask.