Backing up the database during the migration process

One of the key advantages of the parallel upgrade methodology is that, if an unrecoverable failure occurs during the cutover process, the original production system is not affected. Rolling back simply involves resetting the routing of users and integrations back to the original state.

This holds true for consolidations. The original production system is a safe fallback position and provides a safe and quick rollback method for the set of customers being merged into the target system.

However, consolidations differ from standard parallel upgrade scenarios in that the target system is typically an in-use production system that is affected by the transfer of data from the source production system. To guarantee that the target system can be rolled back in the event of a failure during cutover, take the target Production system offline during the migration process and create a full database backup prior to migrating data into the system. In the event that a rollback is required, you can restore the backup and put the system back online with minimal impact to existing users.

The Cutover-methodology provides the fastest and safest rollback method for any of the consolidation cutover methodologies.