Mail is a queue of small items. SharePoint is a permissions model, and that is what makes this move different.
The bytes copy reasonably well. What consumes the schedule is deciding what the target structure should be and resolving what does not map: sharing set up ad hoc over a decade, personal permissions on individual folders, links shared with people who left, sites nobody owns any more, and Teams whose underlying groups have drifted from the team that uses them.
Copy that structure into a clean tenant and you have moved the mess rather than the content. It is also the point where a migration tool alone stops being enough, for reasons we have set out separately. Our largest single engagement moved roughly 20 TB of SharePoint alongside 4 TB of mail. The copying was not the hard part.
“We were emailing massive image files back and forth between our design and production teams. They brought that to our attention and suggested OneDrive and SharePoint. Then we noticed a great many spreadsheets and documents saved only on our internal server, with no cloud backup.”
“When some of our sales team deleted product images without understanding what they were doing, the files were retrieved within minutes and we were back up and running.”
Read-only scan of every site, library and OneDrive. Volumes, counts, owners, last activity. Orphaned and abandoned content surfaces here.
Every permission and every external link, listed. This is the stage clients find most valuable and least comfortable, because it shows who can actually see what.
The site and library structure in the destination, agreed on paper. What is consolidated, what is archived, what is left behind.
Content moves department by department while people keep working in the source. Large libraries run in the background.
A final incremental pass per wave so nothing changed after the copy is lost, then the source made read-only.
Counts and volumes compared per site, mapping document issued, users told where things are.
Volume matters less than the state of the sharing. Tell us roughly how many sites and whether anyone still owns them, and we will tell you what the review will find before it finds it.
From £800 / €950 / $1,000 · 4–8 weeksPartly, and it depends on the workload and tool. We tell you which libraries lose history before the move rather than after. Where full history is a legal requirement, we say so and the plan changes.
Anonymous links do not migrate and have to be recreated deliberately. We produce a report of every one before the move, which is usually the first time anyone in the organisation has seen that list.
Yes — the team, the Microsoft 365 group behind it, its SharePoint site, channels and files. Private and group chat history is a separate mechanism with real limits, which we state during scoping.
Four to eight weeks for a mid-sized estate. Volume matters less than the state of the permissions: a tidy 5 TB moves faster than a tangled 500 GB.
From £800 / €950 / $1,000, scaling with the number of sites and the complexity of the permissions. Fixed price, quoted after the inventory. Scoping costs nothing.
No. Content is copied while the source stays live, then an incremental pass catches anything that changed. The source is made read-only per wave, not all at once.
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.