Old file servers and mapped drives are where organisational knowledge goes to gather dust, and moving them to SharePoint and OneDrive is one of the more nerve-wracking IT projects because everyone notices the moment a file or a permission goes missing. Done in order, it is far calmer than it sounds.
Before anything moves, build a picture of the current state:
Permissions are where file migrations go wrong, so this audit is not optional.
Do not migrate the mess. Stale, duplicated and abandoned data just makes the new home messy from day one. Archive or delete what nobody needs first, then move what matters. A migration is a rare chance to start tidy, take it.
Moving junk to the cloud just gives you junk in the cloud, with a bigger bill.
This is the structural decision people get wrong. OneDrive is for an individual's working files. SharePoint is for shared, team-owned content. Dumping shared data into someone's OneDrive ties the team's work to one person's account, a problem the day they leave. Sort team content into SharePoint sites that mirror how the organisation actually works.
As with a full Microsoft 365 migration, move in waves rather than all at once, and tell people clearly where their files now live and how access changed. Half of the support tickets after a file migration are simply people who were not told where things went.
After each wave, confirm the right people can reach the right content and no one can reach what they should not. This is the file-level equivalent of the identity hygiene we cover in Okta rollouts, access should be intentional, not accidental.
If you are staring at an ageing file server and dreading the move, our cloud and infrastructure team runs these migrations cleanly, permissions intact. Get in touch.
OneDrive is for an individual's own working files; SharePoint is for shared, team-owned content. A common mistake is dumping everything into OneDrive, which makes shared work depend on one person's account. Team data belongs in SharePoint.
They can, if you map and plan them first. Permissions are where file migrations most often go wrong, people suddenly cannot reach what they need, or can reach what they should not. Auditing access before the move is what prevents both.
Reading is one thing. Let's map it to your actual workflows in a free 30-minute working session, no commitment.