Migrating Content to IBM Connections
In my previous blog, I summarized the components of the Move to Connections offering from our services team
This week, let's dive a little deeper into how content is migrated, staying with the Jive example.
The migration of Jive content into Connections is completed using IBM Content Migration Factory, following an Extract, Transform and Load (ETL) process.
Extraction of content is achieved using a migration software tool. The tool identifies content for migration using a web spider approach. The extraction process takes an ‘offline’ copy of the content items and stores them in the software repository. This ensures there is no impact on the current content as it exists in the Jive places.
Transformation of the content is then applied once the content has been identified, it is processed through the migration tool engine. This process involves a series of steps/tasks that perform the required transformations to enable the content to fit the target environment. These transformations can range in complexity depending on the source content structures and its intended target. For Jive content, we have a specific set of transformation rules that accelerates this step.
Loading the content into the Connections instance is the final step after the content has successfully been processed to meet the target requirements. This load process leverages the published API of the Connections instance, ensuring the content is processed through the recommended Connections interface.
All content that has been through the migration process is fully auditable and a mapping is produced to show the source and new target location for each content item migrated.
We conduct the work using these steps
Source Analyis - take inventory of the content, perform a test conversion, and create the plan for the migration
Additional Transformations - if you have some unique requirements, we can define and apply additional transformation rules
Validation - Execute a mini-migration and have you validate that the content is migrated as expected. We can adjust the transformation rules if needed.
Execution - Based on the plan, stage the cutover date and execute the migration
Delta Execution - If you have a large environment, or one that cannot be frozen during the migtration testing, we can go back and migrate the 'deltas' or migrate the content in multiple waves.
Each of the Jive content types is migrated into a corresponding Connections element:
For More Infomation
Content you local IBM Software Collaboration Services representative