Welcome to Zuora Product Documentation

Explore our rich library of product information

Run Quote Charge Data Migration Job

This task guides you through running the ZuoraQuotesUpgradeConversion6_51 job to migrate New Subscription quote data for backward compatibility with the deprecated Quote Charge object.

Note: You only need to run this migration job if you need to maintain a backward compatibility with the deprecated Quote Charge object.

Due to the Quote object refactoring, the New Subscription quotes that were saved in previous versions of Zuora Quotes will not be accessible in this version. The ZuoraQuotesUpgradeConversion6_51 job migrates the New Subscription quote data from the Quote Charge object to the Quote Rate Plan Charge object. You must run the script as a System Administrator.

Note: This migration script will temporarily disable the Store Data in Quote Charge configuration setting while the script is running. You should not enable this setting while the migration script is running.
  1. Disable any custom triggers or validations in your org.
  2. Open Developer Console.
  3. Navigate to Debug > Open Execute Anonymous Window.
  4. Enter the following Apex code in the Enter Apex Code window: zqu.ZuoraQuotesUpgradeConversion6_51 zuc = new zqu.ZuoraQuotesUpgradeConversion6_51(); ID batchprocessid = Database.executeBatch(zuc);
  5. Click Execute.
  6. Navigate to Setup > Administration Setup > Monitoring > Apex Jobs and verify that the above job is running.
  7. Disabled customer triggers or validations can now be re-enabled.
    Note: If all of the following conditions apply to a quote, the quote will not be migrated by the script:
    • A product, a rate plan, or a rate plan charge was removed from the Product Catalog in Zuora.

    • The Product Catalog was rebuilt in Zuora CPQ by a Sync Cleanup followed by a fresh Product Catalog Sync from Zuora.

    • The Quote and Quote Charges include the product, the rate plan, or the charge removed in Step #1

    Note:

    If your current version is 6.50, 6.60, or 7.1.x, you must manually run the migration script in the following scenario:

    • You have not run the migration script introduced in Version 6.51.
    • Your migration script failed with an error.