Migrate Active Contracts and Subscriptions to Revenue Hub

What This Update Actually Is

HubSpot shipped a public beta called Billing Migrations onto Revenue Hub Contracts. It does one specific thing: it gives merchants a controlled, reviewable path to move active billing relationships into Revenue Hub Contracts.

Those billing relationships can come from two places. First, a legacy billing system outside HubSpot entirely. Second, existing Commerce Hub subscriptions running through HubSpot Payments or Stripe.

The migration preserves the original effective date and line-item start dates. You pick a future date when Revenue Hub takes over billing. Imported contracts land as drafts first, so nothing activates until your team reviews and explicitly approves each one.

One important boundary: historical invoices and payments are not recreated. If you need those reflected in HubSpot, the Invoices API is the path after migration.

Why HubSpot Shipped This

Moving recurring billing between systems is one of the riskiest things a finance or RevOps team can do. The gaps are not hypothetical. Billing stops in the old system before the new one is ready. Customers get charged twice. Revenue reports show phantom MRR because the data lives in two places at once.

We've seen this pattern repeatedly across portals: a company moves to HubSpot Commerce or Revenue Hub for net-new deals, but their existing subscriptions keep running in Stripe, Chargebee, or a spreadsheet. The result is a split source of truth that quietly breaks MRR reporting and makes renewal conversations harder than they need to be.

Billing Migrations closes that gap. It gives finance teams a structured handoff: draft review, validation, a chosen start date for Revenue Hub billing, and an explicit activation step. Nothing changes until you say it changes.

How to Use It Step by Step

1. Enroll in the beta. A Super Admin opens Product Updates inside the HubSpot account and opts into the Billing Migrations onto Revenue Hub Contracts public beta.
2. Choose your migration format. Decide between manual payments (invoices sent to buyers) and automatic payments (charged to a payment method on file). Then decide whether you want revenue continuity. Revenue continuity uses ramp keys to group line-item phases so HubSpot can display historical expansions and contractions in the MRR waterfall. Without it, contracts import cleanly but without that change history.
3. Gather your payment method IDs. If you use Stripe, pull the IDs directly from your Stripe dashboard. If you use HubSpot Payments and want to migrate from an external Stripe account, fill out HubSpot's Payment Operations data request form. HubSpot's team will send the IDs securely.
4. Build your CSV. Include contracts or subscriptions, billing contacts, line items, original effective and line-item start dates, collection method, and the future date when Revenue Hub should begin billing. If using revenue continuity, add ramp keys to group phases. Use the same ramp key string for all phases of a single recurring stream, and leave the field blank for flat products that don't change.
5. Test in a sandbox first. If you're using revenue continuity, run the import in a sandbox environment before touching production. Incorrect historical data in the MRR waterfall can only be fixed by deleting the contract and reimporting it. There's no in-place correction.
6. Import via Advanced Imports. Navigate to Revenue, then Contracts, and use Advanced Imports to upload the CSV. Contracts arrive as drafts.
7. Review drafts and resolve validation errors. Check billing schedules, confirm the first Revenue Hub billing date, and fix any issues before activating.
8. Explicitly migrate the drafts. Once you're satisfied, activate the contracts. Revenue Hub takes responsibility for future billing. Coordinate the exact moment billing stops in the legacy system to prevent overlap. This step is permanent: once a contract is activated, HubSpot is the system of record and the migration can't be undone.

What It Touches in Your HubSpot Strategy

This update has a wider footprint than it appears at first glance. Here's where it ripples.

Revenue reporting and MRR waterfall. When you include revenue continuity and structure ramp keys correctly, historical upgrades, expansions, downgrades, and contractions appear alongside future HubSpot billing in the MRR waterfall. That means finance gets a single, unbroken recurring revenue story instead of a pre-migration gap followed by a post-migration cliff.

Commerce Hub subscriptions. If your team built recurring billing on Commerce Hub using HubSpot Payments or Stripe, those subscriptions are migratable. This is the upgrade path HubSpot is offering as Revenue Hub becomes the primary contracts engine.

Contracts Direct Create/Edit beta. There's a second beta woven into this release that matters. Enrolling in Contracts Direct Create/Edit removes the Revenue Hub seat requirement entirely. Your team can create, edit, and use Revenue Hub Contracts for billing without assigning Revenue Hub seats or generating Revenue Hub quotes first. For companies that want the billing infrastructure without rolling out full Revenue Hub seat licenses, this is a significant unlock.

