☕ SharePoint Tip #15 — File server migration: the complete playbook

Posted on by

Good morning! Here is your 15-minute SharePoint tip for today.

Day 15 | Week 3 — Integration, Automation & Migration

Planning a File Server Migration to SharePoint

Since your company uses SharePoint heavily as a file server replacement, migration planning is one of the most critical skills you need. Today’s tip is the most practically relevant of the entire 30 days.

The four phases of a file server migration

Phase 1 — Assess
Inventory what you have. How many file shares? How much data (TB)? What is the folder depth? How old is the content? Which files haven’t been accessed in 2+ years (dark data)? Tools: SharePoint Migration Assessment Tool (SMAT), Storage Sense reports.

Phase 2 — Plan
Design the target architecture. Map file shares to SharePoint sites and libraries. Define the metadata taxonomy. Establish naming conventions. Agree governance policies. Identify stakeholders per department. This phase takes longer than people expect — budget 30–40% of project time here.

Phase 3 — Migrate
Run the actual migration using Microsoft’s Migration Manager (built into the SharePoint Admin Center — free) or third-party tools like Sharegate, AvePoint, or Metalogix. Migrate in waves: start with a low-risk pilot department, learn, then scale.

Phase 4 — Adopt
Training, champions, communication. The migration is technically done when files move — it’s actually done when users stop asking for the file server back.

Common migration pitfalls

  • Path length violations — SharePoint has a 400-character URL limit. Deep folder structures often violate this. Fix: flatten or rename before migrating.
  • Unsupported characters — file names with # % & * : < > ? / { | } will fail. Fix: run SMAT first to identify these.
  • Permissions explosion — file servers often have thousands of unique permission entries. Fix: rationalise permissions before migration, not after.
  • Dark data — migrating 10-year-old files no one uses wastes storage and confuses users. Fix: archive or delete files not accessed in 3+ years before migrating.

Try it today (5 minutes)

In the SharePoint Admin Center → click Migration in the left nav. Explore Migration Manager. Even if no migration is running, understanding the interface — file share scanning, task management, migration reports — prepares you for planning conversations.

As a Product Owner

A file server migration is a change management project that happens to involve a technical migration. The technology is the easy part. Getting 500 people to change how they work is the hard part. Budget at least as much for training and adoption as for the technical migration itself.

See you tomorrow at 6:00 AM with Tip #16 — Microsoft Syntex and AI in SharePoint. Week 3 complete!