• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar
  • Skip to footer
TSB Alfresco Cobrand White tagline

Technology Services Group

  • Home
  • Products
    • Alfresco Enterprise Viewer
    • OpenContent Search
    • OpenContent Case
    • OpenContent Forms
    • OpenMigrate
    • OpenContent Web Services
    • OpenCapture
    • OpenOverlay
  • Solutions
    • Alfresco Content Accelerator for Claims Management
      • Claims Demo Series
    • Alfresco Content Accelerator for Policy & Procedure Management
      • Compliance Demo Series
    • OpenContent Accounts Payable
    • OpenContent Contract Management
    • OpenContent Batch Records
    • OpenContent Government
    • OpenContent Corporate Forms
    • OpenContent Construction Management
    • OpenContent Digital Archive
    • OpenContent Human Resources
    • OpenContent Patient Records
  • Platforms
    • Alfresco Consulting
      • Alfresco Case Study – Canadian Museum of Human Rights
      • Alfresco Case Study – New York Philharmonic
      • Alfresco Case Study – New York Property Insurance Underwriting Association
      • Alfresco Case Study – American Society for Clinical Pathology
      • Alfresco Case Study – American Association of Insurance Services
      • Alfresco Case Study – United Cerebral Palsy
    • HBase
    • DynamoDB
    • OpenText & Documentum Consulting
      • Upgrades – A Well Documented Approach
      • Life Science Solutions
        • Life Sciences Project Sampling
    • Veeva Consulting
    • Ephesoft
    • Workshare
  • Case Studies
    • White Papers
    • 11 Billion Document Migration
    • Learning Zone
    • Digital Asset Collection – Canadian Museum of Human Rights
    • Digital Archive and Retrieval – ASCP
    • Digital Archives – New York Philharmonic
    • Insurance Claim Processing – New York Property Insurance
    • Policy Forms Management with Machine Learning – AAIS
    • Liferay and Alfresco Portal – United Cerebral Palsy of Greater Chicago
  • About
    • Contact Us
  • Blog

OpenText Migration to Alfresco – Best Practices with OpenMigrate

You are here: Home / Alfresco / OpenText Migration to Alfresco – Best Practices with OpenMigrate

February 18, 2016

Recently TSG worked with an R&D client to migrate content from two legacy OpenText repositories into a new Alfresco environment using OpenMigrate. This post will discuss the process used to perform the OpenText to Alfresco migration, as well as some of the technical challenges that were encountered along the way.

Careful planning is required for any migration. See our previous post – Document Migrations – What you need to know –  for more information on what to consider when planning for a migration.

OpenText to Alfresco Migration Strategy

This particular client had content stored in two different OpenText systems. The first system is Livelink, a legacy OpenText product which had been in place at the client for over 10 years. Plagued by browser compatibility issues and an aging infrastructure, the client was anxious to get a fresh start with Alfresco. Their Livelink instance contained 1.5 million objects (roughly 2TB) to be migrated.

The second OpenText system was an even older instance of BASIS Database. Similar to Livelink, this system was hosted on aging hardware and with limited client support. Nearly 100,000 documents needed to be migrated from BASIS to Alfresco.

To minimize the impact on the legacy systems, the client preferred a two-step migration strategy that used existing OpenText utilities to export metadata and content to a file system. The Livelink export process exported metadata in XML format, and the BASIS export process exported into a tagged plain text format. Following the export, OpenMigrate was used to read and map the exported content into Alfresco using OpenMigrate’s CMIS connector for Alfresco.

Migration Challenges

There were several technical challenges that came up during this project that are worth noting. The first was that OpenMigrate had never been used to migrate content from these OpenText exports before. The development team created new source connectors for OpenMigrate to parse the specially formatted metadata exports from both Livelink and BASIS. By leveraging OpenMigrate’s configurable mapping capability, the new connectors were combined with existing connectors to transform the metadata, read content from a file system, and upload content into Alfresco to meet the client’s needs.

Another challenge of the OpenText migration was the need to preserve folder and document permissions from the source OpenText systems migrate the permissions into the target Alfresco system. At a high level, permissions work similarly in both systems. An access control list (ACL) is applied to every object (file or folder) that grants users or groups access to the objects. At a more granular level, there are a number of key differences in the way that each system handles access permissions that proved to be challenging. Using OpenMigrate’s mapping layer, OpenText permissions were translated into Alfresco permissions, allowing for the same security to be applied to content in the new system.

Migration Process

