• 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

Stellent / UCM Migration – Not as hard as you think

You are here: Home / Product Suite / OpenMigrate / Stellent / UCM Migration – Not as hard as you think

June 22, 2020

We are currently engaged with multiple clients to migrate content from aging systems built on the UCM / Stellent platform. This post will share our experience and our approach to mapping all the existing content to its destination system.

History of Stellent / UCM

Stellent was a leading ECM offering in the early 2000’s with offerings focused on Document Management, Web Content Management, Records and Retention, and Business Process Management. The platform was adopted by over 4,000 customers across multiple industries including many Fortune 500 companies. In December of 2006, Oracle saw the opportunity to improve it’s stance in ECM through the acquisition of Stellent and purchased them for $440M.

Over the years since the acquisition, Oracle did not substantially invest in Stellant and was eventually dropped from the Gartner list in 2019. From 2019 Gartner magic quadrant:

This vendor is redeveloping its strategy for the CSP market. Its focus is the Content and Experience Cloud, a product primarily aimed at B2C use cases and most typically associated with web content management technology. Oracle is not actively promoting WebCenter Content, its on-premises CSP, to new clients.

With better options available from modern vendors like Alfresco, many clients are considering upgrading from old Stellant repositories to modern platforms.

Stellant / UCM Migrations – Not as hard as you might think

At its core, Stellant / UCM systems are relational databases with pointers to content stored on a server or network drive. As in any migration, the key activity is to gather requirements so that it is documented, what content and corresponding metadata needs to be extracted from UCM and how is that going to map into the object model of the target ECM.

User Requirements and User Acceptance

Legacy ECM systems that have been in production 10+ years typically fulfill a variety of different user requirements and have customizations that have evolved with the system over time.  Functionality is often introduced as a major feature of the old system that doesn’t easily translate to the new system. Once the requirements are defined, we can configure OpenMigrate with a database / file system source and the desired target system. OpenMigate supports the following target systems, but due to the modular architecture new targets can be developed with relative ease:

  • Filesystem
  • Documentum
  • Alfresco
  • AWS/S3 and AWS/DynamoDB
  • Azure/HDInsight
  • Google/BigTable
  • Hbase/Hadoop
  • Solr
  • Elasticsearch
  • Veeva

The majority of the effort for this particular migration that we are currently engaged in is the mapping. When it comes to the metadata mapping, we are leveraging a wide array of mapping capabilities that OpenMigate offers including lookup tables, combining multiple source attributes into one target attribute, date modifications, and hard-coding values.

Migration Resources

To conduct a successful migration, resources need to be familiar with

  • The old ECM system and data
  • The new ECM system and data
  • The migration tool

Too often, clients will look to leverage their existing resources familiar with the old system to both develop the new ECM system, as well as understand the migration tool.  Typically these are resources that are still required to maintain the old ECM system.  Internal resources often lack the experience in both the new system and migration tool to fully understand the complexity of a large migration.

For Stellant / UCM, a combination of the existing Stellant / UCM support resources as well as dedicated TSG migration specialists familiar with the Stellant / UCM architecture, the new repository, and OpenMigrate has proven successful.

Migration Exceptions and Bad Data

Old systems typically have older documents.  In running our large migrations for clients we have found:

  • Bad File Pointers – content missing in source system
  • Duplicate Data – or content-less objects pointing to other records
  • Corrupt Content
  • Invalid File Names
  • Missing Metadata
  • Unknown File Types

To simplify Stellant / UCM Migrations, OpenMigrate has built in error correction and exception queues.  When OpenMigrate encounters a bad data exception, the bad document is logged as an error, but the migration continues, rather than halting the entire process.

There is one other unique challenge that this migration has provided which is documents in UCM which act as pointers or links to other content containing unique metadata, but share the same content. This approach was adopted may years ago as a hard disk saving architecture, but given the cost of a terabyte of storage today, the approach causes more headaches than the savings are worth. Our approach for these linked records is to migrate a copy of the content to the target system so that all records will have their own content and can be versioned without consequence.

Another example of bad data from this migration is that some date attributes were stored as text (not date objects) and in a variety of different formats. Through OpenMigrate configuration, we were able to convert these date strings to date values in the target systems.

Audit Trail and Compliance

When moving the documents, the compliance components of the new system need to be considered as well.  One common example is the document create date.  When created in the old system, the document create date was system generated. 

With Stellant / UCM, when moving documents to the new system, the new system might automatically generate the create date as the date of migration.  Typically TSG will recommend moving away from relying on system generated values to make migration easier and store and maintain create date in a non-system generated field maintained by the application.

Conclusion

A lot of companies are looking to the future of ECM whether that is SAAS, Cloud, NoSQL, or simply a more modern and capable system. Leveraging OpenMigrate as a migration utility can ease this transition by minimizing impact to users, speed migrations through multi-threading, and complete migrations in one step directly from the source to the target.

Filed Under: OpenMigrate

Reader Interactions

Leave a Reply Cancel reply

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

Primary Sidebar

Search

Related Posts

  • CMOD Migration to a Modern Environment
  • Capture 2.0 – Metadata Extraction with Machine Learning Upon Ingestion
  • Alfresco – Do More with OpenMigrate Services
  • AODocs Migration with OpenMigrate
  • FileNet Migration – Not as hard as you think?
  • FileNet Support – Migrating to mitigate the risk of an unsupportable product
  • FileNet Migrations – Best Practices for Large Migrations
  • Migrations – Why do they fail? (12 Worst Practices)
  • Mobius Content Services Migrations with OpenMigrate
  • IBM Content Manager and Content Manager onDemand (CMOD) Migrations – How to Migrate Quickly

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