Has anyone found a good way to get around the requirement for Opportunity Record Type ID in order to sync opportunities to deals in the Salesforce integration? I literally have run into this issue SO many times in the past few months and it doesn’t appear that HubSpot has any plans to change this about the integration, although I did create an ideas post for it here: Stop automatically mapping Salesforce Opportunity Record ID to Deal Pipeline - HubSpot Ideas - HubSpot Community
Many, many people do not use Opportunity Record Types in Salesforce, and this prevents them from being able to sync their opportunities to HubSpot because it automatically syncs Record Type ID to the Deal Pipeline, which is a prerequisite to creating a deal. How can I get around this without having to ask my clients to assign a new Opportunity Record Type to every single opportunity?
Also, I don’t think that Record Type is the same exact thing as Deal Pipeline in most cases, because people use it as more of an “opportunity type” field. I really do not understand why the integration is like this. Any insight would be appreciated!
Hi @katherineladue,
Thank you for reaching out to the Community!
I wanted to tag in a couple of subject matter experts here to see if they can help:
hi @Drew_Cohen, @MandyDROS, @Aakar, do you have any input on this matter? Thank you!
Cheers
Mia, Community Team
Hello @katherineladue !
We have done this using Zapier! It can be used as an alternative to HubSpot’s native Salesforce Opportunity sync. You can trigger from Salesforce Opportunities, filter and transform the data, map Salesforce stages to a specific HubSpot pipeline, and create the HubSpot deal directly.
For a reliable implementation, you can store the Salesforce Opportunity ID in a custom HubSpot property (“Create and edit properties”) and use it to find/update existing deals rather than creating duplicates. You’ll also need to separately configure contact/company associations and decide whether updates need to flow back to Salesforce. This bypasses the Record Type ID requirement, but it becomes a custom integration that you’ll need to monitor and maintain.
Have you tried that as a solution? We did a very complex integration for a client between SF and HS that was necessary because of this exact issue.
You can use whatever data is necessary to trigger, filter, and feed info into the HS deal record from SF and create a deal.
Do you need that deal information or any part of the deal record to sync back to SF? If so, what information?
Moderator Note: this post was reviewed for relevancy and optimized for clarity on August 28, 2026. Thank you for your contributions to the HubSpot Community!
Oh, very good point! Was that a huge amount of work to get set up and configured with Zapier?
After consulting with support (again), it’s recommended to assign affected Opportunities to an active Salesforce Opportunity Record Type associated with a valid Sales Process. If the native integration cannot meet the client’s requirements, a middleware tool such as Zapier (as you mentioned) can be used to trigger from Salesforce, map the relevant fields and stages, and create or update deals directly in a selected HubSpot pipeline. A custom Salesforce Opportunity ID field should be stored in HubSpot to prevent duplicate deals and support future updates. Here is the article about it “Sync Salesforce opportunities to HubSpot”.
With the specific client I’m working through this with right now, almost all of their deals returned errors at first, but now they are slowly syncing over 1,000 at a time.
However that’s very good to know that Zapier could also be an option, because I’ve also had clients in the past where the integration created a pipeline for each Opportunity Record Type, even the inactive ones, and that was also massively inconvenient.
Moderator Note: this post was reviewed for relevancy and optimized for clarity on August 28, 2026. Thank you for your contributions to the HubSpot Community!
