Conduct A Customization Audit
As the SharePoint farm expanded its footprint within organizations over the years, business requirements and expectations of SharePoint on-premises invariably grew. Many companies leveraged third-party add-ons to extend SharePoint functionality. Over time, several of these add-ons have either become indispensable components or maintenance nightmares that could impede SharePoint to Office 365 migration.
Loosely coupling SharePoint will ease future migration and improve interoperability, but requires its leaders to eliminate customization and uncouple tightly bound third-party add-ons. Assess your current business requirements against those you had at Day One, or whenever each third-party add-on was installed. Instead of taking the piecemeal approach of building customized code, evaluate application and data integration from a holistic enterprise architecture perspective:
There will be some pain in this approach, but it’s the best long-term strategy for getting the most value from your SharePoint to Office 365 migration.
Some vendors may launch their extensions as a new product, forcing you to repurchase the same capabilities for SharePoinOnline. -based tools, like any cloud service, will likely entail a metered or subscription-based model that will often differ from existing perpetual license models.
In the end, both SharePoint and your collective application portfolio benefit from efficiency gained from a loosely coupled architecture. Ensuring that your application extensions are less rooted eases the pain of SharePoint to Office 365 migration or a future move to an alternative platform.
Keep Reading >