migration-center and OpenText Extended ECM

Colleague | Thomas Berger | Round

by Thomas Berger
Project leader @ fme AG

December 12, 2019

Many of our customers have their ERP/business application such as SAP® deeply integrated within their technical landscape. In migration projects where OpenText Content Server is involved as an EDRMS, we are inevitably asked whether migration-center is capable of dealing with OpenText Extended ECM (xECM). xECM offers the integration between Content Server and many lead business applications such as SAP®, Salesforce®, Microsoft SharePoint®, Office 365®. This allows to directly connect the business processes (structured content) with the related unstructured content in a single view via so called Business Workspaces.

Migrating content into xECM Business Workspaces

With a variety of connectors, we can help you to migrate from any kind of source system to OpenText Content Server.

01 | Blogpost | migration-center and OpenText Extended ECM

The OpenText Content Server connector (Importer) has already proven its capabilities. It does a great job importing objects with transformed and newly mapped metadata in a controlled way into OpenText Content Server as it supports documents, folders, emails, categories with any kind of attributes, records management, security, physical objects and classifications.

Creating objects within xECM Business Workspaces

As mentioned above, we were often facing the requirement to import documents into xECM Business Workspaces connected to SAP or SharePoint. migration-center can migrate content into those workspaces as they are technically folders within Content Server – normally controlled and created by the leading business application. In many projects in the past the workspaces have therefore been created upfront prior to the actual content migration so that the entire migration project went smoothly.

Business Workspace creation through migration-center

Although creating the Business Workspaces upfront through the leading applications is considered as best practice, there can be situations where this is not desired or possible straight away. For example, this can be the case when a complete legacy business application needs to be merged into another business application and a lot of data has to be transferred along with the documents. In this case, migration-center can be of huge help to gather structured data from the source business system, which is then needed for the leading business application to create the workspaces. Typically, this is not a big issue in general, but can create issues regarding the timeline of the migration-project as workspaces creation can be a time-consuming exercise, although OpenText has done a great job improving the speed of workspace creation with one of its latest patches.

Consequently, the question often arises if migration-center could also create the Business Workspaces directly. We thoroughly analyzed this option but our opinion at this point is that the leading business application should control and create the connected workspaces and not a third-party tool. However, there are OpenText APIs we could utilize for this and we might integrate the creation of Business Workspaces as a new feature into the product in the future – but for now, we are not actively planning to do so.

If you have this requirement, any other questions or feedback, please don’t hesitate to send us an email: info@migration-center.com

02 | Blogpost | migration-center and OpenText Extended ECM

Extended ECM Platform

03 | Blogpost | migration-center and OpenText Extended ECM

SAP Fiori

0 replies

Leave a Reply

Want to join the discussion?
Feel free to contribute!

Leave a Reply

Your email address will not be published. Required fields are marked *