In addition to continuous content updates, many organizations plan to restructure their website, or introduce new websites or new sections and to have these changes go live with the migrated system. During migration planning and execution, it is important to understand how to manage structural change at the same time as keeping regular content updates synchronized.
Options for keeping data synchronized during migration
Post migration data update
A post migration data update is used to refresh web content after a full migration is complete. A post migration data update migrates only the JCR domain, including all web content. The post migration data update overwrites any web content changes on the migrated system. When there are many changes to the migrated content, a different strategy should be considered.Dual maintenance
Dual maintenance is used when the number of expected changes are low. Authors are required to update both the old system, and the new system, until the migration is complete. The key benefit of this approach is the ability to preserve all content updates on both systems. Dual maintenance is often required in the final stage of migration when other techniques are no-longer possible because they would overwrite changes on the new system.Web content library export and import
A Web content library export and import can be used during migration. However, there are important limitations which preclude the usage of these tools in most migrations. A Web content library export and import can be used when updates are isolated to a small library on the source system. Export and import should only be used where simple modifications or additions are happening in the source system. A Web content library import must not be used to update content which has changed since the last import.
Other useful techniques for managing change
Isolate changes on the old system from changes on the new system
Changes on the old system that are not required on the new system can be isolated to a library that is not used by the new system. Changes to items in libraries that are used by both the old and new system should be kept to a minimum. Any shared changes should be maintained by using a dual maintenance strategy.Keep a record of changes
If there are only a few changes to be made on the migrated system, you can keep a record of every change made on the migrated system. When a post migration data-update is run, you must then reapply the changes on the migrated system that is based on the record of changes.Only make updates the old system during migration
Syndication, data update, and library import will overwrite modifications made on the new system. Where possible make required changes in the old system so they will be preserved by the synchronization process.Parent topic: Migrating from Web Content Manager version 6.1