How to Migrate from a Shared Drive to a Document Management System

Before you migrate, make sure you've chosen the right system — our best document management system UK guide walks through the full decision. This article covers the migration itself: how to move from a shared drive to a DMS without losing files, metadata, or your sanity.

Why Migrating Is Harder Than It Looks

Most businesses underestimate a shared drive migration. The temptation is to copy the folder structure across wholesale — same folders, same files, new location. That approach fails because it imports the problems as well as the documents.

Shared drives accumulate years of disorganisation: duplicate files (final_FINAL_v3_USE_THIS.docx), deeply nested folders nobody can navigate, files in the wrong place because someone was in a hurry, personal files mixed with business documents, outdated templates still in use because nobody knows where the current ones are. Copying that across to a DMS just gives you an expensive, cloud-hosted mess.

Step 1 — Audit Before You Touch Anything

Spend time understanding what you actually have before moving anything:

• Volume: How many files? How many GB? Use Windows Explorer or a tool like TreeSize to get the numbers.
• Age profile: Sort by last modified. Files not touched in 3+ years are probably archive or redundant — don't migrate them to live storage.
• Duplicates: Run a duplicate finder (Duplicate Cleaner Free is good). Most shared drives have 15–30% duplicate files.
• Ownership: Which department owns which folders? You need them to validate their own areas.
• What can be deleted: Expired documents, superseded templates, temp files, personal folders. Delete before you migrate, not after.

Step 2 — Design Your DMS Structure First

Do not replicate your shared drive folder structure in the DMS. Your shared drive structure evolved organically over years — it reflects how documents were created, not how they're used. Your DMS structure should reflect how documents are retrieved.

Work backwards from retrieval: what questions do people ask when looking for a document? "What's the current version of the X contract?" "Show me all invoices from Supplier Y in Q3 2024." "Where's the health and safety policy?" Your metadata fields and folder structure should make those questions answerable in under 10 seconds.

Define your metadata schema before migration: what fields will every document type have? Document type, date, department, reference number, status? Agree this and document it — it's the foundation everything else builds on.

Step 3 — Run a Pilot Migration

Migrate one department's files first. Pick a manageable department — not the largest, not the most complex. Migrate their documents, validate the structure works, get feedback from the team. Is everything findable? Are the metadata fields useful? Does the folder hierarchy make sense?

Fix issues in the structure before you migrate the other 95% of the business. Changes to metadata schema after a full migration are expensive.

Step 4 — The Full Migration

Tools for bulk migration:

• SharePoint Migration Tool (SPMT): Free Microsoft tool for migrating network drives and file shares to SharePoint Online. Handles large volumes, preserves file dates and permissions.
• Mover.io: Microsoft-owned, handles migrations between cloud platforms (Google Drive → SharePoint, Box → OneDrive, etc.).
• DMS vendor migration tools: Most enterprise DMS vendors provide their own migration utilities. Ask specifically about network drive migration support.
• Manual migration: For small volumes (under 5,000 files), drag and drop with careful review is sometimes the most controlled approach.

During migration, put the shared drive in read-only mode. This prevents new files being created in the old location while the migration is in progress. It forces the conversation about the cutover date.

Step 5 — Decommission the Shared Drive

This is the step most businesses skip — and it's the reason migrations fail. If the shared drive stays available after the DMS goes live, people will keep using it. "Just this once" becomes the new normal. Within a month, half the business is still working from the old drive and the DMS is a ghost town.

Set a hard cutover date. Communicate it clearly. On that date, make the shared drive read-only (not deleted — read-only). After 30 days of the DMS running cleanly, archive the shared drive to cold storage and remove access.

Common Migration Pitfalls

• Copying chaos: Migrating the folder structure as-is. Don't do it.
• No metadata strategy: Files land in the DMS without tags. Nobody can find anything.
• Skipping the audit: Migrating 50,000 files when 20,000 should have been deleted.
• No staff training: The DMS goes live, nobody knows how to use it, everyone reverts to email.
• Keeping the old drive alive: Ensures the migration is treated as optional.