I’ve been living in Jersey City for around 4 years now. It’s a great place to live, but one of the downsides is the traffic. New York City is right across the river, and depending on traffic it can take anywhere from 10 minutes to an hour to get there. Of course, there’s a lot of factors at play – the amount of traffic, what route I’m taking, how many lights I hit, whether any roads are blocked, the time of day, and the weather, to name a few.
Fortunately I live in the 21st century, and there’s a ton of technology available so I can plan accordingly and make sure that if I’m heading to New York, I can take the quickest and most efficient route. And the same thing goes for migration into Office 365.
I’ve been working in the SharePoint migration space for 10 years now, and one of the things I’m asked all the time is “How fast does it migrate?” Well, as I’m sure you know, this is a loaded question. Even a Ferrari can’t go anywhere in a lot of traffic. There’s a heap of other factors at play that impact the speed and efficiency of your migration. So, one of the most important parts of your methodology should be planning for these – and just like with the technology I use to get across the bridge to the city, AP Elements has the tech to help you plan for your migration.
Outside of AP Elements Fly solution, here are a few additional considerations to be aware of when mapping out your migration and avoiding roadblocks:
Network capacity, network stability, and network delays
A delay of more than 30ms will potentially slow down the migration process. Data will be transferred in 64K chunks to Office 365 over HTTPS with Fly. What’s more, a fast network doesn’t always result in fast migrations. If the network isn’t stable, data transfer can take longer to correct errors.
Office 365 throttling
You can use multiple Office 365 user accounts to establish connections to Office 365 when adding SharePoint Online site collections into Fly. This can be done with our Connection Manager.
On-prem SharePoint front-end web server and SQL capacity
Low-performance may result in a slow read from SharePoint with SharePoint APIs. Refer to Microsoft’s article for more details on performance and capacity test results and recommendations for SharePoint.
SharePoint site complexity
The complexity of the SharePoint site and total number of SharePoint objects, including versions from the version history, need to be migrated over to Office 365. The migration throughput will slow down if there is a large number of items in a SharePoint site. Filter out unwanted versions from your version history to cut down the number of items. Our pre-migration report can help you plan accordingly so you can promote larger sites into site collections or break them into multiple site collections.
Each migration job will use up to 200 MB of memory. For optimal performance, you can allocate more memory to have up to 20 concurrent migration jobs.
Remember, these items are valuable considerations in planning for your migration. Nobody wants a Ferrari to sit in traffic!