Field Notes › Migrating a file server without hiring a consultant

Migrating a file server without hiring a consultant

Field Notes · 28 July 2026

Moving a Windows file server or NAS into SharePoint or OneDrive is not, by itself, a consultancy project. What often turns it into one is everything around the migration rather than the migration itself.

Nobody has decided what belongs in SharePoint and what belongs in OneDrive. Nobody has checked whether file names are compatible. Nobody has agreed what "finished" actually means. By the time those questions appear, the copying has usually already started.

That leads many organisations to assume they need outside expertise. In reality, most internal IT teams already know more about the data than any consultant ever will. They know which departments collaborate, which folders belong to individuals, which archives can be left behind and which shared drives the business depends on every day. The challenge is rarely understanding the business, it's having a structured process and the right tooling.

What consultants actually bring

A typical migration engagement usually consists of four activities.

• Planning what should move and where it should go.
• Running the migration.
• Verifying that everything arrived correctly.
• Taking responsibility if something goes wrong.

Of those four, running the migration is often the simplest. Modern migration software can handle copying millions of files while preserving structure and timestamps.

Planning and verification still require people, but they usually require business knowledge rather than migration expertise. Those decisions are often made better by the organisation itself, because nobody understands the data better than the people who work with it every day.

The decisions that really matter

There are only a handful of decisions that genuinely determine whether a migration succeeds.

Decide what belongs in SharePoint and what belongs in OneDrive

Not every folder should end up in the same place. Department documents, procedures, project information and shared working files belong in SharePoint. An individual's own working documents usually belong in OneDrive. Making this decision before the migration avoids moving large volumes of data twice. More on making that call.

Deal with file names before they become a problem

Windows and SharePoint do not follow exactly the same naming rules. Characters, reserved names and path lengths that work perfectly on a file server may be rejected by SharePoint. Discovering that after thousands of files have started copying is frustrating. Discovering it before the migration starts is simply another item on the checklist. More on the specific limits.

Decide what "done" means

Many migrations finish with someone browsing a few folders and saying everything looks fine. That is not verification. Verification means knowing:

• Every file was copied.
• Every file was checked.
• Every automatic rename was recorded.
• Any failures were identified.
• The destination matches the source.

Without that evidence, success depends on nobody noticing a problem.

You do not need specialist migration knowledge

None of these decisions require someone who spends every day performing migrations. They require someone who understands how the business uses its information, and that is usually your own IT team. Good migration software should surface issues before they become problems, provide sensible defaults where appropriate, and produce enough evidence afterwards that everyone can be confident the migration completed successfully.

A practical approach

First, classify every top-level folder as either personal content or shared business content.

Next, run a readiness assessment against the live source. Resolve naming issues, understand duplicate data and identify anything that needs attention before copying begins.

Then migrate a small department or pilot group first. Verify the results properly before expanding to the remainder of the organisation.

Keep the original file server as the authoritative source until users are successfully working from Microsoft 365 and the migration has been fully verified. Only decommission the old server once the audit trail confirms every file has been transferred and validated.

When a consultant genuinely adds value

There are absolutely situations where external expertise is worthwhile. Very large estates, mergers, complex governance projects, regulatory requirements or organisations with no internal IT capability can all benefit from experienced migration specialists.

The important distinction is understanding what you are buying. You may need advice on planning, governance or information architecture. You may not need somebody simply to press the start button.

With the right preparation and the right migration software, many organisations are entirely capable of moving their own file servers into Microsoft 365 while keeping full visibility of what happened and confidence in the final result.

← Back to Field Notes