WilliamsWelsh9
07-21-2026, 01:27 AM
I've got a batch of SharePoint Online sites, around a dozen or so, that all need to be migrated together as part of a broader reorganization, and I wanted to check whether doing this in parallel is realistic or if it's better to tackle them one at a time.
The sites vary a fair bit in size and complexity. Some are small team sites with a handful of document libraries, while others have extensive permission structures, custom content types, and years of version history. My concern with migrating everything simultaneously is less about technical feasibility and more about managing the process without losing track of errors or inconsistencies across so many sites at once. Troubleshooting one broken permission set is manageable; troubleshooting the same issue across twelve sites in parallel sounds like a nightmare if you don't have good visibility into what's happening on each one.
There's also the question of throttling. I've read that Microsoft's API limits become a real bottleneck when you're pushing multiple large migrations at the same time, so batching or staggering might be necessary even if the tooling supports bulk migration.
I've been looking into the DRS Softech Tenant-to-Tenant Migration Tool (https://www.drssoftech.com/tenant-to-tenant-migration/) since it appears to support bulk site migrations with individual progress tracking and error logs per site, which would make managing multiple migrations at once far more practical than trying to coordinate everything manually.
The sites vary a fair bit in size and complexity. Some are small team sites with a handful of document libraries, while others have extensive permission structures, custom content types, and years of version history. My concern with migrating everything simultaneously is less about technical feasibility and more about managing the process without losing track of errors or inconsistencies across so many sites at once. Troubleshooting one broken permission set is manageable; troubleshooting the same issue across twelve sites in parallel sounds like a nightmare if you don't have good visibility into what's happening on each one.
There's also the question of throttling. I've read that Microsoft's API limits become a real bottleneck when you're pushing multiple large migrations at the same time, so batching or staggering might be necessary even if the tooling supports bulk migration.
I've been looking into the DRS Softech Tenant-to-Tenant Migration Tool (https://www.drssoftech.com/tenant-to-tenant-migration/) since it appears to support bulk site migrations with individual progress tracking and error logs per site, which would make managing multiple migrations at once far more practical than trying to coordinate everything manually.