Migrating from OpenText™ Content Server to OpenText™ Content Server
Purpose
This resource summarizes the requirements, possible inclusions, and instructions for migrating data from one instance of OpenText™ Content Server (OTCS) to another.
Requirements
Supported Versions
Migrating from OTCS to OTCS is available for versions 16.2, 20.x, and 21.x.
Additional Requirements
The following are required for a successful OTCS to OTCS migration:
Cognitive Toolkit version 2.7.0 or higher
Content Server “Shinydocs Service” Module
Source Settings file for both origin and destination
Note: For source settings details, please review Source Settings in the Shinydocs Help Desk
To generally prepare for a migration, please also review Migration and Your Infrastructure and Preparing to Migrate: Questions to Consider.
Inclusions
The following details are/can be included as part of your OTCS to OTCS migration:
Document
Document Name
Creation Date
Last Modified Date
Owner
User Info
Document Description
Categories & Attributes
Content Server Classifications
Content Server RM Classifications
Content Server Document Versions
Note: Rerunning a migration will count content as new versions
Preparing inclusions as part of a migration
While some inclusions are part of a migration by default, others will require additional preparations. For example, categories and attributes, user information, and classifications, each require mapping files to apply these details to migrated content.
Categories and attributes
Including categories and attributes as part of your organization’s migration requires creating a mapping file. Once created, include the location of the file in the migration command as:
--metadata-mapping "C:\Metadata_File.json"
User Info
Including user information for migrated content also requires a mapping file. Once created, include the location of the file in the migration command as:
--user-mapping "C:\User_File.json"
Classifications
Including classifications as part of your organization’s migration also requires a mapping file. Once created, include the location of the file in the migration command as:
--classification-mapping "C:\Classification_File.json"
Also note that, if using RM classifications, the following parameter is required as part of the command in addition to referencing the classifications mapping file location:
--is-records-management
Workflow
To perform an OTCS to OTCS migration, complete the following steps:
Confirm the location of your source settings files and any additional mapping files that will be included in the migration.
Open Command Prompt as an administrator or a Service account that has permissions to the file directory to be crawled.
Change directory to the location where the Cognitive Toolkit is installed.
In a text editor such as Notepad++, copy the following command:
Migrate --destination-source-settings "C:\destination_source.json" -q "C:\match_all.json" -u http://localhost:9200 -i INDEX_NAME --start-location 123456 --threads 5 --metadata-mapping "C:\Metadata_File.json" --origin-source-settings "C:\origin_source.json"
Make the following updates to the command:
Replace the value for
--destination-source-settings
with the location of the destination source settings json fileReplace the value for
--q
with the location of the query json fileReplace the value for
--start-location
with the Node/Object ID for the folder in OpenText™ Content Server that is the migration destinationReplace the value for
-u
with the URL for the index that includes the data to be migrated (if required)Replace INDEX_NAME with the name of the index that includes the data to be migrated
Replace the value for
--origin-source-settings
with the location of the origin source settings json fileReplace the value for -
-metadata-mapping
with the location of the metadata mapping file (if including categories and attributes as part of your migration)Add
--user-mapping
"C:\User_File.json" and update the value with the location of the user mapping file (if including user information as part of your migration)Add
--classification-mapping
"C:\Classification_File.json" and update the value with the location of the classification mapping file (if including classifications as part of your migration)Note: If including RM classifications, also add the parameter
--is-records-management
to the command
Copy the updated command from your text editor to Command Prompt and run.
For additional details and specific migration options available, please review the Encyclopedia of Cognitive Toolkit Operations. For sample mapping files, please review Migration and Your Infrastructure.