Salesforce CPQ to HubSpot
Salesforce CPQ (formerly SteelBrick) is a managed package for configuring, pricing and quoting inside Salesforce CRM. It uses the SBQQ__ namespace.
Salesforce CPQ data can move into HubSpot, landing mainly in Revenue Hub. 1 of 7 mapped objects move directly (Opportunity); 3 items need manual work and 2 do not move. Plan roughly 3-6 weeks for a small move and 12-24 weeks for a large one.
Migration checklist for Salesforce CPQ
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 5 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
<5k quotes, <200 products
Simple pricing, no bundles.
Mid migration
5k-50k quotes, 200-2k products
Some bundles and approvals.
Large migration
>50k quotes, >2k products
Complex configuration, with part of the quoting layer staying external.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Salesforce CPQ: what you need to get in, what lands in HubSpot, and what will not.
Salesforce REST/SOAP/Bulk APIs over SBQQ__ custom objects, plus the CPQ API (Apex and JSON via ServiceRouter)
Salesforce user or integration user with API access and read access to SBQQ__ objects.
Salesforce admin to create the connected app or integration user and grant CPQ object and field access.
Choose your route
How will you move the data?
No native connector was found.
- You need: Salesforce user or integration user with API access and read access to SBQQ__ objects.
- Permission: Salesforce admin to create the connected app or integration user and grant CPQ object and field access.
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Data Loader or Salesforce export of SBQQ__Quote__c, SBQQ__QuoteLine__c, SBQQ__ProductRule__c and price book tables
- Salesforce REST API extraction
- CPQ Quote Reader API for full quote models
- Third-party ETL or migration tools
Limits: To confirm
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 12-24 weeks, usually phased.
Talk to a partnerWhere each object lands
In Salesforce CPQ
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Product2 / Price Book Entries | Products | partial | HubSpot uses a flat product library, so price books, tiers and multi-currency need redesign. |
| SBQQ__Quote__c | Quotes | partial | Historical quotes can be recreated as Revenue Hub quotes or kept as references. The object model must be decided before field mapping. |
| SBQQ__QuoteLine__c | Line items | partial | Import with the Deals & Line Items multiple-object import. Bundle structure is flattened. |
| Opportunity | Deals | yes | Native sync does not backfill historical line items onto existing deals, so they must be attached during import. |
| SBQQ__ProductRule__c / Price Rules | Custom objects | manual | There is no HubSpot equivalent. Pricing and product rules are rebuilt with workflows, or documented only. |
| Contracts / SBQQ__Subscription__c | Custom objects | partial | Revenue Hub contracts and subscriptions can hold references, but the mapping is custom. |
| Quote templates and approvals | Quotes | manual | Rebuild as HubSpot quote templates and approval workflows. |
What to expect
Salesforce CPQ runs only inside a Salesforce org and has no HubSpot version.
Keep the originals in an external archive and store links in HubSpot.
Rules are tied to the SBQQ__ package and are not transferable.
HubSpot has a flat product library with line items on deals.
Native sync does not backfill them, so products must be matched to Salesforce IDs.
Document the rules and decide per bundle whether to flatten it or keep it external.
Use multiple-object imports keyed on deal and product IDs.
Freeze quoting or run a parallel period, since CPQ remains supported.
Archive PDFs and contracts and link them from deal records.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
The CPQ API and end-of-sale status are backed by Salesforce and its partners. Salesforce-to-HubSpot object mapping, rate limits and governance rest on third-party guides and category-level knowledge, with no HubSpot or Salesforce doc for the CPQ-to-HubSpot path.
Sources
Related migrations
Frequently asked questions
How do I migrate Salesforce CPQ to HubSpot?
1. Inventory SBQQ__ objects, price rules, product rules, templates and approval chains. 2. Create an integration user with API access to the SBQQ__ objects. 3. Clean duplicate and abandoned products and price books. 4. Decide the Revenue Hub object model for quotes, contracts and subscriptions.
What data can move from Salesforce CPQ to HubSpot?
These objects move directly: Opportunity. Check the mapping table for partial and manual items.
What does not move from Salesforce CPQ to HubSpot?
Complex product configuration, bundle option logic and constraint rules and Signed-document evidence and redlines. Plan to rebuild or retire these.
How long does a Salesforce CPQ to HubSpot migration take?
Small (<5k quotes, <200 products): 3-6 weeks. Mid (5k-50k quotes, 200-2k products): 6-12 weeks. Large (>50k quotes, >2k products): 12-24 weeks. These are planning estimates, not a quote.
What access do I need to export from Salesforce CPQ?
Salesforce user or integration user with API access and read access to SBQQ__ objects. Salesforce admin to create the connected app or integration user and grant CPQ object and field access.
Is there a native HubSpot connector for Salesforce CPQ?
No native connector was found. Plan a CSV, API or third-party tool route.
What compliance issues apply when moving Salesforce CPQ data?
Check: Financial or contract terms and Possible customer pricing confidentiality. Agree consent, retention and access rules before exporting.
Moving Salesforce CPQ into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner