When a decision is made to replace an ECM and bring in a new vendor, the task of migrating the contents of the old ECM into the new one can be daunting:

• Each system has it’s own collection of forms, schemas, and interfaces for moving content into and out of its repository
• ECM systems are not designed to support cross-vendor migration
• There can be significant volumes of content to migrate, at a high cost

The typical approach to this kind of migration project requires someone to map data associations, schema structures, and business rules between the old and new systems. Then, once this cross mapping exercise has been completed, a lengthy manual process follows which involves the application of these business rules and data associations to every item being migrated to the new ECM system. Because this is a manual process of large scope, the cost of labor is significant and the chance of human error is high.

Kapow has a better approach. Once the mapping of data structures and business rules between the two systems has been completed, robots can be written which automate the manual migration process, removing people from the equation. With our approach, it is not unusual to see reductions in migration time of 80-90% compared to manual approaches, with significantly fewer errors.