Permissions. The import requires both Import permissions and Edit permissions for contracts. Audit your team's role assignments before the migration day so you're not blocked at the last step.

Breeze and AI reporting. Once Revenue Hub Contracts become your billing source of truth, Breeze can read that contract revenue data for plain-language queries about TCV, MRR, and committed revenue. If you haven't looked at how Breeze now surfaces Revenue Hub contract data, that's the next logical read after this one.

If your team is still getting oriented on what Revenue Hub actually includes and how it fits into your stack, the complete Revenue Hub launch guide gives you the full picture before you commit to a migration.

Who Should Care Most

This update is most immediately relevant to a specific set of humans inside specific types of companies.

• RevOps leads managing a split billing stack who need one place where recurring revenue lives, audited and reportable.
• Finance teams at SaaS or subscription companies who need accurate MRR waterfall data and can't afford gaps when switching billing systems.
• HubSpot admins at companies currently running Commerce Hub subscriptions who've been told to consolidate onto Revenue Hub Contracts.
• Companies on Revenue Hub Professional or Enterprise, or those enrolled in the Contracts Direct Create/Edit beta, who want to start net-new Revenue Hub billing without abandoning existing contract history.
• Businesses using Stripe who want to migrate payment methods into Revenue Hub without involving HubSpot's Payment Operations team.

If your company runs on manual invoicing with no recurring payment methods, you can still migrate but the process is simpler: no payment method IDs required, and the collection method in your CSV reflects manual.

George's Take

This is the update I've been waiting for since Revenue Hub launched. The biggest barrier to adoption wasn't features or pricing. It was the migration problem. Telling a company with 200 active subscriptions to "just switch to Revenue Hub" was a non-starter, because there was no safe, auditable path to move what already existed. Billing Migrations changes that. The draft-first, explicit-activation design is exactly the right approach: it gives finance teams control over the most critical moment in the transition, which is when billing responsibility actually transfers. My strong advice is to run this in a sandbox with real data before you touch production, especially if you're using revenue continuity ramps. The MRR waterfall doesn't forgive import errors quietly.

If you're a Revenue Hub Professional or Enterprise customer and you want hands-on help planning your migration, including CSV structure, sandbox testing, and legacy system cutoff coordination, we'd love to walk through it with you. The humans on our team have worked through enough portal migrations to know exactly where things go sideways. Read up on Revenue Hub first, then book a strategy call with Sidekick and let's build your migration plan together.

Frequently Asked Questions

What is HubSpot's Billing Migrations feature?

Billing Migrations is a HubSpot public beta that lets merchants import active contracts from a legacy billing system or Commerce Hub subscriptions into Revenue Hub Contracts. The migration preserves original dates and payment methods, creates contracts as drafts for review, and lets you choose a future date when Revenue Hub takes over billing.

Will my customers be charged twice during a contract migration to Revenue Hub?

Not if you coordinate correctly. HubSpot does not stop billing in your legacy system automatically. You must manually coordinate when to stop legacy billing before Revenue Hub begins charging. The draft review step is specifically designed to let you confirm the first Revenue Hub billing date before anything activates.

Do I need a Revenue Hub seat to use Billing Migrations?

You need Revenue Hub Professional or Enterprise, or you must enroll in the Contracts Direct Create/Edit private beta. The Contracts Direct Create/Edit beta removes the individual seat requirement, letting your team create and manage Revenue Hub Contracts for billing without assigning Revenue Hub seats to each user.

How do I get payment method IDs for automatic payment migrations?

If you use Stripe, pull payment method IDs directly from your Stripe dashboard. If you use HubSpot Payments and are migrating from an external Stripe account, submit HubSpot's Payment Operations data request form. HubSpot's team will securely provide the required IDs.

What is revenue continuity in HubSpot contract migrations?

Revenue continuity lets you include historical contract change events, such as expansions, contractions, upgrades, and downgrades, alongside future billing in the MRR waterfall. It uses ramp keys to group line-item phases. It does not recreate historical invoices or payments, only the revenue events for reporting purposes.

Can a contract migration to Revenue Hub be undone?

No. Once a contract is activated, HubSpot becomes the permanent system of record for that contract and the migration can't be reversed. Any future contract updates must be made in HubSpot. This is why HubSpot imports contracts as drafts first, so you can review and validate everything before committing.