Migrating from Legacy ECM Repositories to Alfresco Ray Wijangco Technology Services Group Alfresco Practice Lead

Overview Migration Pains Migration Methodology & Common Approaches OpenMigrate Migration Framework Migration Case Studies

Why are migrations complex? The outcome of any migration is simple: However, the requirements for a migration are often numerous and complex Point A Point B

Complex Migration Requirements Which documents will be migrated? Document type Document format Lifecycle state Creation date Modify date Folder path Do related items need to be migrated? Versions Renditions Relations Folders

Complex Migration Requirements How will metadata be mapped? Document type Folder path Security Versions Additional document attributes Do other constraints need to be taken into account? System downtime Migration throughput Migration audit trail

Legacy ECM can be a Black Box Limited or no support for platform No internal expertise Old hardware Missing or orphaned content Significant data cleanup required

Migration Methodology Requirements Gathering & Analysis Source System Cleanup Target System Setup Migration Run Book Development

Migration Methodology Unit Testing Benchmark Testing Data Verification & Acceptance Testing Migration Execution Delta Execution

Typical Migration Approaches Onetime Migration All content is migrated during a single cutover period Staged & Delta Migration Majority of content is migrated during a staging period New and updated content is migrated during the cutover period Rolling Migration Content is migrated to new system only when needed in the new system

Simplifying Migrations Moving documents is a lot like moving homes—you can do it yourself, but you might get half way and regret your choice Professionals have the right tools and skills

What is OpenMigrate? A high performance migration tool for one- time or ongoing migrations A Java based, open source framework made up of highly configurable and extensible migration components A proven methodology developed to assist TSG clients in the migration of their content between locations

OpenMigrate Architecture

OpenMigrate Architecture Features Open source framework Platform agnostic System specific API based adapters Heavily configurable High volume throughput “Node” based architecture Flexible mapping component and listeners support data manipulation and cleanup Supports delta migration approach

OpenMigrate Source & Target Adaptors Source Adaptors Alfresco Documentum FileNET File System Hummingbird OpenText SharePoint Qumas Database Target Adaptors Alfresco Documentum File System SharePoint

OpenMigrate External OM runs as a standalone, command line Java application Ideal for onetime migrations Leverages Alfresco CMIS API / RESTful services

OpenMigrate Embedded OM is embedded as Alfresco subsystem Provides access to Alfresco Java API Migrations are easy to execute via web script and in a repeatable manner

OpenMigrate and Bulk Import OM stages content and metadata and calls the Bulk Import Tool to execute import into Alfresco Allows system functionality and business logic to be seamlessly captured Target Adapter

Case Study: Continuous Ingestion Large Retailer importing inventory reports into Alfresco. Reports available in front-end portal Places in watch folder, uploaded every 2 minutes. User configurable as Share Action.

Case Study: System Upgrade Medical association upgraded from community edition to enterprise edition Original implementation not scalable Content was migrated directly from the existing community system to the new enterprise system Re-architected for better performance Content architecture was redesigned

Case Study: Staging & Delta Migration Client rolled out legal management system to 48 different offices OpenMigrate used in conjunction with Bulk Import Tool In total, five million documents from shared network drives were imported Offices were on boarded in waves of 5-10 offices Majority of content imported during week prior to office onboarding Delta migration performed before official go live

Case Study: Ongoing Ingestion New York Philharmonic bulk ingests all digitally archived content Can ingest up to 45,000 documents a day New assets continually being scanned and digitized for import into Alfresco Externalized rendition process Integrates from metadata sources with assets Drives OCR processes Publishes metadata to external Solr

Resources TSG Web Site TSG Blog Visit the TSG Booth!