An ageing file server nearing end of life is one of the most common reasons Perth businesses look at SharePoint - but treating the migration as "just copy the files across" is exactly how businesses end up moving years of folder-structure mess into their new cloud environment unchanged. It's worth doing properly.
Why This Isn't Just a File Copy
SharePoint isn't a drive letter in the cloud - it's a fundamentally different structure, organised around sites and document libraries rather than deep nested folder trees, with its own permissions model. A direct, unreviewed copy tends to carry across years of disorganisation rather than fixing it, and often creates confusing, overly complex site structures in the process.
Step 1: Audit What's Actually There
Before moving anything, review what's actually on the file server - much of it is often outdated, duplicated, or genuinely no longer needed. This is the natural point to archive or delete rather than migrate everything as-is, since every unnecessary file migrated is wasted time and cost.
Step 2: Design the SharePoint Structure Deliberately
Map departments, projects, or functions to SharePoint sites and libraries based on how the business actually works today, not simply mirroring the old folder tree. This is the single biggest factor in whether the new structure actually improves on the old one or just relocates the same confusion.
Step 3: Redesign Permissions
NTFS permissions from the old file server don't map cleanly onto SharePoint's model and shouldn't be assumed to carry across automatically. Permissions need to be deliberately rebuilt against the new site and library structure - see our guide on auditing Microsoft 365 user permissions for what a properly scoped permission structure should look like.
Step 4: Migrate in Stages
Move data in planned batches rather than all at once - this makes issues easier to catch and fix, and allows a pilot group to validate the new structure works before the whole business depends on it.
Step 5: Run a Transition Period
Keep the old file server accessible (read-only, ideally) for a defined period after cutover, giving staff a safety net while they adjust to the new structure and confirming nothing was missed in the migration.
Step 6: Train Staff on What's Different
SharePoint and OneDrive sync behave differently from a mapped network drive - particularly around file locking during simultaneous edits and offline access. A short training session prevents the confusion that otherwise generates a wave of support tickets in the first few weeks.
What Happens to the Old Server
Once the migration is confirmed successful and the transition period has passed, the old file server can be properly decommissioned - see our guide on safely disposing of old IT equipment for how that should be handled, particularly around securely wiping any remaining data.
Frequently Asked Questions
Can I just copy the file server's folder structure directly into SharePoint?
You can, but it's usually a mistake to do it without review - file server folder structures often reflect years of ad-hoc organisation that don't map cleanly onto SharePoint's site and library structure. A direct copy tends to just relocate the mess rather than fix it.
What happens to old NTFS permissions during migration?
They don't transfer automatically or cleanly - SharePoint uses a different permissions model (site and library-level, generally simpler than deep NTFS folder trees). Permissions need to be deliberately redesigned during migration, not assumed to carry across.
Will staff need to change how they work day to day?
Some adjustment is normal - SharePoint and OneDrive sync work differently from a traditional mapped network drive, particularly around offline access and file locking during simultaneous edits. Staff training during the transition significantly reduces friction here.
Can this run alongside the old file server during a transition period?
Yes, and for most businesses this is the sensible approach - running both temporarily while staff transition, rather than an abrupt cutover, reduces disruption risk considerably.
We plan and run file server to SharePoint migrations for Perth businesses - proper structure, redesigned permissions, and a staged rollout, not a raw copy.
Microsoft 365 Services →Running an old file server past its use-by date?
Call 0433 087 091 - we'll assess your file server and scope a proper SharePoint migration, no obligation.
Get a Free Migration AssessmentFor related reading, see our guides to SharePoint vs OneDrive and how much cloud migration costs.