Data migration
For data migration, you can use tools and processes that are similar to those used in application migration and deployment.
- Extraction of business data from one system to another system. This migration is useful for populating the destination with data for testing purposes.
- Consolidation of business data into a single object store. This migration is useful for merging business data.
- Migration of a subset of an object store from one Content Cortex domain to another, or from one object store to another. This migration is useful for system rebalancing or in reaction to organizational changes.
Frequently, the same tools are used to migrate data and to migrate and deploy an application. Both processes require the general steps that are described in the planning, migrating, analyzing, backing up the system, deploying, and verifying phases. However, the specific actions within these phases can be different. For example, in the deploying phase, an application might require some additional steps after the import to make it operational in the system, but data does not usually require an actual deployment after the import. Also, for a data migration, the number of objects involved is generally greater. A more iterative migration process might be required if complex dependencies between assets are present, resulting in multiple export and import actions within a single overall migration. You can use the change impact analysis feature of FileNet® Deployment Manager to help you identify the dependencies and refine the data migration process.
For general migration steps for business data that is managed by Content Platform Engine, see the concepts and tasks in Deploying assets with FileNet Deployment Manager. For additional information about migrating business data, see Migrating data with FileNet Deployment Manager. This information includes some recommendations that can help you understand the different actions that might be required when you migrate data.