Quest is excited to announce the release of a new feature, which allows organizations to migrate their central repositories and their most crucial data, which are being managed as Records in SharePoint Online.
Info: The feature highlighted in this article has been released in March 2023. However, it is currently placed behind a Feature Flag within the On Demand Migration Platform. Should you wish to utilize this feature for your upcoming and ongoing migrations, please contact the Quest Support team with the following information:
- Quest On Demand Organization ID
- Quest On Demand Deployment Region
- Name of the Feature Flag to be enabled. In this case: migration.sharepoint.recordcenter.allow
Where can I find this new feature?
Once the Feature Flag has been enabled for your On Demand Organization, we kindly ask you to rerun the Discovery of your SharePoint contents within the On Demand Migration for SharePoint module. Once the Discovery is completed, you will be able to identify your SharePoint Sites, which use the “Records Center”-Template, being marked as “Supported” within On Demand Migration for SharePoint.
The migration of such Records and their “hubs” is now seamlessly integrated in the migration operation when using On Demand Migration for SharePoint for tenant to tenant migrations.
Along with (un)declared Records in SharePoint Online, the migration also includes:
- Sites using the “Record Center” Template and all Sites with Records Center Features enabled, such as “In Place Record Management” (including Microsoft Teams related SharePoint Sites)
- Record Declaration Settings (on Site Collection and List levels)
- Content Organizer Settings (on Site and List levels)
- List/Library Folder and Content Type Retention policies (on Site and List levels)
- Content Type Policy Templates
- Migration of Records Management related file metadata, such as Record status, Hold status, Exemption status and Retention stages
- Content Organizer Rules
- Holds migration
Known Issues & Limitations
Due to API limitations on Microsoft's side, the migration of your Records and Record Centers is not fully supported. Here are the known issues and limitations:
- The migration of Content Type Policies can only include basic actions, such as moving to the recycle bin, deleting previous versions, permanently deleting previously declared records, the new declaration of a record, skipping of stages, and deletion of draft versions.
- To migrate the Content Type retention policies, it is necessary to generate a SharePoint Token, similar to how On Demand Migration for SharePoint handles the migration of InfoPath forms. This is due to an API limitation, and we must rely on Native Web Services to perform this migration. Please contact our Support team at Quest Software for more information on how to create the SharePoint Token.
- SharePoint list item metadata is not included in the migration. The API currently limits the reading and writing of this type of metadata. All metadata for documents within libraries is fully supported and included in the migration.
By keeping these issues in mind and taking appropriate steps, you can ensure a successful and smooth migration of your Records and Record Centers using On Demand Migration for SharePoint.
For more information on this, and many other Features within On Demand Migration for SharePoint, check out the On Demand Migration User Guide, visit Quest.com or get in touch with myself via Gary.Hughes@Quest.com.