Get the next conversation in your inbox

One signal-dense note when a new episode lands. No noise.

Join the list
Media

Unboxing Revenue Hub - Contracts & Billing

Guests: Joe Warren, Ryan Ginsberg

August 4, 2026

HubSpot product manager Joe Warren walks through the billing-migration tooling he owns: how a migration onto Revenue Hub contracts actually runs, and what separates a technically clean import from one a team can live with. Ryan Ginsberg brings the practitioner view.

Moments from this episode

Key takeaways

A technically successful migration is not a successful one. Joe's four checks before anything moves: portal readiness, team training, the CRM and product model, and whether your accounting or ERP sync survives the change. Cutover orchestration is the fifth, and it is the one people start with.

Two questions set the difficulty. Are you migrating contracts that send invoices customers pay, or contracts that charge payment methods automatically? The second carries a payment-token migration. And do you need legacy revenue-change history inside HubSpot's waterfall reports? If not, the import gets simpler.

Imported contracts land in a draft state. An import cannot start billing anyone on its own — you review, then activate deliberately. That step tested well enough that HubSpot is extending it to every contract import, billable or not.

The line item is the atomic object. The contract is the container; billing is driven by the line items inside it. That makes product-library decisions the real prerequisite, not an afterthought.

Success shows up early, and it is qualitative. Not contracts moved, not weeks elapsed — whether the team is trained and bought in, and whether finance sees no disruption downstream.

Give yourself a day of runway. The billing override start date tells HubSpot when it may begin billing. Setting it a day or two ahead of the first line-item date buys coordination room with the system you are leaving.

The guests

Joe Warren
Joe Warren
Product, HubSpot

HubSpot product team member specializing in Commerce Hub and billing/payments integrations.

Ryan Ginsberg
Ryan Ginsberg
Technical Lead & HubSpot Implementation Engineer

Keep learning

You just watched the work. Now build it.

The next step is doing it yourself — live, with people on the same path.

Get the next conversation in your inbox

One signal-dense note when a new episode lands. No noise.

Join the list