SharePoint benefits encourage businesses to migrate their file server data online. However, there are at least 7 limitations of SharePoint Online and OneDrive that need to be effectively addressed to reduce migration costs and eliminate OneDrive sync failures. In this article, we'll identify some of the common issues that complicate SharePoint migrations and ways to simplify the migration and solve the issues. Here's a list of common issues: 5,000 item limit in a document library 100,000 item sync limit for the OneDrive client NTFS permission reorganization requirements Maximum name length limitations Prohibitive costs of data reorganization 93 day recycle bin threshold Lack of support for legacy application data (databases, etc…) Obviously, you may not hit every issue in each migration but migrator beware if there's a lack of awareness of how these limitations could impact user experience, productivity, and cost. A Real-World Example Before we discuss each of these items
File Server Migration vs File Server Mobilization File server migration is commonly viewed as an easy, cost-effective way to address the modern workforce’s increasing need for mobile productivity and security. But moving file server data to a cloud service that is not 100% file-server compatible often leaves much to be desired in the following areas: Mapped Drives and File Server Compatibility Backup, Protection, and Recovery Application Compatibility Compliance, Control, and Privacy Reduced Migration Complexity and Costs File server mobilization resolves these issues with 100% file server compatibility SharePoint, Dropbox, Google Drive, and similar services are all based on file server migration. And that’s why so many of their customers have problems in these areas. To address them, file server migration must be replaced by file server mobilization – an approach that fully addresses mobile productivity and security BUT also maintains 100% compatibility with file server use cases.
Challenges of Legacy Application Modernization Legacy application migration often presents a prohibitive set of challenges for businesses seeking to modernize and adapt their applications with best-of-breed cloud services, such as AWS, Azure, and Google Cloud Platform. Despite the compelling business drivers pushing them to complete digital transformation the cost and complexity of rebuilding these legacy applications to become cloud-native often forces them to seek alternatives. The common answer is a “lift and shift” approach where the application and its existing data are essentially “lifted” from the on-premises environment and “shifted” to new hosting premises in the cloud with minimal changes. This reduces the migration costs and complexity since the application is essentially moved to cloud-based servers with almost no changes in architecture, schemas, or any other aspects of the design. For example, an organization may decide to migrate QuickBooks or an ERP application from loc
Comments