Playbook

Migrate from Subskribe to Kugamon: the playbook

DealHub acquired Subskribe on November 19, 2025. Subskribe still runs as its own platform for existing customers; DealHub says it will be fully integrated into the DealHub platform but has published no date, and promised ‘no immediate impact’. Kugamon keeps every quote, subscription and invoice as a Salesforce record with no separate login. The move is typically 6–10 weeks; Kugamon publishes $95 per user per month for subscription management.

Nov 19, 2025
DealHub acquires Subskribe
6–10 wks
Typical migration
0
Separate logins after
$95
Subscription Mgmt, published

Subskribe has a new owner. What now?

  • You are happy to follow DealHub’s integration planThat is the vendor’s path — see what DealHub is
  • You chose Subskribe for Salesforce and want to stay in SalesforceKugamon fits — native records, one admin surface
  • You are mid-contract and waiting to see the DealHub roadmapRun the numbers now, decide at renewal
  • HubSpot is your system of recordKugamon is not the fit — it runs only in Salesforce

Where you are

Subskribe runs outside Salesforce as a separate CPQ and billing system — reps log into another app, quote and subscription data lives off-platform, and post-DealHub-acquisition the product roadmap is uncertain. Kugamon is 100% Salesforce-native: every quote, order, contract, and subscription lives in your org, and reps quote inside Lightning.

Subskribe runs outside Salesforce as a standalone web app for CPQ and billing, with a Salesforce managed package (syncs to its own order objects; not listed on the AppExchange) and a HubSpot app. Reps leave Lightning to quote. Quotes, invoices, payments and revenue schedules stay in Subskribe. And since DealHub acquired Subskribe on November 19, 2025 (followed by DealHub’s $100M growth round led by Riverwood Capital on January 20, 2026), Subskribe still runs as its own platform for existing customers; DealHub says it will be fully integrated into the DealHub platform but has published no date, and promised ‘no immediate impact’. Subskribe’s public release notes have no entry after October 25, 2025 (checked October 2026), and the demo and contact-sales links on subskribe.com now go to DealHub. What the deal means for customers →

Kugamon is 100% Salesforce-native. Every quote, order, contract, and subscription lives in your Salesforce org — no separate login, no sync layer to drift, no external system to forecast against. The #1 rated CPQ on AppExchange, with a 15+ year track record of enterprise deployments and a typical migration of 6–10 weeks.

DealHub acquired Subskribe on November 19, 2025. kugamon.com — the acquisition, explained
Waiting on DealHub’s integration plan? Compare the Salesforce-native path on your numbers first.Open the calculator →

What you leave, what you gain

What you leave behindWhat you get with Kugamon
Runs outside Salesforce — quote, order, and subscription data lives in a separate system, not in your Salesforce org100% Salesforce-native — every quote, order, contract, and subscription lives in your Salesforce org, not beside it
Reps log into a second app to quote and transact — the context switch drives Excel reversion and breaks Lightning workflowsReps quote inside Lightning — no separate login, no app switching, no sync layer to drift
DealHub acquisition (November 19, 2025) — Subskribe still runs as its own platform, and DealHub says it will be fully integrated into the DealHub platform but has published no dateIndependent vendor with a 15+ year track record on AppExchange — #1 rated CPQ, not folded into a multi-CRM platform
Zeppa scripts and other Subskribe-specific logic don’t port directly — future portability is uncertainPricing rules, bundles, and approvals are admin-configured — no proprietary scripting language to maintain
Salesforce reports see only what Subskribe’s package syncs back (Opportunity fields and Subskribe’s own order and ARR objects); quotes, invoices, payments and revenue schedules stay in SubskribePipeline forecasts and LRR/GRR reports run on native Salesforce reports from day one — zero sync delay

Where your data lives, before and after

Where Subskribe keeps quote-to-cash records, next to Kugamon Subskribe: Quotes: outside your org (built in app.subskribe.com); Orders: on both sides, synced (in your org: Subskribe Order objects (copy); outside: master order in Subskribe); Subscriptions: outside your org (in Subskribe); Invoices: outside your org (in Subskribe); Payments: outside your org (in Subskribe); Revenue recognition: outside your org (Subskribe Revenue Recognition). 1 sync point. Kugamon: all six records in your Salesforce org, no sync. Your Salesforce orgSubskribe package objectsOutside your orgSubskribe’s app (now DealHub’s)Quotesbuilt in app.subskribe.comOrdersSubskribe Order objects (copy)Ordersmaster order in SubskribesyncSubscriptionsin SubskribeInvoicesin SubskribePaymentsin SubskribeRevenue recognitionSubskribe Revenue RecognitionKugamonevery record in your orgQuotesKugamon Quote objectOrdersKugamon Order objectSubscriptionsContract and Subscription linesInvoicesInvoice recordsPaymentsPayment records; gateway chargesRevenue recognitionRevenue records (add-on)
Subskribe: 1 on both sides · 5 outside only · 1 sync pointKugamon: 6 in your org · 0 sync pointsdashed box: outside your orgdashed line: a sync someone has to monitor
Figure 1. Where the records live: Subskribe. Quotes, subscriptions, invoices, payments and revenue schedules live in Subskribe’s own app, with a separate login. Its Salesforce package syncs accounts and opportunities in and writes order metrics, ARR and order lines back to Opportunity fields and Subskribe’s own objects; out of the box it does not use the standard Quote or Order (Subskribe). Checked October 2026.

What moves, and what gets rebuilt

