OpenText Content Server Migration
Tzunami Deployer for OpenText Content Server Migration
OpenText Content Server is a document management solution provided by OpenText. Today, most organizations struggle with difficulties of migrating from OpenText Content Server into SharePoint and Office 365.
Using Tzunami Deployer for OpenText Content Server, you will simplify the most complex migrations and transform data from OpenText Content Server to Office 365 or any SharePoint On-premise as fast as possible.
Tzunami Deployer enables migration of numerous data items from OpenText Content Server to SharePoint products and technologies. The solution was developed with a worldwide service integrator & consultancy company.
Tzunami Deployer for OpenText Content Server Migration Tool is part of the Tzunami Deployer Family of Products, which has been developed specifically to respond to all advanced OpenText to SharePoint migration requirements such as OpenText Content Server to SharePoint Online, SharePoint 2013, SharePoint 2016 and SharePoint 2019.
This migration tool fully supports enterprise content migration from OpenText Content Server to SharePoint.
Tzunami OpenText Content Server Exporter is easy-to-use and convenient solution to extract content from OpenText Content Server via REST API. Our OpenText Content Server migration solution allows extraction of all content within your local infrastructure.
With the ability to connect remotely to the OpenText Content Server, administrators can easily choose the content to be migrated from OpenText Content Server to Microsoft 365.
Tzunami Deployer for OpenText Content Server migration has the ability to run exporters using easy to use user interface as well as with command line, allowing multiple exports as part of a script. The exporter has simple user interface and lets you quickly extract contents such as Discussions, Compound Documents, Channels & News, Tasks & milestones, Projects, Documents, Aliases, Link, Generations and more.
With Tzunami OpenText Content Server Exporter we do support extraction of content from OpenText Content Server deployed locally or hosted on the cloud.
How to transfer your content from
OpenText Content Server to SharePoint?
With Tzunami Deployer, you can easily migrate OpenText Content Server to SharePoint with our 4 unique steps.
Migrate OpenText Content Server to Office 365 and any other SharePoint version like SharePoint 2013, SharePoint 2016, and OpenText Content Server to SharePoint 2019.
Tzunami Deployer for OpenText Content Server allows users to export the following items from OpenText Content Server:
• Personal Workspaces
• Enterprise Workspaces
• Discussions (Topics and Replies)
• Tasks (Tasks Lists, Tasks Groups, and Tasks) and Milestones
• Channels and News
• Documents and Compound Documents
If you have any query regarding this format of files, please email to [email protected]
Tzunami OpenText Content Server Exporter uses the API to extract the content and associated ACL information. The exporter provides an option to export the security or not.
Based on the option checked or unchecked security ACL information is exported.
There is a limitation of the source server that Content Server version 16.0.x does not provide the API to extract the security information. However, the exporter includes a workaround to overcome this limitation. First of all, you must export the ACL and Users information in separate two files for Content Server item in a specific format before running the exporter.
At the beginning of export, you need to provide the location of those files for ACL and users information.
For details regarding security please contact the Tzunami Support Team at [email protected].
OpenText Content Server credentials are used for the OpenText Content Server API. These are the same credentials that users use to log-in in order to access the OpenText Content Server portal.
The account provided to the OpenText Content Server Exporter should have the following
OpenText Content Server permissions:
- Log-in enabled
- System administration rights
Tzunami Exporter for OpenText Content Server provides the ability to run export sessions non-interactively using command line instructions. This allows administrators to plan and schedule long running migration jobs through scripts, batch files and schedulers according to needs and organizational timetables. To run the exporter in batch mode you will need exporter specification file explained in the ‘Choose Destination Folder’ step of the export wizard. The file contains all the export option details including:
- Source ECM connectivity information (Server Address, User Name, Password etc.)
- Items to export
- Destination and Log Folder
- Exporter specific options
This file can be edited to suit your needs however the XML schema of the file should not be altered. It is recommended that you generate a sample specifications file in the Destination
Folder Screen selection step of the export wizard and use it as a template to create your own specification file.
Based on your needs you can create number of specification files and use them to run multiple export sessions as batch commands.
After the extraction process completes successfully, you are prompted to load the exported data into the current Tzunami Deployer project and migrate your data.
Tzunami Deployer provides Auto deploy and manual deploy processes. In auto deploy process, all required security, property and value mapping are automatically deployed when you drag and drop the content from source system to target. In manual deploy process, mapping wizards for security, property and value mappings are displayed subsequently deployed when you drag and drop the content from source system to target.
Link Resolver Service is used to manage the links in migrated content to point to target source after migration. It can be installed in any machine in network and is installed as Windows Service.
Tzunami Deployer should point to LRS. Tzunami Deployer provides an option Update LRS DB. When this option is checked, henceforth the items migrated successfully are updated in the Link Resolver Service’s database. Any instance of Tzunami Deployer can identify the migrated items from other instances of Deployer at the runtime without reloading, provided that the instances of Tzunami Deployer are pointing to same Link Resolver Service.
- Therefore, there is no need of reloading process for the information of latest changes made in target through other instances of Tzunami Deployer.
- The reloaded information of target from an instance of Tzunami Deployer is available to other instances of Tzunami Deployer instantly. So, reloading items in each Tzunami Deployer is no longer needed.
- Since the reloaded information of target items from an instance of Tzunami Deployer is available to all other instances of Tzunami Deployer, the operational cost of reloading needed in each instances of Tzunami Deployer is reduced.
- Incremental migration of same item in same library can be accomplished with reloading library only (not all items necessarily).
Tzunami OpenText Content Server Exporter uses a default license that can be used for evaluation purposes. This license is limited in the number of items that are exported. If the license does not match your evaluating needs, contact [email protected] for an extended license. For this purpose you will need to provide the Product Serial Code, and then enter the License Key you receive back from Tzunami.
OpenText Content Server 16.2.6
OpenText Content Server 16.x or later
OpenText Content Server 20.x and up
You can install Tzunami OpenText Content Server Exporter on any machine from which you can connect to OpenText Content Server.
The following list include the minimum system requirements for Tzunami OpenText Content Server
Exporter Version 3.4.
Computer and processor: 2GHz Pentium processor or equivalent
Memory: 2 GB (Minimum); 4GB (Recommended)
Hard disk: 50Mb (additional space will be required for the Tzunami Deployer projects, which may vary from 10 Mb to 4 GB).
Supported Operating System: Windows Server 2008/2012, Windows 10 as client OS.
Supported Architectures: x86 and x64
Network: Intranet/Internet access depending on connectivity requirements
Display: 800 x 600, 256 colors (minimum); 1024 x 768 high color
Microsoft .Net Framework 4.7.2 or higher (including versions 2.0, 3.0 and 3.5).
Tzunami Deployer enables organizations that wish to migrate OpenText Content Server to SharePoint and dramatically reduce migration costs. Using Tzunami Deployer, the time required for a SharePoint content migration project is significantly reduced compared to the traditional labor-intensive processes. Tzunami Deployer supports migration to target SharePoint Online using Migration API (and CSOM when necessary), Tzunami Link Resolver and Redirection Services. Tzunami Deployer for OpenText Content Server enables you to prepare for your migration project in an offline simulated environment. Any changes performed in Tzunami Deployer do not affect the Opentext Content Server data. SharePoint cloud and server will only apply changes when chosen to migrate.