Rollback Product Catalog Version Upgrade
Overview
Businesses that upgrade their Chargebee Product Catalog version from 1.0 to 2.0 can initiate a rollback request post upgrade. A successful rollback ensures that the Chargebee test and live sites are reverted back to product catalog version 1.0.
Step-by-step rollback process
The following are the steps to perform product catalog version upgrade rollback process:
- Initiate a rollback request with the Customer Success Manager, Professional Services Consultant, or Chargebee support stating the reasons for the rollback.
- Chargebee will validate if the test or live site adheres to the limitations mentioned below. If there are any discrepancies, you will be notified. Please note that the below caveats are important to ensure a successful rollback is possible without complexities.
- Chargebee will run an internal API to perform the rollback to product catalog version 1.0. If plan and addon ID updates were performed as part of the upgrade process, you can choose to retain them or revert them to their original format.
- The rollback process will take approximately one to one and half hour(s) depending on the volume of data.
Limitations
To ensure that a successful rollback can be performed, follow the limitations:
- New plans, addons, or charges should not be created on the product catalog version 2.0 site post upgrade.
- Updates in naming convention, price, billing cycle, attached items and more should not be made to the existing plans, addons, and charges post upgrade.
- All operations that are halted/paused on the Chargebee site during the upgrade should continue to be paused until the rollback process is completed. New customers, subscriptions, quotes, invoices, and transactions should not be generated on the site post upgrade. Only existing subscription renewals and subscription activations (future/trial subscriptions) scheduled to run by Chargebee automatically within the same time window as the upgrade and rollback can continue.
- Product catalog version 2.0 specific features should not be enabled and used post upgrade.
Related Articles
Articles & FAQ