Roll Back the Migration

In addition to verifying your transactions, the Migration Transactions page also gives you the option to roll back your migrations, should you decide to do so. Rolling back a migration reverses the entire migration so that the database reverts back to the state it was in before the migration occurred. For example, if the migration included an Insert, the equivalent Delete script is stored in the rollback file. Likewise, if the migration included an Update, the equivalent Update script is stored in the rollback file. When you roll back the data, the Delete and Update scripts will be run to restore the old values.

Upon analyzing the Migrated Data File details below, two data differences were found in the WB_ARCH_POLICY table:

  • In the Interactions record, the value of the WBAP_ENABLED field was Y in the source database while the value of the WBAP_ENABLED field was N in the destination database.
  • In the Temporary Teams record, the value of the WBAP_ENABLED field was Y in the source database while the value of the WBAP_ENABLED field was N in the destination database.

Due to these data differences, a migration occurred, where updates (U) were made to the Interactions and Temporary Teams records to change the N (Old) values in the destination database to the Y (New) values to match the source database.

WB_ARCH_POLICY

U, INTERACTIONS

Field Old Value New Value
WBAP_ENABLED N Y

U, TEMPORARY TEAMS

Field Old Value New Value
WBAP_ENABLED N Y

If the above transaction was rolled back, the contents of the Rollback File for the same WB_ARCH_POLICY Migrated Data File would be:

WB_ARCH_POLICY

U, INTERACTIONS

Field Old Value New Value
WBAP_ENABLED Y N

U, TEMPORARY TEAMS

Field Old Value New Value
WBAP_ENABLED Y N

Rollbacks, if required, should be performed immediately after the migration. Common reasons for rolling back data:

  • You migrated the wrong tables or functional objects.
  • You forgot to apply a filter or exclude certain records or fields before you migrated the data.

Again, like migration transactions, when a rollback is successful, two Migration History records will be created:

  • Rollback Initiated record
  • Rollback Completed record
Note:  If transactional data is associated to the newly-migrated data, performing a rollback will not revert the database back to its original state. In other words, if you try to roll back migrated data that someone has already modified (i.e., via a transaction), the Migration Tool may fail the rollback. For example, if you migrate data to a production instance, and then a user modifies the data in the production instance, you will not be able to roll the data back.

If you need to roll back multiple migrations, you can roll back one file at a time in the reverse order of that in which they were created.

For steps on how to roll back migrations, see Roll back the Migration.