Microsoft 365 / Sub-service 03
SharePoint & OneDrive migration consultant.
IA first. Then the migration.
Modern collaboration, not chaos in a cloud folder. We do the information architecture, permission rationalization, and labeling work before the migration — so the destination doesn't recreate the original mess.
Service detail
File share to SharePoint Online migration plan
A migration that solves the inheritance mess at the source instead of carrying it forward. IA before lift-and-shift, permissions before automation, labels before Copilot.
What's in scope
- ›File-share inventory and ownership mapping
- ›Information architecture before migration (not after)
- ›Permission rationalization — solving the inheritance mess at the source
- ›Migration to SharePoint Online sites or OneDrive personal storage
- ›Sync client deployment and end-user onboarding
- ›Sensitivity labels and retention policies applied at migration
- ›Old file-share decommission and archival
Why most file-share migrations fail
- ›Lift-and-shift without IA results in SharePoint that nobody can navigate
- ›Permission inheritance bugs surface months later as access incidents
- ›The 12,000-permission problem becomes a Copilot data-exposure event
- ›Old file shares stay running 'just in case' and never actually retire
- ›End-user resistance kills adoption and people drift back to OneDrive personal sync
What you get
- ›An information architecture document (yours to maintain)
- ›A permission report showing who had access to what before, and what they have after
- ›Sensitivity-label and retention baseline ready for Copilot enablement
- ›End-user training materials and adoption metrics
- ›Old file-share retirement plan and execution
FAQ
Common questions about file-share modernization.
What does a SharePoint and OneDrive migration consultant do?
A SharePoint and OneDrive migration consultant moves on-prem file shares — and legacy SharePoint Server content — into Microsoft 365 SharePoint Online and OneDrive for Business. Scope: file-share inventory and ownership mapping, information architecture design BEFORE migration, permission rationalization (orphan SIDs, broad-group access, ownership concentration remediated at source), migration to SharePoint Online sites or OneDrive personal storage, sync client deployment with Known Folder Move, sensitivity labels and retention policies applied at migration, and old file-share decommission and archival. Tooling chosen per project (Microsoft Migration Manager for under 5 TB, ShareGate or BitTitan MigrationWiz for larger scale) — vendor-neutral, no resale. Output is Copilot-ready destination state, not a lift-and-shift mess in the cloud.
When should files go to SharePoint vs OneDrive?
Personal working drafts go to OneDrive. Anything two or more people work on goes to SharePoint. Department file shares almost always become SharePoint sites — never group OneDrives. Migrating user-home shares to OneDrive is straightforward; migrating departmental shares to OneDrive is a structural mistake that breaks within a year.
What's the right tool for file-share to SharePoint migration?
For projects under 5 TB and 100K files, Microsoft's free Migration Manager is usually sufficient. Beyond that, ShareGate Migrate or BitTitan MigrationWiz handle filename oddities, path-length failures, and permission preservation at scale. We recommend per project — not per partnership.
How do you handle permission inheritance during migration?
We rationalize permissions before migration, not after. Every share gets an audit pass: orphan SIDs, broad-group access (Everyone, Domain Users), and ownership concentration are flagged and remediated at source. Carrying inheritance bugs forward into SharePoint is what makes Copilot dangerous later.
Will users keep their drive letters after migration?
OneDrive Known Folder Move (KFM) maps Documents, Desktop, and Pictures locally so users see no change. SharePoint sites get added as 'Sync' libraries that appear in File Explorer under the company name. We coordinate end-user communications and training as part of every engagement.
Field notes
- → Copilot readiness: the 12,000-permission problem — why oversharing has to be solved at source before Copilot can read it.
How big is the file environment?
Tell us TB count and approximate share count. Two-business-day response with scope, timeline, and recommendation on tooling.