Do not lift and shift
Copying a file server into a new system moves the mess with it. File shares typically hold duplicates, outdated versions and documents nobody needs. Moving all of it costs time, inflates storage and licence use, and carries unmanaged content into a system meant to be governed. Decide what deserves to move before you move anything.
Audit and triage
Start by profiling what is there: volume, file types, age, owners, duplicates and last access. Sort content into what must be kept as records, what is worth keeping as working documents, and what can be archived or disposed of under your retention rules. Involve the business owners, because IT cannot decide on its own what is still needed.
Map classification and metadata
Agree the classification scheme and the metadata each record type needs, then work out how existing folder paths and file names map to it. Often a folder structure encodes useful information, such as customer, project or year, that can be extracted into metadata during migration. Test the mapping on a sample before applying it to everything.
Migrate in waves and validate
Move one department or record type at a time. After each wave, check counts, spot-check content and metadata, and confirm permissions behave as intended. Agree a clear cutover date, after which the old location becomes read-only, so nobody keeps working in two places. Our experience includes a university records project covering 150,000 to 200,000 records.
After the move
Keep the old location read-only for an agreed period, then retire it under your retention rules. Train teams on how to file and find documents in the new system, assign owners for each record type, and review the first few months of use for gaps in the classification or workflows.
Common questions
How long does a file server migration take?
It depends on volume, content quality, the complexity of the classification, and how many departments are involved. Triage and classification design usually take longer than the technical transfer. A pilot gives you a realistic estimate.
Should we migrate everything?
Usually not. Triage first, and migrate what must be kept as records or is still actively used. Dispose of or archive the rest according to your retention rules.
Can we keep our existing folder structure?
You can, but a metadata-driven system lets documents be found by customer, project or type instead of one folder path. Folder names often become useful metadata during migration.
What about duplicates and old versions?
Identify duplicates during triage and decide which copy is the record. Older versions can be kept as version history where required or disposed of under your retention rules.
Related: M-Files consulting and implementation
Have a similar problem in your business?
Bring us the current process and we will help you work out whether it is worth solving.
Talk through the problem