
OneDrive Migration
Retire your file server. Move users' home directories and Windows Known Folders to OneDrive. Remote access without VPN. Your data follows the user, not the location.
Your File Server Is the Reason Remote Work Does Not Work
Home drives on an on-prem file share. Department shares mapped as network drives. VPN every time somebody works from home. Backups running overnight, restores taking hours, and nobody is sure which folders are still actively used. When the file server hardware comes up for renewal, the question is always the same: another three years of the same problem, or a clean move to the cloud.
This is not a failure of your IT team. Known Folder Move to OneDrive is not plug-and-play — you need to handle long-path issues, unsupported characters, sync app rollout rate limits, permissions structures that do not map cleanly, and users who treat file moves as an act of aggression. Without a structured migration, the pilot stalls, the file server stays on, and nothing changes.
Traditional consulting for a file-to-cloud migration? Six figures. The consultant migrates, leaves a handover, leaves. When users complain six months later about sync errors, you are back on your own.
ACTIVITIES IN DETAIL
DELIVERABLES
Licensing and Provisioning: Storage quota against real data, OneDrive pre-provisioned per user
Data Inventory: Volume and file count per user, deepest path, largest file, and the blockers
Migration Strategy: Scope, tool, pilot, waves, rollback, plus the 100 GB and PST edge cases
OneDrive Baseline: Sharing level, default link type, sync restrictions, and storage quotas
Known Folder Move: Desktop, Documents, Pictures, prompted on pilot, silent then locked in production
Migration Execution: Agent registered, home directories mapped, assessment scan before every run
Pilot and Waves: 5-10 users across data profiles, then department waves with a 5% error gate
Validation and Decommission: Source-to-target check, remediation list, then the file server shutdown
Next steps after OneDrive Migration
A cleanly configured tenant is the foundation. These blueprints build directly on it




