Implementation

SharePoint Migration

Move off shared drives, Box, Dropbox, or SharePoint 2016/2019, and arrive with a structure people can find things in, and that Copilot can be trusted with.

Talk to us about your project
SharePointMicrosoft 365Microsoft TeamsMicrosoft Copilot

Kumo's SharePoint migration services move your content off shared drives, Box, Dropbox, or older SharePoint and into Microsoft 365, restructured on the way in. The migration is where content gets owners, sensitive material gets a real permission model, and metadata gets applied, while every file is already in hand.

12,000+

SharePoint sites migrated

40+ TB

of documents moved into Microsoft 365

3

single migrations of 4,000 to 5,000 sites each

150,000+

users working in SharePoint we have migrated or built

Who it's for

A good fit if…

  • Your documents live on a network file share, Box, or Dropbox, and nobody can explain the folder structure anymore.
  • You still run SharePoint Server 2016 or 2019, which stopped receiving security updates on July 14, 2026.
  • You are rolling out Copilot and need permissions you can account for before it starts answering.
What you get

You walk away with

  • Your content moved into SharePoint in Microsoft 365, cleaned, with duplicates resolved.
  • A site, hub, and Teams structure people can navigate.
  • Owners, metadata, and a permission model you can explain, applied during the move.
  • Training aimed at how your teams actually work, so the new structure gets used.
Value

Why it matters

The cheapest moment to fix it

Every file is being touched anyway. Restructuring during the move costs far less than cleaning up after it.

Copilot inherits what you move

Open folders and stale duplicates become confident wrong answers. A permission model you can explain prevents that.

Approach

How it works

1

Inventory what you have

Sources, volume, owners, permissions, and the duplicates and dead folders nobody claims.

2

Design where it goes

Site and hub structure, Teams and channels, metadata, and the permission model, settled first.

3

Plan the move

The sequence, what is restructured on the way in, and how people are brought along.

4

Migrate and adopt

Content moves cleaned, tagged, owned, and permissioned, with training aimed at the work.

Inside the build

What it actually looks like

Screenshots from production work Kumo built and runs. Client branding and customer data are redacted.

A research hub for a healthcare organization: reports that used to sit in folders, now one search away. Client details are blurred.
Metadata applied during the migration powers the filters: 167 reports narrowed by region and research category.
The deeper read

What we migrate from

Network file shares. The most common starting point: deep folder trees, inherited permissions, and no clear owner. We map them to sites and libraries people can navigate.

Box and Dropbox. Usually adopted team by team, so sharing links and folder conventions differ everywhere. We bring them into one structure and one permission model.

SharePoint Server 2016 and 2019. No longer supported after July 14, 2026. We move the farm to SharePoint in Microsoft 365 and use the move to retire what nobody uses.

Third-party intranet platforms. News, pages, and departmental content moved onto a SharePoint intranet your communications team can run.

Not ready to commit? Start with a SharePoint migration assessment and get a scoped plan first.

FAQ

Questions we hear a lot

Is SharePoint Server 2016 or 2019 still supported?

No. Both reached end of support on July 14, 2026 and no longer receive security updates. SharePoint in Microsoft 365 is where Microsoft is investing, and moving there is where many of the migrations we run today begin.

Why not just move everything as it is?

Because the same folder chaos arrives at a new address, and Copilot then answers from it. Moving as-is skips the one moment when fixing ownership, permissions, and duplicates is cheap.

Do you take on smaller migrations?

Yes. We move teams of ten as well as large enterprises. Scale changes the governance and rollout plan, not the approach.

Ready to start?

Off shared drives, Box, Dropbox, or SharePoint 2016/2019, restructured on the way in instead of just relocated.

Talk to us about your project
Also under this capability

More from SharePoint & Modern Work

Assessment · 2 to 4 weeksWays to startSharePoint Migration AssessmentAn inventory of your content and permissions, a target SharePoint structure, and a migration plan your leadership can decide from.Scoped on a callSee the engagement →
← Back to SharePoint & Modern Work