Playbook

Migrate from Zuora to Kugamon: the playbook

Zuora runs billing on its own platform and connects to Salesforce through Zuora CPQ (the Zuora Quotes managed package) and Zuora 360 / the Zuora Connector for Salesforce CRM. Kugamon keeps every Quote, Subscription, Invoice and Payment as a record in your Salesforce org. The move typically runs 6–10 weeks; Kugamon publishes $125 per user per month for Subscription Billing, and Zuora has no price list on zuora.com (its AWS Marketplace listing shows packages from $75,000 per unit per year, unit not defined).

6–10 wks
Typical migration
0
Sync layers after
$125
Subscription Billing, published
Feb 14, 2025
Silver Lake and GIC complete Zuora acquisition

Leave Zuora, or stay?

  • You rate usage at high volume, need ASC 606 revenue recognition as a finance-owned subledger, or bill from many legal entitiesStay on Zuora — it is built for that depth. See Kugamon vs Zuora
  • Salesforce is your system of record and your billing is recurring invoices, proration, payments and renewalsKugamon fits — one catalog, one data model, nothing to sync
  • You are mid-contract with ZuoraRun the inventory and the numbers now; time the cutover to a quarter boundary before your renewal

Where you are

Zuora runs billing on its own platform, between your CRM and your general ledger. Salesforce sees it through Zuora CPQ (the Zuora Quotes managed package) and Zuora 360 / the Zuora Connector for Salesforce CRM, so the catalog, the subscriptions and the invoices live in Zuora and Salesforce holds a copy. Kugamon runs the same lifecycle inside your org: Quotes, Subscriptions, Invoices and Payments are Salesforce records on one data model.

Zuora is a billing-first quote-to-cash platform outside Salesforce. Its catalog of products, rate plans and charges is maintained in Zuora and synced in through the Zuora CPQ managed package, whose Quote is a custom object linked to the Opportunity. Subscriptions, invoices and payments run in Zuora Billing, and the Zuora 360 / Connector sync copies accounts, subscriptions, invoices and payments into Salesforce on a batched schedule (Zuora documentation). Zuora’s documentation says its ‘real-time’ sync to Salesforce runs after 10 change events or 120 minutes by default, whichever comes first; it is configurable, and lower values use more Salesforce API calls. A full sync can take up to a few hours (real-time sync). That is a coherent design for a large finance organization. For a Salesforce-centric team it means two catalogs to keep aligned, a sync that has to be right for a report to be right, and a renewal book that lives in a billing system instead of the pipeline. The full Zuora migration guide →

Kugamon is 100% Salesforce-native. Releasing an Order creates the Contract, Subscriptions, Invoices and the future Renewal Opportunity as Salesforce records related to the same Account, so the catalog sales quotes from is the catalog billing invoices from. Kugamon is #1 on the Salesforce AppExchange for Subscription Management and Subscription Billing, and a typical move from Zuora runs 6–10 weeks.

Silver Lake, with GIC, completed its acquisition of Zuora on February 14, 2025; Zuora is now privately held. zuora.com
Quoting in Salesforce and billing in Zuora? Price the one-system path on your own numbers first.Open the calculator →

What you leave, what you gain

What you leave behindWhat you get with Kugamon
A catalog of products, rate plans and charges maintained in Zuora and synced into SalesforceOne catalog: standard Products and Price Book Entries, used by quoting and billing alike
Subscriptions, invoices and payments in Zuora Billing; Salesforce holds a synced copy through the Zuora 360 / Connector syncSubscriptions, Invoices and Payments are records in your Salesforce org, related to the same Account
Billing metrics such as MRR, TCV and unbilled revenue in Zuora’s own dashboardsARR, MRR and TCV roll up on the Contract and report with the standard Salesforce report builder
Renewals tracked in the billing system, beside the pipelineRenewal Opportunities created on Order Release, with price uplifts applied by rule — renewals are pipeline
Zuora administrators, with Zuora University training and Extension Studio for custom logic; Zuora recommends upgrading the Zuora Quotes package at least once a quarterYour Salesforce admin, point-and-click: invoice schedules, payment terms and renewal uplifts are settings; dunning is built in Flow
No price list on zuora.com; its AWS Marketplace listing shows Billing + CPQ + Revenue packages from $75,000 per unit per year (unit not defined), not priced per userPublished pricing: $125 per user per month for Subscription Billing, with a fixed implementation fee

What you give up is depth some teams need. Zuora Billing has built-in mediation and rating for usage at very high volume, Zuora Revenue automates ASC 606 and IFRS 15 as a finance-owned subledger, and Zuora handles multi-entity, global finance (zuora.com). Kugamon supports usage billing with minimal customization, and its Revenue Management add-on creates monthly Revenue records for reporting; it is not a revenue subledger. If those capabilities are central to how your finance team works, stay on Zuora. Kugamon vs Zuora, row by row →

