Skip to content

SharePoint and Microsoft 365 migration

SharePoint and Microsoft 365 migration for file servers and older SharePoint sites, with permissions sorted out before anything moves.

We move file servers and older SharePoint sites into SharePoint Online and Microsoft Teams, and personal files into OneDrive. Before anything moves, we find out who can open what and agree the new structure with your teams. Content nobody uses is archived instead of copied, so people can find their files after the move. Because the permissions are fixed first, Microsoft Copilot shows each person only what they should see.

200+ production deployments on AI and the Microsoft platform since 2014

The problem

What goes wrong when files are copied as they are.

Permissions nobody can explain

Years of folder permissions granted to individuals and to everyone in the company. Copied unchanged, the same oversharing lands in SharePoint, where search and Copilot can surface it.

Files nobody uses

Duplicates, old versions and folders from projects that ended long ago. Moving them takes time and makes search worse for everyone.

Folders shaped like an old org chart

Top-level folders often follow departments that no longer exist, and people find files by remembering where a colleague once saved them.

Customizations that will not move

Classic workflows, InfoPath forms, farm solutions and custom web parts built for older SharePoint versions need a decision to rebuild or retire. They do not carry over as they are.

In plain words

What a Microsoft 365 migration involves.

A migration moves your company's files and sites from servers you run into Microsoft 365. Files a team works on together go to a SharePoint site, which can sit behind the team in Microsoft Teams. Files that belong to one person go to that person's OneDrive. Sites from older SharePoint versions move to SharePoint Online.

Copying the files is the easy part. Most of the work is deciding what to move and who should see it, then helping people get used to the new place. On the Rockwell Automation intranet program the technical migration was straightforward, while content curation and migration decisions took significant effort and stakeholder alignment.

How it runs

How a migration runs.

Each step ends with a decision your team signs off before the next one starts.

  1. Before the move

    Inventory

    We list what sits on each file server and site, who owns it, who can open it and when it was last used. Usage data shows what people still work with.

  2. Before the move

    Clean up

    With each owner we decide what moves, what goes to an archive and what is deleted. On the Rockwell Automation program only high-value content moved, and outdated material was archived.

  3. Before the move

    Design

    We agree the new sites and hubs with your teams, organized around how people work instead of the org chart, with content types, metadata and retention policies where they help.

  4. Before the move

    Permissions

    Old permissions are mapped to SharePoint groups, and sharing with the whole company is removed where it does not belong. For Burckhardt Compression we mapped SAP authorization profiles to SharePoint security groups.

  5. First department

    Pilot

    One department moves first and works in the new sites while the old location stays available. At Burckhardt Compression the engineering department piloted the new route alongside SAP.

  6. Rest of the company

    Move in waves

    The rest of the company moves in waves, by department or region, with training and change champions in each business unit. Rockwell Automation rolled out region by region.

Ready for Copilot

A migration is a good moment to prepare for Copilot.

Microsoft Copilot can show a person anything that person can open. If old permissions move across unchanged, Copilot can surface files that were never meant to be shared widely.

A migration already touches every site and every permission, so it is the natural time to set up sensitivity labels and data loss prevention in Microsoft Purview as well. Our Copilot AI Foundation service covers that work, together with the AI policy and training for your teams.

How it works

What you have at the end.

An inventory

Every file server and site in scope, with its owner, its permissions and when it was last used.

Less to move and to search

Content nobody uses archived or deleted, each time with the owner's agreement.

Sites people understand

Sites and hubs organized around how your teams work, with navigation that connects them.

Permissions you can explain

Access set at the site and library level, with company-wide sharing removed where it does not belong.

Search that finds files

Search configured across the new sites, with your company's own terms and acronyms.

People who know the new place

Training for each wave, change champions in each business unit and a governance guide for site owners.

Our method

From an inventory to files people can find.

  1. First

    Inventory and plan

    We take stock of the file servers and sites in scope, and agree the plan and the acceptance criteria for the migration with you in writing.

  2. The move

    Pilot and migrate

    One department moves first. The rest follows in waves, with the old location available until each cutover.

  3. After the move

    Settle in

    We train site owners and hand over a governance guide. We also stay on after each wave to fix what people report, or keep running the sites for you.

Compliance & security

  • Built to SOC 2, HIPAA and GDPR standards
  • EU AI Act-aligned delivery
  • Microsoft Solutions Partner

How we engage

Four ways to work with us.

Most migrations start with an inventory of one file server or one group of sites. Microsoft 365 licenses stay on your own agreement, and the migration tooling is agreed in the statement of work.

Advisory

Strategy, roadmap and readiness for an AI program.

Build

One scoped workflow at a time, with acceptance criteria agreed in writing before the build starts.

Run

Managed operations after launch, measured against those criteria.

Outcome-linked terms

Commercial terms can be tied to the acceptance criteria you sign.

Every engagement starts with one scoped workflow and a written definition of done. Commercial terms are set in the statement of work.

Frequently asked

Questions buyers ask.

How long does a SharePoint or file server migration take?

It depends mostly on how much content you have and how tangled the permissions are. We give you a plan with dates after the inventory. For scale, the Rockwell Automation intranet program ran as 12 two-week sprints, with the build and the content migration in sprints 5 to 8.

Do we have to move everything?

No. Most companies move only what people still use. We archive the rest where you can still reach it, and delete only what each owner agrees can go. Rockwell Automation moved its high-value content and archived outdated material.

What happens to our permissions?

We map them before anything moves. Folder permissions become SharePoint groups at the site or library level, and sharing with the whole company is removed where it does not belong. You approve the mapping before the move.

Should our files go to SharePoint, Teams or OneDrive?

Files a team works on together go to a SharePoint site, which can be connected to the team in Microsoft Teams, so the same files appear in both. Files that belong to one person go to that person's OneDrive. We agree the rule with you before the move, so people know where to save new files.

Will people lose access to their files during the move?

We plan the move so they do not. One department pilots first while the old location stays available, and each wave has a cutover date people know in advance. At Burckhardt Compression, pilot users could reach each document through the old route and the new one.

Will our content be ready for Microsoft Copilot after the migration?

Only if the permissions are right. Copilot can show a person anything that person can open, so we fix oversharing during the migration. Sensitivity labels and data loss prevention in Microsoft Purview, the AI policy and training are part of our Copilot AI Foundation service.

Can you move documents out of SAP or other business systems?

Yes. For Burckhardt Compression we kept SAP as the system of record and synchronized its documents with SharePoint in both directions, with SAP authorization profiles mapped to SharePoint security groups. Staff now search and co-author those documents in Microsoft 365.

What happens to old SharePoint workflows and forms?

They do not carry over as they are. Classic workflows, InfoPath forms and custom web parts need a decision to rebuild or retire. We rebuild the ones you still need in Power Automate and Power Apps.

Research paper

Past the stall: Why M365 Copilot rollouts plateau and the governed path through

Why Copilot pilots stall, and the governed path from pilot to measured adoption.

Read the paper
Get the designed PDF

Tell us which file server or site to start with.

Every engagement starts with one scoped workflow and a written definition of done. Commercial terms are set in the statement of work.

  • Built to SOC 2, HIPAA and GDPR standards
  • EU AI Act-aligned delivery
  • Microsoft Solutions Partner