Streamline your content migration to OpenText Content Suite

Accelerate your project. Reduce expenses. Migrate now!

Logo | Square | OpenText Content Suite

Capable of handling even the most complex migration project

When it comes to the migration to OpenText Content Suite we offer a wide range of supported features. Migrating folders, containers, documents, emails, and physical objects to Content Suite is easy to accomplish whether on-premise or cloud. All different attribute types within custom categories are supported, as well as records management, classification, and ACLs.

Illustration | 07In-place migration & cleansing
Our in-place migration and cleansing capabilities allow clients to change workspaces, object types, metadata, folder structures, access rights etc. without migrating the objects from one to another repository. This feature is mainly used to clear up or enhance the data quality of an OpenText Content Server repository or simply to assign data to new business workspaces without executing a classic data migration. Original object IDs remain unchanged during such an in-place migration approach.

Illustration | 02Data quality enrichment
migration-center provides a huge set of capabilities to enrich the data and information quality of our client’s OpenText Content Server repositories. With individual metadata transformation and mapping capabilities, the integration of external information sources, or our artificial intelligence-based auto classification modules, our product supports clients to easily enhance the quality of metadata. This leads to faster retrieval of information and compliance improvement.

Illustration | 11Physical object migration
migration-center manages a large range of OpenText Content Server objects including physical objects (paper, microfiche, and other types of physical records). This capability helps Records Managers, Business Consultants, and Administrators to include the organization’s physical records in the migration strategy. During the migration of physical objects, all classifications, physical filed locations, access rights as well as other custom metadata are supported and mapped to the target system.

Illustration | 01Migration to xECM Business Workspaces
OpenText xECM offers the integration between Content Server and many leading business applications such as SAP®, Salesforce®, Microsoft SharePoint®, Office 365® etc. This allows to directly connect the business processes (structured content) with the related unstructured content in a single view via so-called Business Workspaces. In migration projects where OpenText Content Server is involved, migration-center is capable of migrating data/documents into OpenText Extended ECM Business Workspaces in a legal and audit-compliant manner.

Official OpenText Technology and Services Partner

Logo | Partner | OpenText | Technology
Logo | Partner | OpenText | Services

Six proven steps for your success

migration-center follows a best-practice-based migration process consisting of six iterative steps to ensure efficiency and accuracy. These steps can be performed independently and in parallel, making them fully scalable. The advantage is that they take place in migration-center’s database, which allows for the detection and correction of any transformation or mapping errors before the actual import.

Migration process | Step 1

Extract & analyze

All objects to be migrated to OpenText Content Suite are exported from their corresponding source system and can be analyzed in terms of type, format, metadata, and other properties.

Migration process | Step 2


The objects are now organized into manageable sets. Such a set is usually created from objects that have something in common and are to be processed in the same or a similar way.

Migration process | Step 3

Transform & map

Transformation rules are assigned to each migration set, which are used to generate the properties for OpenText Content Suite. The transformation is executed within migration-center.

Migration process | Step 4


The transformed metadata of the documents is tested and validated against OpenText Content Suite but without importing the objects.

Migration process | Step 5


Potential errors are detected during the transformation and validation steps and can be corrected in unlimited iterations of step 3 and 4.

Migration process | Step 6 | OpenText Content Suite


The transformed and validated objects are gradually imported into OpenText Content Suite.


Obtain important information on migration options to OpenText Content Suite with the help of migration-center: insights into possible use cases, supported source systems, and an overview of our migration process, all compiled on one page!

Thumbnail | Datasheet | Successfully migrate to OpenText Content Suite

View all features of your individial migration path

In order to show supported capabilities and versions, simply choose a combination of source and target system in the Connector Matrix below. migration-center supports content migration from databases, file shares, cloud platforms, legacy applications, and more systems to popular ECM platforms like OpenText Content Suite.

Source System

Supported versions:

Target System

Supported versions: 10.5, 16.x, 20.2, 20.4, 21.4, 22.4

Feature Category Support
Logo | Eon | Gray
Logo | Baker Hughes | Gray
Logo | Swiss Re | Gray
Logo | Intesa Sanpaolo | Gray
Logo | United Nations | Gray
Logo | Bosal | Gray

Professionalize your migration project

Explore the leading content migration software migration-center and all of its features by requesting our 14-days valid Free Evaluation Copy.
We are also there for you, should you have any further sales-related inquiries.

Free Evaluation Copy

Illustration | 09
1 Step 1

Private email addresses can't be considered!

reCaptcha v3

Sales Information

Illustration | 08
1 Step 1

Private email addresses can't be considered!

reCaptcha v3