Where your data lives, before and after

Zuora is the system of record for the catalog, the subscriptions and the invoices; Salesforce holds what the sync copies in.

Where Zuora keeps quote-to-cash records, next to Kugamon Zuora: Quotes: on both sides, synced (in your org: Zuora Quotes package objects; outside: sent to Zuora in one click); Orders: outside your org (Zuora Orders and amendments); Subscriptions: on both sides, synced (in your org: copy via Zuora 360; outside: master in Zuora); Invoices: on both sides, synced (in your org: copy via Zuora 360; outside: master in Zuora); Payments: on both sides, synced (in your org: copy via Zuora 360; outside: Zuora Payments and gateways); Revenue recognition: outside your org (Zuora Revenue subledger). 4 sync points. Kugamon: all six records in your Salesforce org, no sync. Your Salesforce orgZuora Quotes package and synced copiesOutside your orgZuora’s platformQuotesZuora Quotes package objectsQuotessent to Zuora in one clicksendOrdersZuora Orders and amendmentsSubscriptionscopy via Zuora 360Subscriptionsmaster in ZuorasyncInvoicescopy via Zuora 360Invoicesmaster in ZuorasyncPaymentscopy via Zuora 360PaymentsZuora Payments and gatewayssyncRevenue recognitionZuora Revenue subledgerKugamonevery record in your orgQuotesKugamon Quote objectOrdersKugamon Order objectSubscriptionsContract and Subscription linesInvoicesInvoice recordsPaymentsPayment records; gateway chargesRevenue recognitionRevenue records (add-on)
Zuora: 4 on both sides · 2 outside only · 4 sync pointsKugamon: 6 in your org · 0 sync pointsdashed box: outside your orgdashed line: a sync someone has to monitor
Figure 1. Where the records live: Zuora. Quotes are built in the Zuora Quotes package’s own objects and sent to Zuora, which creates the subscription (Zuora). Zuora 360 copies subscriptions, invoices and payments back into Salesforce; its “real-time” sync runs after 10 change events or 120 minutes by default, whichever comes first (Zuora). Checked October 2026.

What moves, and what gets rebuilt

Migrate active subscriptions, not invoice history. Keep Zuora read-only, or export invoices to an archive, so the history stays queryable without being re-created.

Object mapping from Zuora to Kugamon Figure 2. Object-by-object from Zuora to Kugamon. Stored payment profiles move through your payment gateway’s supported process, not by copying card data. ZuoraKugamonAccount, Contact, OpportunitySame Salesforce recordsmoves as-isProducts, rate plans, chargesProduct2 + Price Book EntriesrebuildOpen Zuora quotesKugamon Quote (kugo2p)rebuildActive subscriptionsKugamon Subscription (kuga_sub)rebuildInvoices (history)Archive; new invoices in kugo2prebuildStored payment methodsPayment Method, via the gatewayrebuild
Moves as-is — standard Salesforce objectRebuild — package-specific, no direct equivalent
Figure 2. Object-by-object from Zuora to Kugamon. Stored payment profiles move through your payment gateway’s supported process, not by copying card data.

The migration, step by step

  1. Inventory the billing you actually use (week 0)

    List billing frequencies, proration rules, payment methods, dunning steps and revenue schedules, and mark what ran in the last 90 days. Flag anything that needs usage rating at volume, ASC 606 allocation or multi-entity invoicing: that is where Zuora is strongest.

  2. Map subscriptions, not invoices (weeks 1–2)

    The unit of migration is the active subscription: customer, products, quantities, rates, term dates, renewal terms and payment method. Invoice history stays in Zuora, read-only or as an archived export.

  3. Rebuild the catalog natively (weeks 1–3)

    Zuora’s product, rate-plan and charge hierarchy flattens into Salesforce Products and Price Book Entries, with Tiered Pricing where you need it. Retire the rate plans nobody sells any more.

  4. Load active subscriptions and bill in parallel (weeks 3–6)

    Import the active subscriptions, then run one or two billing cycles in both systems and compare the invoices line by line before any customer sees the new output.

  5. Cut over payments and dunning (weeks 5–8)

    Re-point the payment gateway (Kugamon connects natively to Stripe, Authorize.Net, PayPal and eWay), move stored payment profiles through your processor’s supported process, and switch dunning communications last. Time the cutover to a quarter boundary so revenue reporting has a clean seam.

Migration phasesFigure 3. Typical sequence. The parallel-billing band is the only period both systems are live; most teams finish in 6–10 weeks.wk 0wk 1wk 2wk 3wk 4wk 5wk 6wk 7wk 8InventoryMap subscriptionsRebuild catalogLoad subscriptionsParallel billingPayments & dunning cutover8 weeks shown · 6–10 weeks typical
Build phaseParallel run (both systems live)
Figure 3. Typical sequence. The parallel-billing band is the only period both systems are live; most teams finish in 6–10 weeks.