Object mapping from Subskribe to Kugamon Figure 2. Object-by-object. Export every active subscription from Subskribe while the platform runs as it does today; DealHub has published no date for its integration. SubskribeKugamonProduct2 (synced)Product2 (same records)moves as-isSubskribe plans & pricingPrice Books + tiered pricingrebuildOpen quotesKugamon QuoterebuildActive subscriptionsKugamon Subscription (kuga_sub)rebuildInvoices (history)Archive; new invoices in kugo2prebuild
Moves as-is — standard Salesforce objectRebuild — package-specific, no direct equivalent
Figure 2. Object-by-object. Export every active subscription from Subskribe while the platform runs as it does today; DealHub has published no date for its integration.

The migration, step by step

  1. Subskribe Data Export

    Export product catalog, pricing logic, active subscriptions, billing schedules, and any Zeppa scripts. Document what each Zeppa script does — the logic will become Kugamon config, not code.

  2. Salesforce Reconciliation

    Since Subskribe stores data externally, reconcile Opportunities, Accounts, and Contracts in Salesforce against Subskribe records before Kugamon install — resolve any drift.

  3. Install & Configure Kugamon

    Install the single Kugamon managed package. Rebuild your Zeppa-equivalent logic as native Kugamon pricing rules, bundles, and approval flows — admin-configured, no proprietary scripting.

  4. Subscription & Billing Migration

    Migrate active subscriptions, contract end dates, billing schedules, and renewal status. Validate the next billing cycle runs cleanly on Kugamon before sunsetting Subskribe.

  5. Cutover & Subskribe Sunset

    Go live on Kugamon. Reps quote inside Lightning. Decommission the Subskribe tenant on the next renewal — no more separate login, no more sync layer.

Migration phasesFigure 3. Typical sequence and duration. The parallel-run band is the only period both systems are live.wk 0wk 1wk 2wk 3wk 4wk 5wk 6wk 7wk 8wk 9wk 10Export & reconcileCatalog & pricingQuotes + subscriptionsParallel runCut over6–10 weeks typical
Build phaseParallel run (both systems live)
Figure 3. Typical sequence and duration. The parallel-run band is the only period both systems are live.

What it costs over three years

License only, because Subskribe publishes no implementation fee. Below $10 million in annual billings, the estimate from Subskribe’s own calculator is lower than Kugamon’s published license; at $25–50 million it is higher.

Three-year licence costFigure 4. Three-year licence cost at 50 users. Kugamon Subscription Billing is published ($125 per user per month). Subskribe publishes no list prices, so its bar is an estimate, hatched: the midpoint of the 26–50-seat Quote-to-Revenue figures its own website calculator shows at under $10 million and at $25–50 million in annual billings ($56,000 and $145,000 a year). Below $10 million in billings, Subskribe’s figure is lower than Kugamon’s licence. Subskribe publishes no implementation fee, so implementation and admin are left out. Subskribe$301KKugamon Sub. Billing$225K
Solid = published priceHatched = estimate
Figure 4. Three-year licence cost at 50 users. Kugamon Subscription Billing is published ($125 per user per month). Subskribe publishes no list prices, so its bar is an estimate, hatched: the midpoint of the 26–50-seat Quote-to-Revenue figures its own website calculator shows at under $10 million and at $25–50 million in annual billings ($56,000 and $145,000 a year). Below $10 million in billings, Subskribe’s figure is lower than Kugamon’s licence. Subskribe publishes no implementation fee, so implementation and admin are left out.
Common questions

From Subskribe — FAQ

All questions →

DealHub acquired Subskribe on November 19, 2025 and says there is ‘no immediate impact’: existing Subskribe environments continue to operate, and customers keep their customer success contact. DealHub also says Subskribe will be ‘fully integrated into the DealHub platform’ with ‘a single user experience and unified data model’, and has published no date for that move. If you’re a Subskribe customer evaluating where to land, Kugamon is the Salesforce-native alternative.

Subskribe’s proprietary “Zeppa” scripting language doesn’t transfer on migration. In the Kugamon migration, Zeppa logic gets rebuilt as Kugamon configuration, with Flow where needed — no proprietary scripting to maintain.

Active subscriptions, contracts, and open quotes migrate into Kugamon’s Quote, Order and Subscription records and the standard Contract in your org. Historical order data can be preserved as read-only reference. Order-lifecycle rigidity in Subskribe (after execution only the order name and open opportunities can be edited, and an admin can revert or delete only before anything is invoiced or recognized) is replaced by Kugamon’s editable orders with full audit trail.

DealHub is multi-CRM and stores quote data outside Salesforce, syncing it back via integration. Kugamon keeps quotes and orders as records in your Salesforce org (Kugamon’s own Quote and Order objects, synced to Opportunity Products) — same login your reps already use, no sync layer, AppExchange-listed managed package. If staying Salesforce-native is your priority, Kugamon is the cleaner path.

Most Kugamon migrations complete in 4–8 weeks — against the 12–18 months a Revenue Cloud Advanced rebuild takes in practice. We've been building Salesforce-native CPQ since 2009, across 150+ companies. We know where the traps are, and we've built a proven process to avoid them. You keep your Salesforce data, your product catalog, and your pricing rules. We handle the rest.

For Salesforce CPQ customers, your data stays in Salesforce — because Kugamon is in Salesforce. There's no database migration, no export-import, no data mapping to an external system. Your product catalog, price books, quotes, and order history remain exactly where they are. For teams migrating from other platforms — including DealHub, Nue, Conga, or a custom-built CPQ — Kugamon supports data imports to bring your product catalog, pricing, and historical quote data into Kugamon. Either way, we've done it before and we'll guide you through it.

Next step

See your migration plan

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