File Share to SharePoint Migration

Leave the Folder Maze on the File Server

We move your network file shares into SharePoint and use the move to make content easier to find, not just to put it somewhere new.

Plan your file share migration

Most file shares grew one folder at a time. Years later, the only way to find a contract is to know it lives five levels down, under a client, a year and a project. Copy that into SharePoint and you have the same maze in a new place, with paths SharePoint may reject and permissions nobody can follow.

We move file shares into SharePoint and Microsoft 365 and use the move to fix how the content is organised. The folder structure becomes metadata. What nobody needs stays behind. Access is rebuilt around groups, and AutoTag tags the content as it lands.

Folders Become Metadata

A path like Clients\Acme\2021\Contracts already says who a document is for, when it was written and what it is. On a file share, you only learn that by knowing where to look.

We turn each useful level of the folder structure into a SharePoint column, such as Client, Year and Document type, and fill it in as the files move. File properties, such as created and modified dates, come across too. Libraries stay shallow, and people can find the same contract by client, by year or by type, from search or a filtered view.

What Stays Behind

Duplicates, old drafts and files nobody has opened in years don’t need to move. We show each area’s owner what they have and agree what goes, what is archived and what is deleted. Moving less makes the migration quicker and search better afterwards.

Permissions

File share permissions tend to be set folder by folder, often for named people, and rarely tidied. Copied across as they are, they become broken inheritance in SharePoint, and Microsoft 365 Copilot can use anything the person asking is allowed to open.

We grant access through groups, set it at the site or library, and keep exceptions rare. Where part of a share needs different access, it gets its own library or site, not a folder with its own permissions. If your existing SharePoint is already shared too widely, our Copilot oversharing clean-up deals with that.

Tagging With AutoTag

Folders only tell you so much. A supplier invoice filed under a project says nothing about the supplier. AutoTag, our automation platform for Microsoft 365, fills the gaps. Its Metadata Bots run inside your tenant and apply terms from your taxonomy, by rules you set, by AI reading the document, or both.

They work through everything you have migrated, then tag new files as they arrive, so the metadata is still there a year after go-live.

How It Works

1

Audit

volume · age · duplicates · owners

We scan the shares to see what is there, how old it is, who owns each area and how access is set.

2

Design

sites · libraries · columns · groups

We design where content will live, map folder levels to columns and agree who gets access through which groups.

3

Move

migration tooling · batches

We migrate with automated tooling, one area at a time, so each team switches over in one go.

4

Tag and check

AutoTag · permissions · search

AutoTag fills in the metadata. We check content, permissions and search in SharePoint before the share is retired.

From File Shares to SharePoint

CVC Capital Partners

More than 30 years of deal documents, once hard to find in file shares and legacy applications, now in a SharePoint research portal where AutoTag categorises them automatically.

Already in SharePoint?

If your content has moved but is still hard to find, we fix the information architecture and tag what is already there.

For moves between tenants, from other platforms or from SharePoint Server, see our SharePoint migration services.

File Share Migration FAQs

Ready to retire the file server?

Tell us about your file shares. We’ll start with an audit and quote the migration from what it finds.