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

Docschargebeedocs

HomeBillingPaymentsRevRecGrowthReveal
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

AI in Chargebee

  • Chargebee Agents
  • Chargebee Copilot
  • Chargebee MCP Server (Model Context Protocol)

Developer Resources

  • Developer Resources Overview
  • Articles and FAQ

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

  • Understanding Usages
  • Setting up Usage Based Billing
  • Usage Alerts
  • Metered Billing
  • Articles and FAQ

Chargebee CPQ

  • Chargebee CPQ
  • Chargebee CPQ for Salesforce
  • Chargebee CPQ for HubSpot

Invoices, Credit Notes, and Quotes

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

Taxes

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

Hosted Capabilities

  • Overview
  • Hosted Checkout
  • Hosted Self-Serve Portal
  • Hosted Pages Features
  • Additional Hosted Pages
  • Payment Components
  • Pricing Table
  • Managing Payments with Chargebee.js
  • Mobile-Optimized Hosted Pages
  • Articles and FAQ

Site Configuration

  • Users & Roles
  • 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
  • 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 One-Time Orders
  • Mobile 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
  • 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

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?

Problem Statement

You want to know whether all plans in the 1.0 live system (including archived ones) need to be mapped to a 2.0 item price ID during migration.

Solution

There might be subscriptions and invoices records linked to the plans and addons. So it is necessary to move all the plans and addons to Latest Product Catalog, including the archived ones.

However, if there are no subscriptions attached to the plans and addons that you do not want to move to Latest Product Catalog, you can delete them right away in Legacy Product Catalog.

To handle archived plans in Latest Product Catalog

Going forward, you could make use of grandfathering feature of Plans which is explained here, since you are creating new Plans only to introduce price change. This is supported in Legacy Product Catalog as well

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?
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?