Vyapin\u2019s DocKit Migrator<\/strong><\/a>.<\/p>\nCopy site and list UI elements<\/h2>\n
One of the major headache for users who are performing a migration from on-premises to SharePoint Online (Office 365) is to maintain the same look and feel (webparts, navigations, quick links etc.) in SharePoint Online as the source SharePoint site, in order to maintain the current sites look and feel for end users.<\/p>\n
In addition to this, if you have any customization in the look and feel then migration becomes even more difficult. You won\u2019t be able to migrate those items using the Microsoft\u2019s SharePoint Migration Tool, whereas Vyapin\u2019s Dockit Migrator can copy site and list UI elements seamlessly<\/strong>.<\/p>\nMigrate Workflows<\/h2>\n
Now a days workflows are most commonly used among users of SharePoint. Microsoft provides a lot of built-in workflows in SharePoint and also provides the flexibility to configure the workflows through the SharePoint designer. So, most of the companies use workflows in SharePoint for their business purposes (either the built-in workflow or a custom workflow or a third party workflow). Creation of such workflows again in the new SharePoint Online (Office 365) site (where the source contents are to be migrated) is a very tedious job. So it would be better if the migration tool itself handles such workflows. Microsoft\u2019s SharePoint Migration Tool lacks this feature (may be they will add this later), whereas the Vyapin\u2019s DocKit Migrator tool allows migration of workflows<\/strong>.<\/p>\nEnrich or Modify Metadata through a Metadata File<\/h2>\n
Most of the organizations don\u2019t want to migrate unwanted\/unused content and they would like to tag additional or new metadata or make corrections to existing metadata (to index and search the documents in SharePoint), when performing migration from file servers to SharePoint Online (Office 365). Applying a reorganized metadata structure on the fly during migration to SharePoint Online need to be automated instead of reorganizing metadata after the documents are migrated. Reorganizing metadata in an automated manner is also lacking Microsoft\u2019s SharePoint Migration Tool. Along with advanced metadata handling capabilities, Vyapin\u2019s DocKit Migrator also provides features to flatten a folder hierarchy or re-parenting folders<\/strong>.<\/p>\nReplace illegal characters on the fly<\/h2>\n
The biggest trouble for users when performing migration from file shares to SharePoint Online is when document names contain characters in file shares that are not acceptable to SharePoint. Even though Microsoft\u2019s SharePoint Migration Tool does provide the facility to skip those files and folders from migration it does not provide options to replace or modify illegal characters with SharePoint friendly characters. Vyapin\u2019s DocKit Migrator tool has powerful features to replace illegal characters on the fly using rules<\/strong>.<\/p>\nScheduling<\/h2>\n
The ability to break up a migration project to multiple migration tasks at scheduled times<\/strong> is a powerful feature available in Vyapin\u2019s DocKit Migrator, for example, when the migration needs to run during\u00a0 off-peak hours without disturbing production during peak hours. Microsoft\u2019s SharePoint Migration Tool lacks this feature.<\/p>\nSupported Platforms<\/h2>\n
Vyapin\u2019s DocKit Migrator handles all Microsoft supported SharePoint platforms<\/strong> (SharePoint Server 2019 \/ 2016 \/ 2013 \/ 2010 \/ 2007 and SharePoint Online) as source, whereas Microsoft\u2019s SharePoint Migration tool currently supports only SharePoint 2013 as a source.<\/p>\nHere is a more comprehensive checklist comparing Microsoft\u2019s SharePoint tool and Vyapin\u2019s DocKit Migrator.<\/b><\/p>\n