New in Chargebee: Explore Reveal and understand your payment performance end-to-end.Try Now
Docschargebee docs
HomeBillingCPQPaymentsRevRecGrowthReveal
Support

Product Updates

  • Release Notes

Getting Started

  • Overview
  • Chargebee Billing Data Centers
  • Object Relationship Model
  • Understanding Sites
  • Chargebee Tech Glossary
  • Articles and FAQ

Implementing Chargebee

  • Implementation Guide
  • Go-live Checklist
  • Articles and FAQ

Agentic AI

  • Chargebee Copilot
  • Catalog Setup Assistant
  • MCP Servers

Developer Resources

  • Developer Resources Overview
  • API Explorer
  • Articles and FAQ

Chargebee Apps

  • Chargebee Apps CLI Developer Guide

Product Catalog

  • Product Catalog Overview
  • Coupons
  • Articles and FAQ

Subscriptions

  • Working with Subscriptions
  • Billing
  • Orders
  • Articles and FAQ

Customers

  • Managing Customers
  • Account Hierarchy
  • Email Notifications
  • Branding
  • Configure Multiple Languages
  • Articles and FAQ

Entitlements

  • Entitlements Overview
  • Features Overview
  • Feature Management
  • Managing Product Entitlements
  • Subscription Entitlements
  • Customer Entitlements
  • Grandfathering Entitlements
  • Articles and FAQ

Usage Based Billing

  • Overview
  • Use Cases
  • Setting up Usage Based Billing
  • Usage Alerts
  • Prepaid credits
  • Mid-term Subscription Changes
  • FAQs

Invoices and Credit Notes

  • Invoices
  • Credit Notes
  • Quotes [Legacy]
  • Transactions
  • Articles and FAQ

Taxes

  • Overview
  • Configuring Taxes
  • Country-specific Taxes
  • Articles and FAQ

E-Invoicing

  • Overview
  • Enabling E-Invoicing

Hosted Capabilities

  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Pricing Table
  • Mobile SDKs and Wrappers
  • Articles and FAQ

Site Configuration

  • Add Users & Assign Roles
  • Chargebee Notifications
  • Custom Fields & Metadata
  • Approvals
  • Mandatory Fields
  • File Attachments & Comments
  • Advanced Filter Options
  • Multicurrency Pricing
  • Multi-decimal Support
  • Configuring Reason Codes
  • Events and Webhooks
  • API Keys
  • OAuth Apps
  • Time Zone
  • Time Machine
  • Transfer Configurations
  • Articles and FAQ

Multi Business Entity

  • Multi Business Entity Overview
  • Customer Transfer Overview
  • Articles and FAQ

Mobile Subscriptions

  • Overview
  • Omnichannel Subscriptions
  • Omnichannel Subscriptions (Legacy)

Reports and Analytics

  • RevenueStory
  • Home Dashboard
  • Frequently Asked Questions
  • FAQs for Classic Reports Sunset
  • Articles and FAQ

Integrations

  • Sales
  • Customer Support and Success
  • Finance
  • Tax
  • E-Invoicing
  • Marketing
  • Stitch
  • Collaboration
  • Contract Management
  • Ecommerce Management
  • Articles and FAQ

Data Privacy & Security

  • Two Factor Authentication
  • SAML Single Sign-On
  • System for Cross-Domain Identity Management (SCIM)
  • EU-GDPR
  • Consent Management
  • Personal Data Management
  • Compliance Certificates
  • HIPAA Guidelines
  • PCI Recommendations and Integration Types
  • Articles and FAQ

Data Operations

  • Bulk Operations
  • Migration
  • Articles and FAQ
  1. Billing
  3. Product Catalog
  5. Articles and FAQ
  6. Migration
  1. Billing
  3. Product Catalog
  5. Articles and FAQ
  6. Migration

Is it not possible to go back to Legacy Product Catalog post migration? Can new 2.0 subscriptions can co-exist with old 1.0 ones?

Problem Statement

You want to know if you can revert to Legacy Product Catalog after migrating to PC 2.0, and whether new 2.0 subscriptions can coexist with old 1.0 ones.

Solution

The site can exist either on Legacy Product Catalog or 2.0. We do this Product Catalog update to 2.0 within the live site. Plans and Addons of Legacy Product Catalog will become items and item price points in Latest Product Catalog.

So the other entities (Subscriptions, Invoices, etc.) in the live site will be unaffected and they will be linked to the corresponding price points in Latest Product Catalog.

Yes, technically it is possible to take your site back to Legacy Product Catalog since we retain the data structures of Legacy Product Catalog and create new data structures for Latest Product Catalog during Latest Product Catalog upgrade for your live site. This fallback will be helpful if your deployed code changes don't work during the upgrade. We can switch your site back to Legacy Product Catalog while you fix your code. Once you are tested and ready again, we can go for the upgrade: you can deploy the code changes and we upgrade your site to Latest Product Catalog.

Related Articles

Will the plan ID be linked to the subscriptions in Legacy Product Catalog be changed after the site is migrated to Latest Product Catalog?
Can I move only selected plans and addons to Latest Product Catalog?
How can we test our code after the Latest Product Catalog upgrade on our Test Site?
Can we change the structure of our product catalog as a part of Latest Product Catalog migration ?
Is it possible to override quantity and price of tiered/Volume/Stairstep plan in Latest Product Catalog?
Do all plans in the 1.0 live system need to be mapped to a 2.0 item price id i.e. even archived ones?
Advantages of Latest Product Catalog
How can I check if my site is on Coexistence Mode or Latest Product Catalog?
'Error: "The API endpoint is incompatible with the product catalog version. You are calling Legacy Product Catalog API endpoint but you are using Latest Product Catalog"'

Show more

Was this article helpful?