Playbook

Migrate from Subskribe to Kugamon: the playbook

DealHub acquired Subskribe on November 19, 2025; Subskribe customers are being absorbed into DealHub’s platform, which runs outside Salesforce. 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 moving onto DealHub’s platformThat 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

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 separate CPQ and billing system. Reps leave Lightning to quote. Quote, order, and subscription data lives off-platform. 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 is being absorbed into DealHub’s multi-CRM product — the roadmap, support cadence, and pricing you signed up for are being redirected. 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
Being migrated to DealHub? 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) — roadmap, support cadence, and pricing model are all being absorbed into DealHub’s multi-CRM productIndependent vendor with a 15+ year track record on AppExchange — #1 rated CPQ, not absorbed 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
Pipeline forecasts and renewal reports run on Subskribe’s tools, not native Salesforce reports — sync lag creates blind spotsPipeline forecasts and LRR/GRR reports run on native Salesforce reports from day one — zero sync delay

Where your data lives, before and after

Your Salesforce org versus Subskribe → DealHub platform Subskribe, now part of DealHub, runs outside the Salesforce org and syncs records into it. Your Salesforce orgSynced subscription & quote recordsOpportunities & AccountsSubskribe → DealHub platformSubskribe / DealHub platform (system of record)Billing engineVendor admin consolesync
Figure 1. Before: the platform holds the authoritative subscription; Salesforce shows a copy. After Kugamon: subscriptions, contracts and renewals are native records with automated renewal opportunities.

What moves, and what gets rebuilt

Object mapping from Subskribe to Kugamon Figure 2. Object-by-object. Export every active subscription from the platform before its DealHub migration changes the export format. 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 the platform before its DealHub migration changes the export format.

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

Three-year cost comparisonFigure 4. Three-year cost at 50 users, from the ROI calculator. Kugamon licence ($65/user/month) and implementation ($10,000 for CPQ on a 3-year term) are published. Subskribe is being folded into DealHub; the DealHub row is used. DealHub does not publish pricing, so all three segments are estimates, shown hatched. DealHub$216K$75K$108K$399KKugamon$117K$143K
Solid = published priceHatched = estimate
Figure 4. Three-year cost at 50 users, from the ROI calculator. Kugamon licence ($65/user/month) and implementation ($10,000 for CPQ on a 3-year term) are published. Subskribe is being folded into DealHub; the DealHub row is used. DealHub does not publish pricing, so all three segments are estimates, shown hatched.
Common questions

From Subskribe — FAQ

All questions →

Subskribe was acquired by DealHub in November 2025. DealHub has publicly stated Subskribe will be fully folded into DealHub under a single experience and unified data model. The standalone Subskribe product’s long-term roadmap is uncertain. If you’re a Subskribe customer evaluating where to land, Kugamon is the native-Salesforce alternative.

Subskribe’s proprietary “Zeppa” scripting language doesn’t transfer on migration. In the Kugamon migration, Zeppa logic gets rewritten as standard Salesforce Apex or Flow — portable, maintainable by any Salesforce admin or developer, and no vendor-specific knowledge required to keep it running.

Active subscriptions, contracts, and open quotes migrate cleanly into native Salesforce objects (Quote, Order, Subscription, Contract). Historical order data can be preserved as read-only reference. Order-lifecycle rigidity in Subskribe (executed orders that can’t be cleanly reverted) 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 writes natively to Salesforce Quote, Order, and Opportunity Product objects — 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 outside Salesforce — including DealHub, Nue, Conga, or a custom-built CPQ — Kugamon supports data imports to bring your product catalog, pricing, and historical quote data into Salesforce. 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.