FAQ: Migrate
Frequently asked questions about migrating data.
Sources and destinations
What migration sources & destinations are supported?
Shinydocs Cognitive Suite supports migrating from the following sources:
Source | Destination |
|---|---|
File Share | OpenText™ Content Server 16.2, 20.x, 21.x |
File Share | SharePoint® Online |
IBM® FileNet® | OpenText™ Content Server 16.2, 20.x, 21.x |
Microsoft® OneDrive | OpenText™ Content Server 16.2, 20.x, 21.x |
OpenText™ Content Server 16.2, 20.x, 21.x | OpenText™ Content Server 16.2, 20.x, 21.x |
OpenText™ Content Server 16.2, 20.x, 21.x | SharePoint® Online |
What details need to be considered in advance?
Shinydocs recommends considering the following three elements in advance of migrating:
Community model
What are the user/group structures implemented by your organization and used for metadata and security purposes?
Information model
What metadata (including RM metadata) will be applied to content?
What is the taxonomy model that will be used in the destination platform?
Security
How is the community model combined with the information model?
What taxonomy options are available when migrating?
Shinydocs offers three taxonomy options when migrating:
A recreation of the source’s taxonomy within the destination (minus the root)
A filtered recreation of the source’s taxonomy within the destination from a specified subpath in the source
Customized destinations within pre-existing folders in OpenText™ Content Server
What additional materials are needed?
If OpenText™ Content Server is your migration destination, installation of Shinydocs Content Server Module is required. For details, visit the Help Desk.
Can we complete a test migration first?
Yes. If you would like to understand how many files will be migrated in advance, migration tooling includes “dry run” functionality.
Alternatively, if you would like to complete a test migration to better understand the workflow, a migration with a subset of data can be completed to test the functionality.
Migration process
What can be migrated?
This varies depending on the source and destination of the migration.
Source-Destination | Inclusions & Options |
|---|---|
File Share to OpenText™ Content Server 16.2, 20.x, 21.x | Files, folders, permissions* |
File Share to SharePoint® Online** | Files, folders |
Microsoft® OneDrive to OpenText™ Content Server 16.2, 20.x, 21.x | Files, folders |
IBM® FileNet® to OpenText™ Content Server 16.2, 20.x, 21.x | Files, versions, folders |
OpenText™ Content Server 16.2, 20.x, 21.x to OpenText™ Content Server 16.2, 20.x, 21.x | Documents, versions, folders |
OpenText™ Content Server 16.2, 20.x, 21.x to SharePoint® Online |
*If OTDS is synced with the AD used in the File Share
** Document libraries only at this time
What details are migrated with content?
This varies depending on the source and destination of the migration:
Source-Destination | Details |
|---|---|
File Share to OpenText™ Content Server 16.2, 20.x, 21.x | Created Date, Last Modified Date, Owner, Index Insights mapped to Categories & Attributes, Content Server Classification Mapping, RM Classifications, Metadata Mapping, Permission Mapping, User Mapping |
File Share to SharePoint® Online | Created Date, Last Modified Date, Metadata Mapping, Classification Mapping, User Mapping |
Microsoft® OneDrive to OpenText™ Content Server 16.2, 20.x, 21.x | Created Date |
IBM® FileNet® to OpenText™ Content Server 16.2, 20.x, 21.x | RM Classifications, Metadata Mapping, Classification Mapping |
OpenText™ Content Server 16.2, 20.x, 21.x to OpenText™ Content Server 16.2, 20.x, 21.x | Created Date, Last Modified Date, Owner, Categories & Attributes, Content Server Classification Mapping, RM Classifications, Metadata Mapping |
OpenText™ Content Server 16.2, 20.x, 21.x to SharePoint® Online | Created Date, Last Modified Date |
Can a migration be delegated to a specific team?
Yes. Migration for your organization can be completed by a designated team. The team completing the migration requires permission to:
Connect to the index via HTTP(S)
Read and Open source data
Read and Write in the destination
Also, if the destination is cloud-based, either an Internet connection or a proxy allowing communication to the repository is required.
Post-migration
How do we communicate migration results?
Migration results can be viewed from the Visualizer. Depending on the source and destinations involved in the migration, the Migrated Files – File System to Content Server or the Migrated Files – OneDrive/SharePoint to Content Server dashboards provide a visualization of migration results to share with leadership and across your organization. You can also create a custom visualization to share with stakeholders.