Skip to content

SharePoint migration

SharePoint migrations, planned properly.

We migrate organisations to SharePoint Online from on-premise SharePoint, file shares, other tenants, Lotus Notes and Google Workspace, with minimal downtime. Each migration runs as a structured project, with an audit, a target architecture, a pilot and validation before go-live.

Related services

Migration services and guides.

The right approach depends on where you are moving from and why. These pages cover the scenarios we see most.

Intranet migration

Moving your intranet off an older platform, with the content reviewed on the way.

Intranet migration

Classic SharePoint end of life

What the 2026 retirement of Add-Ins, ACS and 2013 workflows means and how to replace them.

Classic end of life

ShareGate

The migration tool we use for complex SharePoint Server moves with granular permissions and large volumes.

ShareGate

SharePoint Server 2016 and 2019

End of support on 14 July 2026, and the options for moving on.

Server end of support

SharePoint governance

Permissions and ownership designed for the new environment before content arrives.

SharePoint governance

End to end intranet migration

A full intranet move covering audit, design, migration and launch.

End to end migration

4 to 6 weeks

for a straightforward migration under 500 users

6 to 10 weeks

for 500 to 5,000 users with some customisations

10 to 16 weeks

for 5,000+ users and complex environments

How we work

How a SharePoint migration runs.

01

Discovery

We audit your source environment with automated scanning and manual review, covering content volume, site structure, customisations, permissions and content that no longer needs to move.
02

Design

The target information architecture in SharePoint Online: hub sites, libraries, metadata and permissions, with every source location mapped to a destination and a remediation plan for custom solutions.
03

Build

A pilot migration of a representative sample, validated by your key users, followed by the full migration in scheduled batches with validation checks after each one.
04

Train

Training for your people on the new environment, so they know where things are and how to work in modern SharePoint.
05

Go live

We check document counts, metadata, permissions, broken links and search results, then support your people through go-live.

Client feedback

What it is like to work with us.

“The migration went very smoothly, and our new intranet ensures our data is secure and easily accessible.”

George IrvineHead of IT, CitNOW

“ThinkShare were a delight to work with and supported us every step of the way with great client service and strong technical expertise.”

Grace TimperleyInternal Communications & Engagement Specialist, Shelter

Case studies

Case studies we have delivered.

A smooth migration

CitNOW's data was migrated from the old setup into a SharePoint intranet and document management system so dispersed teams can find and co-author work, and the migration went smoothly.

Read the CitNOW case study

File server to Teams and SharePoint

Praxis moved its file server into Teams and SharePoint, with a Team per business function and the data cleansed and reorganised on the way.

Read the Praxis case study

2016 SharePoint to modern

Shelter moved from a 2016 SharePoint intranet to modern SharePoint, mostly out of the box, with retention labels and policies.

Read the Shelter case study

FAQ

Frequently asked questions.

How long does a SharePoint migration take?

As a guide, 4 to 6 weeks for organisations under 500 users with straightforward content, 6 to 10 weeks for 500 to 5,000 users with some customisations, and 10 to 16 weeks for 5,000+ users, sometimes phased by business unit.

Which migration tools do you use?

Microsoft SPMT for straightforward migrations, ShareGate for complex SharePoint Server moves with granular permissions and large volumes, and custom PowerShell or Graph API scripting for non-SharePoint sources. We recommend the tool, or combination, during scoping.

What happens to our custom solutions?

Farm and sandbox solutions do not work in SharePoint Online. We audit each one and recommend replacing it with native features, rebuilding it in SPFx or converting it to Power Platform.

Will our users be disrupted?

The full migration runs in scheduled batches, typically over evenings and weekends, with validation after each batch and rollback procedures in place.

Talk to our migration team.

Tell us what you are working on and we will come back to you within one working day to arrange a call.