SharePoint migration services cover everything around moving your content and processes to SharePoint Online or a newer SharePoint: assessment, planning, rebuilding what will not move, the migration itself, and support afterwards. This guide explains what a good service includes, what drives the cost, and what to ask before you choose a partner.
What a migration service should include
- Assessment: a scan of sites, libraries, sizes, permissions and customisations, so there are no surprises.
- Plan: what moves, what is archived, what is retired, and in which order.
- Rebuild: InfoPath forms, old workflows and custom code that cannot be moved as they are, rebuilt in Power Apps, Power Automate or the SharePoint Framework.
- Migration: a pilot first, then waves, with checks after each one.
- Cutover and support: user communication, short training and a period of support after go-live.
What you can migrate from
- Older SharePoint versions. Support for 2016 and 2019 ended on 14 July 2026, so these moves are now urgent. See our 90-day plan and the 2013 and 2016 strategy.
- File servers and shared drives. Covered in our file server migration guide.
- Other platforms, such as IBM Lotus Notes or Google Drive.
What drives cost and time
- Data volume and the number of sites and libraries.
- How much of it is still in use. Cleaning up before migration reduces both cost and risk.
- The number of customisations, forms and workflows that need rebuilding.
- Permission complexity, especially broken inheritance and very large groups.
- Compliance requirements, such as retention and audit rules.
Our cost and timeline guide goes into these drivers in more detail.
Questions to ask a migration partner
- Will you assess our environment before you quote, and share the findings?
- How do you handle InfoPath forms, old workflows and custom code?
- Do you run a pilot, and what happens if it shows a problem?
- How do you keep permissions correct during and after the move?
- What support do users get after go-live, and for how long?
- Who will do the work, and can we speak to a client who has been through a similar move?
Read how we run these projects on our SharePoint migration page.
Planning a SharePoint migration?
Share what you run today and we will review your environment and recommend a route, a timeline and a first wave.
Book a free reviewFrequently asked questions
How long does a SharePoint migration take?
It depends on size and customisation. A focused first wave can go live in a few weeks, while large environments typically take several months.
Will our users lose anything?
Not if the plan includes checks. We verify file counts, permissions and key metadata after each wave, and keep the old source read-only until you sign off.
Can we migrate in stages?
Yes, and it is usually the safest route. Start with a pilot team, then move departments in waves.
Do we need a tool or a service?
Free tools such as the SharePoint Migration Tool cover simple file moves. A service helps when you have customisations, complex permissions or a deadline.
You may also like

SharePoint 2016 and 2019 support ended on 14 July 2026. See the risks, your three options and a 90-day plan to migrate or modernise.

Learn what impacts SharePoint Online migration cost and timeline for enterprises. Understand key factors before moving to SharePoint Online.

Plan your SharePoint 2013 to Online migration with a structured strategy. Learn risks of legacy systems, upgrade steps.

SharePoint Online content management powers 60% of Fortune 500 companies.Learn why enterprises migrate from legacy systems.
