Not as a general-purpose, native import. HubSpot's own documentation states that contract imports and subscription-to-contract migrations are not currently supported out of the box.

This is the single biggest gap companies hit when adopting Revenue Hub with an existing book of business — and it's exactly the gap SyncMatters closes, by mapping legacy contract and subscription data into properly structured, fully associated Contract records rather than leaving them as orphaned data outside HubSpot.

Yes. It requires translating Salesforce CPQ's quote, price book, and approval-workflow structures onto Revenue Hub's CPQ and Contract object model rather than a direct field-for-field copy, since the two platforms handle approval logic, discounting, and quote-to-contract conversion differently. SyncMatters handles this translation as a core part of Revenue Hub migration engagements, preserving approval history and pricing logic in the process.

HubSpot provides a migration tool for legacy quote templates, but it migrates structure, not your full historical quote data — and accepted legacy quotes do not automatically create Contract records in the new system. Anything you want represented as a structured Contract needs its own migration path, which SyncMatters builds and runs as part of a Revenue Hub rollout.

In most cases, yes. Revenue Hub is designed to sync with ERPs and accounting platforms — NetSuite, Microsoft Dynamics, SAP, QuickBooks, Xero — rather than replace them. It gives sales, finance, and customer success a shared, CRM-native view of revenue data that stays connected to your financial system of record. SyncMatters builds and maintains that connection so both systems stay accurate rather than drifting apart.

It depends on the number of source systems, the volume of historical contract and subscription data, and how much de-duplication and reconciliation is required. Phasing by object type — quotes first, then contracts, then subscriptions and billing — produces a far more predictable timeline than a single big-bang cutover, and it's the sequencing SyncMatters uses on every migration.

Revenue Hub offers native QuickBooks and Xero sync for ongoing invoice and payment data. That sync keeps things current going forward — it is not designed to backfill years of historical billing and invoice history accurately. SyncMatters runs the historical migration separately from the live sync setup, so the two don't collide and create duplicate or conflicting records.

A sync (to NetSuite, QuickBooks, Xero, Stripe, etc.) moves data going forward. A migration backfills your existing historical quotes, contracts, subscriptions, and billing records into HubSpot's object model, with de-duplication and reconciliation against your source system. Most companies need both, in that order — sync alone leaves years of contract and revenue history missing from Revenue Hub, which is precisely where SyncMatters' migration work comes in.

Yes, though HubSpot's native tooling is built for current and future invoicing and payments rather than backfilling historical records with full accuracy. SyncMatters migrates historical invoice and payment data alongside contracts and subscriptions, and reconciles totals against your accounting system of record before go-live, so finance can trust the numbers in HubSpot from day one.