Have you been using an intranet on SharePoint 2010 for years, while it’s high time to get a modern solution on SharePoint 2016? Do you support SharePoint On-Premises, while the rest of your corporate software has been already running in the cloud? Do you use scattered collaboration apps but want to unite them all under the same hood? If your SharePoint story is similar to one of the above scenarios, your only way to enter a better SharePoint world is through SharePoint migration.
However, a promising way to an improved SharePoint experience, migration comes together with numerous challenges and risks that often lead to negative outcomes. According to the 2017 SharePoint and Office 365 State of the Market Survey by Concept Search, almost 40% of all SharePoint migration projects fail. Not only can organizations underestimate their migration investment, development, and customization effort, but also they can choose the wrong migration path.
In this article, we will explore three available migration options, listing their challenges and advantages, to help you decide which SharePoint migration plan is optimal for you.
Organizations keep their server-based deployments if they want to preserve their IT infrastructure, solutions’ logic, and collaboration models unchanged, as well as to stay away from compliance and security debates. At the same time, even if your company sticks to SharePoint On-Premises, you shouldn’t leave your solution unchanged for years. To keep in step with the platform advance and meet users’ growing demands, you can go for SharePoint upgrade or migration.
When you perform a SharePoint upgrade, you move up to the next version of the platform using Microsoft-supported upgrade methods, including the database attach technique and in-place upgrade. When you choose a SharePoint migration, you can move to any version of SharePoint from any third-party application or from SharePoint itself through an automated or manual migration process. To add more, migration implies SharePoint’s physical movement to a new farm along with the solution’s restructuring.
Multistage migration. Until now, there are no Microsoft-enabled methods to jump through several SharePoint versions in one leap. For example, if you currently run a SharePoint 2013 solution and you are waiting for the SharePoint 2019 release, you will come to the final point only by moving to SharePoint 2016, first, and then by making the second migration step to SharePoint 2019. You can solve this issue using SharePoint migration tools; however, they will require additional effort, investment, and technical skills.
Rework is necessary to get visible benefits. If you just migrate your existing solution to the latest SharePoint version without any changes, there will be little to no visible advantages for end users, which can bring migration effort to nothing. Once you take up SharePoint migration, consider improving the solution along the way. Introduce new features, refresh the solution’s design, and make it mobile-friendly to get users’ loyalty.
You will still lag behind cloud solutions. If you stay on-premises, accept that your solution will lack capabilities available in SharePoint Online and Office 365. For example, SharePoint On-Premises owners can’t use communication and hub sites available in SharePoint Online, while Office 365 subscribers can benefit from a whole array of productivity apps beyond SharePoint.
SharePoint migration to Office 365 or Microsoft 365 is very popular today due to the great popularity of the cloud collaboration suites. Cloud migration can be particularly beneficial for companies running outdated solutions. Instead of diving into a complex on-premises migration, they can move directly to the cloud and start a new collaboration experience.
Differences in solutions’ logic. If you got used to the SharePoint On-Premises structure, it can be hard to accept the one of Office 365 at once. As we’ve mentioned, in SharePoint Online, you can find more types of collaboration sites. Besides, there are critical functional differences. For example, the cloud-based SharePoint lacks MySites. So, if your current on-premises deployment has well-developed MySites with employees’ blogs and document storages, you will have to distribute them across Office 365 apps, Delve or SharePoint blogs, OneDrive and SharePoint document libraries.
Collaboration overload. End users might feel confused about the abundance of collaboration tools in the cloud. That’s why you should consider beforehand how to avoid a collaboration chaos and how to make employees use Microsoft Teams, Yammer, SharePoint, Skype for Business, and Office 365 Groups effectively in line with their collaboration needs and your corporate policies.
Management concerns. When it comes to migrating to Office 365, multiple concerns seize SharePoint owners. Some organizations are pulled back by Office 365 ownership and security matters, some of them worry about limited customization capabilities, and some reveal the negative side of ongoing monthly payments.
All in all, if you aren’t ready to accept Office 365 rules, then it’s reasonable for you to look at the third migration option.
The SharePoint hybrid deployment model started to gain popularity together with the Office 365 advance, as it enabled companies to benefit from both on-premises and cloud worlds. The 2017 SharePoint and Office 365 Survey proves that hybrid deployments are much in demand, so your organization can also choose it as the SharePoint migration goal.
SharePoint On-Premises version matters. If you still run an older version of SharePoint On-Premises, thinking about a hybrid solution is unreasonable due to the huge gap between them and Office 365. Microsoft put great effort into hybrid experience within two latest versions of the platform in order to make it easier to use and manage, so choose SharePoint 2013 or 2016 to start your hybrid experience.
Double management effort. Hybrid deployments are the most complex in terms of management, as you have to balance content, features, compliance, and administration within both on-premises and cloud environments. Before going hybrid, make sure your admins can handle the deployment, otherwise look for SharePoint consultants who will take up the hybrid challenge.
Hybrid disruption. If managed inappropriately, a hybrid environment can transform from a business enabler into a headache maker. Data inconsistency, site collections randomly hosted on servers and in the cloud, badly set search are just a few things that can hinder employees’ experience in hybrid SharePoint.
|On-Premises Upgrade & Migration||Cloud Migration||Hybrid Migration|
Now, let’s take a quick look at the SharePoint migration process itself. Here are possible ways to fulfill a migration project.
Do it yourself or delegate. If you have an in-house team of SharePoint developers and admins, you can migrate on your own.
A DIY migration is risky, though. As many internal projects, it can become a secondary activity for developers to take up in their free time. This way, a migration can become a long-lasting project, while employees will have to use half-baked solutions. If you don’t have available internal specialists, better go for SharePoint consulting and hire an external team to complete the migration project as required.
Use migration methodologies and tools. The larger your deployment is, the more time and effort you have to spend on SharePoint migration.
Fortunately, to make the process faster and easier, you can use dedicated SharePoint migration tools and methodologies from such vendors as Sharegate, Metalogix, AvePoint, Ampio Solutions and more. Remember that tools can’t handle the entire migration but they can help developers speed up particular migration steps. For example, tools enable you to analyze the initial deployment and reveal issues that can affect the migration process or move large content libraries automatically.
Cooperate with Microsoft. Microsoft launched their own free SharePoint migration tool in 2017 to help Office 365 subscribers migrate their contents from SharePoint On-Premises to SharePoint Online or Office 365.
Apart from that, owners of SharePoint 2010 and 2013 can use the SharePoint Migration Assessment Tool (SMAT) to scan your SharePoint environment and identify existing problems before migration. Companies can also benefit from the Microsoft FastTrack migration program that offers the assistance of Microsoft experts during cloud migrations to Microsoft 365, Azure, and Dynamics 365.
SharePoint migration isn’t just a technical but also a strategical task. That’s why without a preliminary planning you risk joining the companies with failed migrations. Once you choose the final destination of your migration, analyze your existing solution and decide how you can optimize it so that end users can see clear migration benefits. Apart from potential technical issues, consider possible adoption challenges and draw up a user adoption strategy beforehand, particularly if you switch from on-premises deployments to the cloud.