OpenMigrate 1.7 Released: Enhanced Support for Documentum, Alfresco and SharePoint Migrations

With the new year comes exciting new product updates, and the  release of TSG’s migration framework, OpenMigrate version 1.7, leads the way. This release of OpenMigrate includes some new features as well as enhancements to existing features, as described after the jump.


One of the more prominent (and asked about) parts of this release is the development of a new migration target for SharePoint. This will allow clients to migrate data from their existing storage systems directly into SharePoint so users can make use of that collaboration environment.

TSG continues to provide a high-performance SharePoint source component.  By using the underlying database directly, large migrations run very quickly.


Enhancements to our Alfresco source and target components include:

  • Improved MIME type support
  • Ability to associate a node to an already existing node
  • Read all node properties during source export


We’ve extended OpenMigrate’s rich Documentum support to include:

  • DCM-like version label logic
  • Ability to set repeating attributes in the target via a JDBC query with multiple selected attribute values
  • Ability to infer the content type of a document based on its file extension with help from the dm_format table
  • Ability to specify renditions as optional when loading from the file system
  • Ability to include or exclude empty repeating values and null dates when reading from Documentum
  • Ability to append a unique “count” integer to the end of a object_name in Documentum if the same file name already exists
  • Improved support for documents linked to multiple folders

 Other Updates

Some of the other notable items include:

  • Enhanced Excel support to read formulas from an Excel spreadsheet, to properly handle repeating date values, and to use the latest version of the POI library
  • Enhanced email support, including the ability to connect to mail servers securely using SSL, and loading all message properties into the migration node
  • Extended metadata manipulation, such as offsetting dates, extracting a repating attribute’s value by index, and multiplying integers
  • The ability to use OpenContent’s extensive API libraries to interact with the repositories (without having to invoke a web service)
  • Several optimizations for very large migrations
  • Enhanced FileNet support, including more flexible “stitching” of multi-part images

Are there features you’d like to see included in OpenMigrate?  Let us know in the comments.

8 thoughts on “OpenMigrate 1.7 Released: Enhanced Support for Documentum, Alfresco and SharePoint Migrations

  1. All the DCTM enhancements to handle repeating attributes are very welcome.

    This was a major limitation in previous open migrate releases and we had complement OpenMigrate with custom scripts to migrate repeating values.

  2. Does it support migrating folder structures into Alfresco? The samples only migrate the files, but not the folders. And when I set the includeFolderObjects property in app-ctx.xml file, it produced an error:

    2012-04-27 12:32:43,360 891 src[0] INFO AbstractMigrationSource Exporting node [1], sourceId=Folder 1
    2012-04-27 12:32:43,360 891 src[0] ERROR NodeContentFileReader Error caught while loading content
    com.tsgrp.migration.error.MigrationNonfatalException: Unable to load content from fileLocationExpression=null or fileLocationAttribute=om_full_file_path
    at com.tsgrp.migration.event.NodeContentFileReader.loadContent(
    at com.tsgrp.migration.event.NodeContentFileReader.processNode(
    at com.tsgrp.migration.event.NodeContentFileReader.endExportNode(
    at com.tsgrp.migration.source.AbstractMigrationSource.fireEndExportNodeEvent(
    at com.tsgrp.migration.source.AbstractMigrationSource.exportNode(
    at com.tsgrp.migration.thread.SourceMigrationThread.process(
    2012-04-27 12:32:43,376 907 src[0] INFO AbstractMigrationThread Marking the node with source id Folder 1 as failed

    • @Sherwin,

      The includeFolderObjects property is not actually what you want in this case. You should just migrate your documents in, setting the om_folder attribute to the path you want; OpenMigrate will create any folders it needs along the way. There is no need to run a separate folder migration, nor any special configuration that is necessary. Well, there are rare circumstances where that is needed–but they are very rare.

      If you’d like to discuss it further, please don’t hesitate to send any questions to openmigrate[at]

      Thanks for your interest in OpenMigrate!

  3. Does OpenMigrate support Filenet IMS? Im not quite sure if Panagon libraries works for Content and Image Services. Regards JC

    • Jorge,

      OpenMigrate supports exporting from FileNet systems when metadata can be retrieved directly from the FileNet database and content can be retrieved directly from its storage location. When exporting images stored in FileNet, OM also has the capability of converting the images to PDF files upon export.

      If you any additional questions, feel free to contact us at openmigrate[at]

    • Kay,

      Yes, OpenMigrate is modular, so any migration source can be configured to migrate to any migration target regardless of which components are used.

Comments are closed.