After developing the source connectors for OpenText Livelink and BASIS exports, the process for executing the migration was straightforward and similar to other migrations we’ve run using OpenMigrate. One big advantage for the client was the ability to migrate one department or groups documents at a time. Per department/group we would:

  1. Suspend all content updates in the source OpenText system (viewing/downloading content was still allowed)
  2. Use OpenText export utility to export metadata and content from OpenText to the file system
  3. Use OpenMigrate to create the folder structure in the OpenText export in Alfresco, including any folder metadata and permissions
  4. Use OpenMigrate to upload all documents in the OpenText export in Alfresco, including metadata, permissions, and versions
  5. Use OpenMigrate log output to verify that all objects were migrated successfully and resolve any errors
  6. Allow users to access the migrated content in the new Alfresco system

As is the case for most ECM migrations, the success of this project was largely attributed to careful planning. We’re excited to now have source connectors for OpenText Livelink and BASIS available in the OpenMigrate tool belt.

Please feel free to comment below.

Filed Under: Alfresco, Migrations, Open Text, OpenMigrate

Reader Interactions

Comments

  1. Chris McCoy says

    February 22, 2016 at 8:41 pm

    I would like to know more about the details of the OpenMigrate tool. I have a number of BASIS Webtop installations that I need to migrate to a different DMS (Alfresco, Documentum, etc…)

    Reply
    • George says

      February 23, 2016 at 8:37 am

      Chris – you can get in contact with us here: https://tsgrp.wpengine.com/about/contact-us/

      Thanks!

      Reply
  2. Phil James says

    February 24, 2016 at 12:30 am

    Dave – nice blog!
    Phil

    Reply
  3. Gene Klamerus says

    July 22, 2016 at 8:34 am

    Dave,

    Nice blog. The issues with LiveLink go far beyond browser compatibility (although hopefully their new v 16 product will be both easier to use and more stable). The management of LiveLink takes a lot of man hours (in comparison with other similar products). I’m referring to their Content Server. The Archive Server (which is IXOS) is generally problem free. Good discussion regarding security/ACLs. We have also found that’s the biggest issue with migrations amongst Doc Mgmt products. The different products view of the world on how to control what users can do can be really problematic.

    Reply

Trackbacks

  1. Documentum sold to OpenText – Detailed Analysis and Predictions – Technology Services Group says:
    September 15, 2016 at 9:02 am

    […] perspective, Documentum is probably better than what OpenText has now.  We (TSG) have done both OpenText and Hummingbird migrations and, from what we saw of the core repository services, Documentum is […]

    Reply
  2. Documentum bought by OpenText – what do OpenText customers think? – Technology Services Group says:
    September 29, 2016 at 9:39 am

    […] we have said after our OpenText migration experience, we would have to say, from a core repository perspective, Documentum is […]

    Reply

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

Search

Related Posts

  • Alfresco – Do More with OpenMigrate Services
  • ECM 2.0 – One-Step vs. Two-Step Migrations
  • FileNet Migration – Recorded Alfresco/TSG Webinar – 05/29/2019
  • Migrating to Alfresco – Reducing Risk, Stress and Cost with a Rolling Migration
  • Redaction for AWS, Alfresco, Documentum and Hadoop – Bulk Redaction upon Ingestion or Migration
  • DocFinity – Migrating to Amazon S3
  • Alfresco Solutions of the Year 2017 – TSG wins Alfresco award for sixth year in a row
  • Documentum – What is the business case to replace it?
  • Alfresco Bulk Import Tool Versus OpenMigrate – What are some of the differences?
  • Data Visualization Dashboard for ECM Migrations

Recent Posts

  • Alfresco Content Accelerator and Alfresco Enterprise Viewer – Improving User Collaboration Efficiency
  • Alfresco Content Accelerator – Document Notification Distribution Lists
  • Alfresco Webinar – Productivity Anywhere: How modern claim and policy document processing can help the new work-from-home normal succeed
  • Alfresco – Viewing Annotations on Versions
  • Alfresco Content Accelerator – Collaboration Enhancements
stacks-of-paper

11 BILLION DOCUMENT
BENCHMARK
OVERVIEW

Learn how TSG was able to leverage DynamoDB, S3, ElasticSearch & AWS to successfully migrate 11 Billion documents.

Download White Paper

Footer

Search

Contact

22 West Washington St
5th Floor
Chicago, IL 60602

inquiry@tsgrp.com

312.372.7777

Copyright © 2023 · Technology Services Group, Inc. · Log in

This website uses cookies to improve your experience. Please accept this site's cookies, but you can opt-out if you wish. Privacy Policy ACCEPT | Cookie settings
Privacy & Cookies Policy

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Non-necessary
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
SAVE & ACCEPT