Every file server migration faces the same temptation: copy everything as-is and sort out the organisation later. "Later" never arrives - and the company ends up paying cloud licences to host fifteen years of duplicates.

1. Inventory before any decision

Before discussing tooling, get the numbers: total volume, file count, distribution by type, last access date and maximum path depth. This diagnosis usually shows that 60% to 70% of the archive has not been opened in over three years.

2. Clean-up - what stays behind

Four categories are excluded from the migration or sent to cold archive:

  • Exact duplicates: the same file replicated across departments.
  • Manual versions: report_final_v3_reviewed_OK.docx and its twelve siblings - native versioning replaces this habit.
  • Obsolete files: untouched for years with no legal obligation to keep.
  • Ephemeral content: installers, personal backups and media that never belonged there.

This purge needs formal sign-off from the areas that own the content. It is as much political as technical work - and where schedules slip without sponsorship.

3. From folder to metadata

Here is the real gain. A path like \\fs01\Legal\Contracts\2024\Suppliers\ACME carries four implicit facts: area, type, year and counterparty. Instead of recreating the path, those facts become columns populated automatically during the load.

The result is a flat library, filterable by any combination of those axes - no longer a tree that only answers in the order it was built.

4. Permissions: rebuild, do not copy

Inheriting file server ACLs imports years of accumulated exceptions. The better path is redesigning from role-based groups, breaking inheritance only where explicitly justified, and reviewing the result with managers before cut-off.

5. Pilot wave

Pick a mid-sized area with a representative archive and an engaged manager. The pilot validates metadata mapping, load performance and - above all - whether the designed views make sense to the people using the archive daily.

6. Cutting off the legacy share

Migration without a cut-off date creates a permanent dual environment. After validation, the old share goes read-only for an agreed period and is then retired, with an automatic notice pointing to the new location.

As long as the file server accepts writes, half the company will keep saving there. The cut-off is part of the project, not an afterthought.

How to measure success

  • Reduction in total migrated volume against the initial inventory.
  • Share of documents with mandatory metadata populated.
  • Use of team views in the weeks after go-live.
  • Drop in "I can't find the file" tickets.