What it costs

Kugamon publishes per-user prices; Zuora has no price list on zuora.com. The honest comparison is your Zuora renewal quote against Kugamon’s published numbers, plus what the second system costs you to run.

LineKugamonZuora
LicenseSubscription Billing (CPQ + Billing + Subscription Management): $125 per user per month, published on the AppExchange listingNo price list on zuora.com; its AWS Marketplace listing shows Billing + CPQ + Revenue packages at $75,000 (Launch), $175,000 (Scale) and $250,000 (Enterprise) per unit per 12 months, and does not define the unit. It is not priced per user.
ImplementationFixed fee: $30K for Subscription Billing, $5K less on a 2- or 3-year termZuora says its Milo implementation agent (July 2026) lets companies ‘go live in weeks with up to 80% fewer resources’ (the 80% is footnoted ‘based on early customer testing’). The same release says billing and revenue implementations often take more than six months. Delivered by Zuora Global Services and SI partners (zuora.com).
Connection to SalesforceNone needed: the billing system is the CRMZuora CPQ package plus the Zuora 360 / Connector sync to keep in step
Who runs itYour Salesforce adminZuora administrators
Three-year cost comparisonFigure 4. Three-year cost at 50 users. Kugamon Subscription Billing’s licence ($125 per user per month) and implementation ($25,000 on a three-year term) are published; its admin is our estimate. Every Zuora segment is an estimate, hatched: the licence averages one Launch package ($75,000 a year) and one Scale package ($175,000 a year, with a typical renewal uplift) from Zuora’s AWS Marketplace listing, which does not define its unit; implementation and premium support are the midpoint of our low and high cases. Zuora is not priced per user, so it is not in the per-user ROI calculator. Zuora$394K$81K$64K$538KKugamon Sub. Billing$225K$266K
Solid = published priceHatched = estimate
Figure 4. Three-year cost at 50 users. Kugamon Subscription Billing’s licence ($125 per user per month) and implementation ($25,000 on a three-year term) are published; its admin is our estimate. Every Zuora segment is an estimate, hatched: the licence averages one Launch package ($75,000 a year) and one Scale package ($175,000 a year, with a typical renewal uplift) from Zuora’s AWS Marketplace listing, which does not define its unit; implementation and premium support are the midpoint of our low and high cases. Zuora is not priced per user, so it is not in the per-user ROI calculator.

At 50 users on a three-year term, Kugamon Subscription Billing is $225,000 in license plus a $25,000 implementation fee: $250,000 over three years, every figure published. Figure 4 adds our admin estimate and sets it beside an estimate for Zuora built from Zuora’s own AWS Marketplace package prices: about $538,000 over three years against about $266,500 for Kugamon, roughly half. Put your Zuora renewal quote and the cost of keeping the sync running beside it, or set your own user count for Kugamon in the ROI calculator. Zuora has no price list on zuora.com (zuora.com), and its AWS Marketplace packages are priced per undefined unit, not per user, so any per-user number you use for Zuora is your own quote or an estimate. On Zuora’s direct editions, Zuora CPQ and Collections are purchased separately; editions include 2, 5 or 10 payment gateways and cap active subscribers at 25,000 / 500,000 / 2,000,000; phone support and SLAs start at the Enterprise edition (Zuora editions).

Common questions

From Zuora — FAQ

All questions →

For mid-market teams moving to Salesforce-native billing, 6–10 weeks is a realistic range: a week-zero inventory, the catalog rebuilt on the standard Price Book, active subscriptions loaded, one or two billing cycles run in parallel and compared line by line, then payments and dunning cut over last.

Usually no. Keep Zuora read-only, or export invoices to an archive, and migrate only active subscriptions and their forward-looking billing schedules. You need the history queryable, not re-created.

Payment profiles move through your payment gateway’s supported process, not by copying card data. Kugamon connects natively to Stripe, Authorize.Net, PayPal and eWay, and processes ACH through the Authorize.Net and Stripe connections.

Kugamon supports usage billing with minimal customization, and its Revenue Management add-on creates monthly Revenue records for reporting. It has no built-in mediation or rating engine at Zuora’s scale and is not an ASC 606 revenue subledger. If high-volume rating or Zuora Revenue is central to your finance process, Zuora is the better fit.

Subscription Billing: CPQ, Billing and Subscription Management in one managed package, at $125 per user per month with a fixed $30K implementation fee, $5K less on a 2- or 3-year term. Quotes, Orders, Contracts, Subscriptions, Invoices, Payments and renewals all run on records in your Salesforce org.

You switch them off at cutover. Quoting moves to Kugamon’s Quote and Order in Salesforce, and because billing runs on the same records there is nothing to sync. Open Zuora quotes are re-created as Kugamon Quotes before the cutover.

Next step

See your migration plan

Published timelines by source platform, a fixed implementation fee, and a calculator that labels every estimate.