We completed our SharePoint Online migration last week. 2TB of files moved from on-premises file servers to the cloud. Here's what we learned.
Why Migrate
File servers were aging. Remote access was clunky. Collaboration was difficult. SharePoint Online solves these: anywhere access, real-time collaboration, versioning, and no hardware to maintain.
Planning the Migration
We spent more time planning than migrating. Inventory all shares. Identify owners. Clean up obsolete data (we deleted 400GB of files nobody had touched in 5+ years). Map permissions to SharePoint groups. Define site structure.
The Migration Tool
Used SharePoint Migration Tool (free from Microsoft). Worked well for straightforward migrations. For complex permission scenarios, manual cleanup was required post-migration.
User Adoption
OneDrive sync client made adoption easier - users still see files in File Explorer. Training focused on new capabilities (sharing, versioning) rather than dwelling on change. Most users adapted within a week.
Challenges
Path length limits bit us - SharePoint has shorter maximum paths than Windows file servers. Had to rename some deeply nested folders. Also discovered files with characters that SharePoint doesn't allow - required cleanup before migration.
Results
Two file servers decommissioned. Remote access dramatically improved. Collaboration features getting used. Storage costs shifted from capital to operating expense. Worth the effort.
Planning an ERP modernization?
6 SAP-to-Dynamics conversions with zero business disruption. Let's discuss your project.
ERP Services Book a Call