Integrations · Coming in
Bring the catalog over. Switch on a date.
Plans and add-ons become catalog products with list prices; customers become catalog customers. Contracts are then read from the PDFs, so the schedules Sonic runs come from what was signed, not from what Chargebee remembered.
Chargebee → Sonic
How it flows
Catalog and customers for a cutover. Chargebee stays the source of truth until you switch.
- 01
Plans and add-ons to products
Each plan becomes a product with a list price and billing frequency. Add-ons become their own products.
- 02
Customers to the catalog
Customers and their contacts come across with the Chargebee id kept for a second pass.
- 03
Contracts from the PDF
Schedules are built from the signed agreements, reviewed, and activated from a cutover date. Chargebee bills until then.
What it does
- A one-time or repeated import you trigger, with a preview of what will be created.
- Links an existing catalog record with the same name rather than duplicating it.
What it does not
- Run both systems live on the same customer — pick a cutover date per schedule.
- Copy Chargebee's invoice history into Sonic as issued documents.
Before the first sync
- 01Export or API key with read access to the product catalog and customers.
- 02A cutover date per customer group, so no period is billed twice.
Where it lands
Read more
Next
See it on your contracts
A walkthrough on the agreements and files you actually bill from — not a slide deck.