web
You’re offline. This is a read only version of the page.
close
Skip to main content

Announcements

News and Announcements icon
Community site session details

Community site session details

Session Id :
Engage with the Community
Suggested Answer

Enterprise SharePoint Online Migration Restructuring Looking for Best Practices from the Community

(0) ShareShare
ReportReport
Posted on by 2

Hello Microsoft Community,

I'm currently planning a large-scale SharePoint Online restructuring and migration and would appreciate advice from anyone who has completed similar enterprise migrations.

Environment


  • ~2.7 TB of SharePoint data

  • 114,000+ files

  • 19,000+ folders

  • Multiple document libraries

  • Deep folder structures and long file paths

  • Multiple business units being split into separate SharePoint sites

  • Need to preserve permissions, metadata, version history, and business continuity

  •  

Rather than a simple lift-and-shift, we're redesigning the information architecture by creating multiple SharePoint sites and document libraries with a phased migration approach.

Key Challenges

We're looking for best practices around:


  • Preserving version history

  • Migrating or remapping sharing links

  • Handling long file paths

  • Validating source vs. destination (file counts, folders, versions, permissions)

  • PowerShell automation and checkpoint/resume strategies

  • Permission migration using Microsoft Entra ID security groups

  • Scheduling and executing a multi-terabyte migration with minimal downtime

  •  

Questions

For those who have completed migrations of this scale:

 
  • Which migration tools did you use (SPMT, Migration Manager, PnP PowerShell, Microsoft Graph, or third-party tools)?

  • How did you validate that no content was lost?

  • How did you handle version history and sharing links?

  • Did you migrate site-by-site, library-by-library, or folder-by-folder?

  • What lessons learned or Microsoft best practices would you recommend before we begin execution?


  •  

Any guidance, real-world experiences, or recommendations would be greatly appreciated.

Thank you!

I have the same question (0)
  • Suggested answer
    MS.Ragavendar Profile Picture
    7,613 Super User 2026 Season 2 on at
     
    Based on your requirement, the approach of PnP PowerShell alone for the actual content migration of 2.7 TB and 114k+ files is not a recommend approach.
     
    Migration Tools
    • ShareGate - Best tool in the market
    • Metalogix
    • Avepoint
    • SPMT (Microsoft Migration Manager)
    these are the tools available in the market for the migration of contents from source to destination based on the pricing you can choose the relevant tool.
     
    Based on the migration tool selection all your queries will addressed.
     
    The Migrated metrics will be available after the every job migration, it will have detailed information what copied and what files aren't copied and the reason for it you need to check and plan for the delta or incremental migration.
     
    Version history - if the version is enabled in the source if you enabled the relevant settings the version of items will gets copied (each versions of the file will be migrated to one version).
     
    Permission - The permission will be handled as per the source, If the users are part of AD will it resolved automatically, if the user doesn't exists the mapping has to be provided for those.
     
    Migration Journey :
     
    Sprint 0 : Discovery and Assessment - Need to the volume of files and decides what sites are migrated and what are custom functionality available what is the priority.
     
    Sprint 1 : Dry Run - To do some sample migration how the data and structure permissions are copied measured the through put and decide the timeline based on that.
     
    Sprint 2 : Actual Migration - Batch wise migration based on the priority and content size 
     
    Sprint 3 : Data Validation - Validates the volume of data and permission in the destination sites.
     
    Sprint 4 : Development- Redeveloped and deployed the custom functionalities ensure its working as expected.
     
    Sprint 5 : UAT - Validated by the business for the sign off and collection inputs for the missing functionalities and file
     
    Sprint 6 : Incremental Migration - Missing files and failed files needs to be planned on this phase.
     
    Sprint 7 : Release PROD - Released for production and old site redirection and apply read only on the old sites.
     
    Sprint 8 : Hyper Care - Any issues in the prod or sync missed in old that has to be taken care.
     
    Sprint 9 : Decommission the OLD Application (SharePoint Site)
     
    This is the overall process but it varies from org to org and person to person.
     
    ✅If this helped, please Accept as Solution to help others ❤️ A Like is appreciated 🏷️ Tag @MS.Ragavendar for follow-ups.

Under review

Thank you for your reply! To ensure a great experience for everyone, your content is awaiting approval by our Community Managers. Please check back later.

Helpful resources

Quick Links

Season of Sharing Community Challenge Winners!

Congratulations to our community stars!

Kudos to our 2025 Community Spotlight Honorees

Expanding mentorship, skilling, and AI innovation

Congratulations to the July Top 10 Community Leaders!

These are the community rock stars!

Leaderboard > Engage with the Community

#1
metthew Profile Picture

metthew 11

#2
lukoplt Profile Picture

lukoplt 8

#3
sannavajjala87 Profile Picture

sannavajjala87 6 Super User 2026 Season 2

Last 30 days Overall leaderboard