New integration: OpenText Content Server 16.2

We are proud to present our new integration: OpenText Content Server 16.2

Using Tzunami Deployer you can migrate data from OpenText Content Server to Office 365 & SharePoint 2019, 2016 and more!

The migration Process:

1. Analyze
   Based on size, count, item types for export plan can be added as First Step
2. Export
   Extract data from OpenText content server
   Extract all basic and custom metadata along with content type (i.e. property set which can be mapped to Target Content Type, e.g. Alias in content server can be mapped to Link To Document Content Type in target)
3. Load
   Load imported source content and read your destination
4. Deploy
   Deploy content structure, metadata, security  using simulated Virtual Migration
5. Migrate
   Migrate all data and configurations to any SharePoint via CSOM as well as SSOM along with Migration API

Benefits of using Tzunami Deployer to migrate content from OpenText Content Server to SharePoint online & on premise:

• Rule Engine
  There are default predefined rulesets that comes with Deployer for the most common Deployment Practices. However, it can be used to customize many aspects of the Deployment Process from Deployment Structure to Mappings.
• URL redirection
  Redirects any requests for an item already transferred to its new location in SharePoint. This will prevent broken links (also within documents) and prevent users from modifying content that was already migrated into SharePoint.
  
• Link Resolver Service
  A component of Tzunami Deployer, which is required to fix links during migration. Fixing the link inside A to point to B. The Tzunami Link Resolver Service runs as a windows service.
  
• Migration API
  Tzunami Deployer Performs data migrations into Office 365 Utilizing Microsoft’s Migration API for higher throughput and avoiding throttling.
  
• Global MAPPING
  Map the entire setting, permissions, groups, properties, metadata, values once before committing into SharePoint. You can save and use the same global setting for your future migration projects.
• Filtering
  The exported source content can be filtered based on any type of the metadata.  Export only content that match a certain defined criteria. Content can be filtered during the export process itself based on metadata and desired conditions.
  
• Version Management
  Export items versions.
  Choose the types of item versions to export.
  Control deployment and migration deciding how you would like to manage version in transit to Office 365.
  
• Scheduling
  Run a migration during off-hours, weekend or any other time that fits your needs, you can schedule the migration plan to start when you are ready.
  

Supported versions:

OpenText Content Server 16.2.X
OpenText Content Server 16.X
OpenText Content Server 10.5
Livelink ECM 10.0.0
Livelink 9.7.X
Livelink 9.6.x

Read more about our OpenText migration tools here