Content Matrix and Microsoft's New API Speed up Migrations by up to 30X (updated)
Migrations of anything but vanilla SharePoint collaboration sites to SharePoint Online (SPO) are significantly more complex and time consuming than most clients think they will be (and some vendors will have you believe). There are a number of reasons for this, an important one is the migration speed to SPO. I've addressed the others in the latter part of this blog post.
If you're using Content Matrix, after Microsoft’s announcement at Ignite of its new migration API, speed will no longer be one of the blockers if you're willing to use some best practices. The latest version of Content Matrix has been developed to deliver the fastest migration speeds to SharePoint Online in history, with improvements of up to 30X depending on workload.
So why does the speed matter? Until now, that migration speed has been far from optimal:
With Content Matrix' ability to migrate directly from detached SharePoint Content Databases, our clients have migrated most of their content directly from Azure VMs in the same geographical region as their SPO tenancies with only SQL Server installed on one VM and Content Matrix installed on one or more VMs. This along with Content Matrix' ability to multi-thread, run multiple jobs simultaneously from a single machine, run multiple parallel migrations from multiple Azure VMs and automate migrations using PowerShell magnified that ability to migration speeds between 3 GB/hour to 15GB/hour (see below). A vast improvement from the first chart.
Combining this with Microsoft's new migration API, those speeds have now soared:
Best Practices for Faster SharePoint Online Migrations:
Regardless of whether you're using a migration tool, or which migration tool you're using, before migrating to SharePoint Online, it's important to:
- Evaluate your company strategy and understand whether you need to make changes to your SharePoint farm as you migrate.
- Understand your content: Do you have stale content that no one is using any more? Why migrate that to SPO?
- Understand your SharePoint Inventory: Do you have site templates, list templates, custom web parts, full trust code solutions, sub site numbers, list view thresholds, or other settings that are not supported in SPO? Those will not migrate and it's better to know that up front then mid-migration.
- Determine if you'd like to leverage new and exciting functionality in SPO such as Community Sites, Video, etc.
- Ensure your resulting search results are better than they were before – improve your Information Architecture
Once you've taken these steps, and you've got a migration and remediation plan in place, it's time to execute your migration. From this point on, it's all about speed. Content Matrix plus Microsoft's new migration API were built to help companies get to the cloud faster than ever before.