Factors to Consider for SharePoint Migration

Many factors affect the speed of migration from on-premises SharePoint to SharePoint Online depending on the source and destination. Invariably this kind of migration involves the use of some toll. The natural question that arises then is how long will the migration take? While it is difficult to predict the actual time it will take based on factors such as system load, bandwidth, average item size, and bottlenecks in source or destination, some sites incorrectly claim impossible speeds such as 5GB per hour or 10GB per hour. This is not always true as there are different aspects such as the infrastructure set-up and complexity of content & site objects.

Handling the Infrastructure Set-Up

The first phase of working with the infrastructure is the process of identifying the number of migration servers. The initial task is the content inventory analysis phase to understand the content size, content depth, site objects, any custom functionality involved, etc. The size, content depth, and tentative deadlines can help identify the number of servers that might be required for the migration. Migration tests can help in establishing baselines.

Network Quality Factors

There are two primary network factor considerations for SharePoint migration. The first is the network latency which determines the quality of the connection between the data center and the two ends which are the source and destination. The other factor is network speed. This is decided by the internet speed and availability.

Actual SharePoint Migration Process

The type of SharePoint migration that will be performed impacts the time for completion. The SharePoint migration partner will plan a strategy that is tailor-made to the requirement of the business based on the content that is being moved. There are two types of migration paths that can be followed. We will discuss them briefly in the following sections.

Content Only Migration

In the case of content only migration, there is a simple transfer of contents like from one document library to another, sharing of a file to a document library, or transferring data from one OneDrive tenant to another OneDrive tenant. You can directly estimate the throughput once the infrastructure is set up. In this type of migration, the focus is on the content and its permissions. The throughput is not fixed as every SharePoint On-Premises to SharePoint Online migration client is different. Such migrations are common when users have to be moved on cloud based technologies like Desktop as s Service.

Site Objects and Content Migration

In this type of migration from the source to the destination, there is a much larger scope. This type of migration is more generic and can be applied to migrations from SharePoint 2007 or methods to migrate SharePoint 2010 Migration to SharePoint Online. It can be even used to migrate SharePoint from On-Premises to Office 365, i.e migrating from SharePoint on-premises to SharePoint Online. This form of migration requires extensive testing and is often riddled with several change requests. It is also slower with significantly lower throughput and often requires expert assistance who use special tools for the process.

Opting for Hosted SharePoint

If you need to maintain your SharePoint existing SharePoint solution, migrating to hosted SharePoint might be a good solution as you do not have to worry about the infrastructure. As a tier 1 Microsoft CSP, Apps4Rent provides hosted SharePoint solutions along with SharePoint Migration Services at promotional prices with 24/7 phone, chat, and email support.

Leave a Reply

Your email address will not be published. Required fields are marked *