How to migrate a file server to SharePoint Online

To migrate a file server to SharePoint Online, audit what you have, delete or archive what nobody uses, design a new structure of sites and libraries, rebuild permissions with groups, copy the files with a migration tool, test with a pilot group, then switch users over and make the old share read-only. The copy is the easy part. The planning decides whether people accept the result.

Why move off the file server

A file server works while everyone is in one office and the folder tree is tidy. It stops working when people are remote, when you need to know who changed a document, or when a contract is approved by email and the signed copy lives somewhere else. SharePoint Online adds version history, an audit trail, sharing without attachments, search across content and approvals that can run in Power Automate. It also opens in Teams and Office without a VPN.

If you are still deciding, read SharePoint vs file servers first. This guide assumes you have decided and need a plan.

Step 1: audit the file server

Before you choose a tool, find out what you are moving. A scan of the share gives you the numbers that drive every later decision.

• Volume: total size and number of files, and the biggest folders.
• Age: how much has not been opened or changed in three years or more.
• Duplicates and temporary files: copies, backup files, old installers and system files.
• Path length and file names: paths close to the limit and names with characters SharePoint does not accept.
• Permissions: where access is set on folders instead of groups, and which accounts no longer exist.
• Owners: who is responsible for each top-level folder. Folders with no owner are usually the first to archive.

Step 2: clean up before you copy

Migrating everything blindly costs more, takes longer and moves the clutter into a place that is harder to tidy. Agree a rule with each owner: keep, archive or delete. Archive old material to cheaper storage with a note of where it went. Remove duplicates. Rename files and folders that will fail. Do this on the file server, where you can still compare with the original.

Step 3: design the structure

A folder tree built for a network drive does not suit SharePoint. Use the audit to decide what becomes a site, a library or a folder.

• One site per team, project or topic when the audience or permissions differ. Our SharePoint best practices cover the flat structure and hub sites in detail.
• One library per kind of content inside a site, with a few columns (document type, owner, status, date) instead of five levels of folders.
• Personal folders go to OneDrive, not to a shared site.
• Keep folders shallow. One or two levels is enough for broad groupings such as year or region.

Write the mapping down as a simple table: source folder, target site and library, owner, audience, and what happens to it (move, archive, delete). This table is your migration plan and your checklist.

Step 4: rebuild permissions with groups

File server permissions are usually a mix of inherited rules, one-off grants and accounts of people who left. They do not map neatly to SharePoint, and copying them as they are recreates the same confusion. Decide access from the new structure instead.

1. Create or reuse groups for each audience (a department, a project team, a client team).
2. Give each site its owners, members and visitors through those groups.
3. Use unique permissions on a folder or file only when there is a real reason, and write the reason down.
4. Ask each owner to confirm who should have access before go-live, not after.

Step 5: check the limits that cause errors

These figures are from Microsoft's published limits at the time of writing. Check the current documentation before a large migration.

• Path length: about 400 characters for the full address of a file. Deep folders with long names are the most common cause of failed items.
• File size: up to 250 GB per file. Very large files such as video or CAD archives may be better kept in other storage.
• File names: some characters and reserved names are not allowed. Fix them in a pre-scan rather than letting the tool rename them silently.
• List view threshold: 5,000 items per view operation. Libraries can hold millions of files, but views that filter or sort on a column that is not indexed can fail. Index the columns you filter on.
• Syncing: do not sync libraries with hundreds of thousands of files to every laptop. Split large content across libraries or use shortcuts.

Step 6: choose a tool and run a pilot

Microsoft provides the SharePoint Migration Tool and Migration Manager in the SharePoint admin center, which can copy file shares to SharePoint and OneDrive. Third-party tools add scheduling, reporting and permission mapping. The right choice depends on volume, how much re-mapping you need and how much reporting your auditors expect.

Whatever the tool, run a pilot first. Pick one real team, move its content, and ask them to do their normal work for a week or two. Look at three things: files that failed and why, whether people can find what they need, and whether permissions are right. Fix the pattern, not just the file, then plan the main waves.

Step 7: cut over and retire the share

1. Announce the date, the new addresses and where to get help. A short guide with screenshots helps more than a long email.
2. Run a final copy of changed files, then set the old share to read-only.
3. Keep the read-only share for an agreed period, then archive or retire it.
4. Add a shortcut or a redirect in places where people used to open the old path, such as intranet links and desktop shortcuts.
5. Review search, permissions and the top questions from users after the first month.

After the move: make it a document system

Moving files is the start. The gains come when you use what SharePoint adds: versioning, metadata for search and filtering, retention policies for records, and approval flows for documents that need sign-off. Our document management system shows what a configured set-up looks like, and the migration planning guide gives a full checklist. For cost and timelines by size of project, see SharePoint Online migration cost and timeline.

Mistakes we see most often

• Copying the whole tree and calling it done.
• Leaving permissions for after the migration.
• No pilot, so the first users find the problems.
• No owner for the new sites, so they are untidy again within a year.
• Ignoring path length until the copy fails in the middle.

Related: SharePoint migration services, SharePoint consulting and SharePoint 2013 or 2016 to Online migration.