TSG has recently begun a partnership with AODocs, a new player in the Content Services Platform space. This post will present some background on AODocs as well as demonstrate a Documentum to AODocs migration with our product, OpenMigrate.
AODocs Background
AODocs is a software solution owned by Altirnao. They are a new company founded in 2012 based out of Atlanta that caters to Google Suite users. AODocs is a true Software as a Service (SaaS) solution for a Content Services Platform with AODocs hosting the user interface and storing the metadata and having the content stored in the customer’s own Google Drive. AODocs recently entered the Gartner Magic Quadrant this year and is seen as an up and coming player in the content services space. Notable recent management team addition of David Jones as VP of Marketing adds considerable experience with David bringing years of experience from Hyland, AIIM, and most recently VP Product Marketing from Nuxeo.
AODocs and OpenMigrate
Our first step with AODocs was to add support for an OpenMigrate target. OpenMigrate has both source and target adapters that can be configured based on the type of migration being performed. Sources represent the repositories that content and metadata are being migrated out of. OpenMigrate has source connectors for FileNet, Documentum, Stellent, OpenText, Hummingbird, and a host of others, including file systems and legacy platforms. For more detailed information, visit our OpenMigrate product page. Targets represent the destination repositories. While developing a new target for AODocs, components that need to be migrated include:
- Content File
- Mapping to AODocs Document Classes
- Metadata
- Versions
- Folder Structure
OpenMigrate handles both the ingestion of content and metadata into Google Drive, as well as the linking of the content and setting metadata in the AODocs library.
See the video below demonstrating migrating content from Documentum to AODocs with OpenMigrate.
OpenMigrate Advantage
By using OpenMigrate to migrate content to AODocs, clients can take advantage of the all of the existing built-in features of the tool, including:
Multi-Threading Capabilities – provides for maximum throughput for high-volume migrations
Metadata Mapping – perform transformation/translation of metadata before pushing to AODocs
Migration Logging – provides detailed auditing/tracking of the success/failure status of all objects being migrated
Delta Migration – for a large migration, the ability to perform an initial bulk migration of the backlog of content and then perform a smaller “delta” migration to pick up any new or changed content since the start of the bulk migration
Summary
AODocs is a strong SaaS alternative for those looking to add enhanced content management features to Google Drive. With OpenMigrate support for an AODocs target, clients wishing to move to AODocs can do so from a variety of platforms.
Let us know your thoughts below.
Leave a Reply