Duplicate leads
The weekly import did not match.
BoldBellowsHubSpot Salesforce integration for companies where marketing works in HubSpot and sales lives in Salesforce
HubSpot to Salesforce automation that syncs contacts, companies and deals both ways by External ID, with field owners and a queue for rejected records
HubSpot speaks of contacts, companies and deals while Salesforce speaks of leads, contacts, accounts and opportunities, and Salesforce limits how many API requests an org may make each day, so a sync that guesses at matches wastes both its limit and your data. BoldBellows agrees how HubSpot contacts, companies and deals map to Salesforce leads, contacts, accounts and opportunities, which system owns each field and the External ID that will tie the two together, upserts by that External ID so a record is created once, translates lifecycle stages into lead status and opportunity stages, and queues anything Salesforce rejects with its reason, then builds the sync around your sales process. A marketing qualified contact in HubSpot becomes a lead or contact in Salesforce, a won opportunity updates the HubSpot deal, a field edited by a rep wins over a marketing value where you say so, and rejected records wait in a queue with their error. This is the tidy way to move HubSpot contacts into Salesforce and keep both CRMs honest.
View Pricing
One-off setup from $1,075
No monthly subscription
- Sync HubSpot contacts to Salesforce
- Upsert by External ID
- Rejections queued with the reason
- Upsert by External ID a record is created once
- Stages translated lifecycle to lead status and opportunity stage
- Field owners one system wins each field
- Rejections queued with the Salesforce error
- Written handover The route, the controls and the repair steps arrive as a PDF
- Quoted before you commit the Foundation package begins at $1,075 and the total is visible before checkout
Chapter 01 the two-CRMs problem
Two CRMs that each think they own the Salesforce customer spend their days overwriting each other
Marketing works in HubSpot and sales works in Salesforce. A weekly import creates duplicate leads, so reps phone people twice. A rep updates the phone number in Salesforce and a nightly job puts the old one back from HubSpot. Deal outcomes never travel to marketing, so a customer is still receiving the prospect nurture. Salesforce rejects records with a missing required field, and the failures sit in an email nobody reads.
The first week with no duplicate leads, and a rep said it was the first time she trusted the list.
Edits overwritten
A nightly job restored old values.
Outcomes that never return
Marketing cannot tell who bought.
Before
After
Before
- Every event is written as it arrives
- A weekly import creates duplicates
- Edits are overwritten by a nightly job
After
- Each write is keyed on an External ID field holding the HubSpot object ID
- Records are upserted by External ID and owned by one side per field
- Outcomes return to HubSpot and rejections wait in a queue
Chapter 02 How it works
How a qualified contact becomes one Salesforce record with a deal that reports back
A change is admitted, identified, matched and written, always in that order.
Receive and qualify
The notification is authenticated, stamped with account, resource and time, then checked against the admission rule.
Read, map, upsert
The HubSpot record is read, mapped to the right Salesforce object and upserted by External ID.
Return, queue, protect
Outcomes return to HubSpot, rejections are queued and field ownership prevents overwrites.
Behavior of HubSpot and Salesforce we design around
- Two CRMs, two vocabularies: HubSpot speaks of contacts, companies and deals while Salesforce speaks of leads, accounts and opportunities, and the integration decides which object in one becomes which in the other.
- Upsert is the safe verb: An upsert by External ID creates a record if none exists and updates it if one does, so a repeated event cannot create a copy.
- If a reply is lost: The route reads Salesforce through an External ID field holding the HubSpot object ID to learn whether the write landed, then acts on the answer.
Chapter 03 What ships in the build
Inside the Salesforce route: mapping, upserting and queuing
Foundation sets the rules and the key. Operations does the writing. Assurance compares both sides over time.
Admission rule engine
Decides which HubSpot events may proceed and logs why the others were set aside, in the HubSpot to Salesforce route.
Stable identity ledger
Pairs every HubSpot record with its Salesforce counterpart in a ledger you can read.
Allowlist mapper
Maps approved HubSpot fields to Salesforce fields one by one and rejects anything not on the list.
Object mapper
Maps contacts, companies and deals to leads, contacts, accounts and opportunities.
External ID upsert
Creates or updates by one stable ID, so there are no duplicates.
Stage translation
Turns lifecycle stages and deal stages into Salesforce statuses and stages.
Field ownership
Decides which system wins each field and prevents loops.
Rejection queue
Holds records Salesforce refuses, with the error and an owner.
Owner queue
Gives each unresolved HubSpot case a named owner, so nothing waits in a shared inbox, in the HubSpot to Salesforce route.
Whether it is HubSpot Salesforce API integration, HubSpot Salesforce workflow or sync HubSpot contacts to Salesforce, start here. Related searches include HubSpot to Salesforce Zapier, HubSpot to Salesforce, HubSpot Salesforce contact create, HubSpot deals Salesforce mapping, HubSpot Salesforce lead capture, HubSpot deal to Salesforce opportunity, HubSpot lead to Salesforce lead, HubSpot Salesforce integration, connect HubSpot to Salesforce, HubSpot Salesforce CRM sync, HubSpot Salesforce automation, HubSpot Salesforce duplicate prevention, HubSpot Salesforce two way sync, HubSpot Salesforce opportunity and HubSpot Salesforce external id.
Chapter 04 Who this fits
Built for office managers, and for anyone who must run one customer story across HubSpot and Salesforce, with each system owning what it should and neither overwriting the other
Two CRMs can work together when each owns what it is best at and the handoff between them is exact.
RevOps lead
"Get one customer view."
Both CRMs agree on the same record.
Sales rep
"Stop duplicate outreach."
Leads exist once in Salesforce.
Marketing manager
"See who became a customer."
Outcomes return to HubSpot.
Salesforce admin
"Stay inside the limits."
Writes are batched and paced.
HubSpot admin
"Keep marketing data clean."
Rep edits are respected.
Sales director
"Trust the pipeline."
Stages are translated by rule.
Chapter 05 The options
Three ways to connect HubSpot and Salesforce: a bulk import that creates duplicates, a zap, or a two-way sync with External IDs, field owners and a rejection queue
Each can hold a customer. Only one upserts by a stable ID and lets each system own its own fields.
| Question | Bulk imports | A basic zap | Our External ID route |
|---|---|---|---|
| What starts the work | A person spots the update | Every matching hook runs | Only a CRM change that meets the written rule |
| How identity is decided | Whoever it is checks the name | Email or name, compared as typed | Imports, overwrites and unread errors |
| What reaches Salesforce | Fields typed from memory | Every mapped field, as plain text | External IDs, field owners and a rejection queue |
| After an uncertain result | Someone checks by eye | Retry, or give up | Searches by an External ID field holding the HubSpot object ID, compares, then repairs |
A late notice follows a newer update
The timestamp on the incoming Salesforce event is checked first; a stale one is recorded and closed instead of rolling the record back.
Salesforce rejects a lead because a required custom field is empty
The record is queued with the exact error, a person fills the field or adjusts the rule, and the route retries it without creating a second lead. The route looks for the record through an External ID field holding the HubSpot object ID, compares it with the intended values and records a verdict: absent, correct, different or unclear. A new Salesforce record is made only when the search proves there is none.
Start the HubSpot to Salesforce build with an External ID field holding the HubSpot object ID; the rest of the route leans on it.
Interlude What drives the cost: objects, fields and stages
Estimate the Salesforce build object by object
Three packages, three quick questions and a live total: that is how you price the HubSpot to Salesforce build. It starts at $1,075.
View Pricing
One setup fee · Range shown first
Pricing
Build your HubSpot to Salesforce price
Pick a package, answer three short questions about how HubSpot data should reach Salesforce, and your price and turnaround move as you choose.
Chapter 06 The process
Six steps from imports to a two-way sync
From the first brief to the first month live, six steps with clear outputs.
-
About 30 minutes
Map objects and stages
We map HubSpot objects and stages to Salesforce and decide which system owns each field.
-
Access review
Approve access
Together we approve what the route may read in HubSpot and where it may write in Salesforce.
-
Most of the project
Agree External IDs and rules
The External ID field, the upsert rules and the handling of conflicts and rejections are agreed in writing.
-
Before you review
Break it on purpose
For HubSpot to Salesforce, we replay events, delay them, remove fields and revoke access in a safe Salesforce copy before anything goes live.
-
Handover day
Launch with notes
We switch the route on at a checkpoint you approve and leave you with written notes on how it works.
-
About 30 minutes
Review after launch
Once real events flow, the opening weeks are checked against the evidence log so early surprises are caught and recorded.
Chapter 07 Turnaround
Timing for the Salesforce build
The clock starts once HubSpot and Salesforce access are approved.
Foundation
4 to 7 business days
Operations
7 to 11 business days
Assurance
11 to 16 business days
Chapter 08 Getting started
What you supply to begin
Approved, revocable access to the HubSpot side
Admin access to HubSpot and Salesforce, a connected app or user for the API and your object and stage map
An authorized HubSpot connection for the resources named in scope
Your definition of which CRM changes should reach Salesforce
Permission to run tests against a copy of Salesforce
Your expected volume, so limits and pacing can be set
Chapter 09 Trust
Nothing is installed in HubSpot or Salesforce, only mapped data moves
Only agreed HubSpot data leaves, and it goes to one named place in Salesforce.
Nothing installed inside either tool
The route talks to HubSpot and Salesforce only through documented endpoints, so neither needs a plugin, a patch or a hidden setting.
Scoped, revocable access
Scopes are reviewed with you before launch and again at handover.
Only what the map allows
A written field map decides what crosses. Anything not on it, including private notes and billing data, is left behind.
Search before you write again
After any uncertain result the route looks for the record using an External ID field holding the HubSpot object ID; only a proven absence allows a new one.
Minimal logging
Logs hold identifiers, times and error types, not your customer content.
Full handover
Handover includes the rules, the owners and the repair steps in one PDF.
"Sales and marketing need the same customer, and the build gives them one without taking either tool away."
Steven GrratFounder, BoldBellows
Chapter 10 In their words
What BoldBellows clients say
Verified reviews from business owners who use BoldBellows automations every day, from marketing and data to support and operations.
AI CRM Automation
Our CRM was barely used because updating it by hand was tedious. BoldBellows automated data entry, tagging, segmentation and follow-ups.
Now the CRM is always up to date and our campaigns are far more accurate. It improved our whole sales pipeline.
AI Lead Qualification & Sales Automation
Our sales team wasted hours chasing cold leads. BoldBellows built an AI lead-scoring system that reads behavior, email engagement and buying signals.
It filters out weak leads and sends personalized follow-ups automatically, so our team only talks to people who are ready to buy. Conversions rose 40% in the first month. It paid for itself straight away.
AI Translation & Localisation
When we expanded abroad we needed fast, accurate translations. BoldBellows built an AI translation system that turns our content into several languages instantly.
The translations read naturally and suit each culture. We now serve customers in five new countries without hiring translators. BoldBellows helped us go global.
AI HR & Recruitment Automation
Our HR team was drowning in applications. BoldBellows automated screening, skills-based filtering and interview scheduling.
It saves us hours every week and means we only interview qualified people. Hiring is now faster, better organized and more professional.
AI Accounting & Invoice Automation
BoldBellows automated our whole invoicing process: creating invoices, sending reminders and tracking payments.
Late payments dropped sharply, and our accounting team finally has time for strategy instead of repetitive admin. Worth every penny.
AI Data Entry & Reporting Automation
We used to spend hours collecting data and building weekly reports by hand. BoldBellows automated all of it.
The reports are clean, visual and easy to read, and our managers rely on them for quick decisions. Human error is gone and our numbers are more accurate across the board.
AI E-commerce Listings Automation
BoldBellows automated our product listings. The AI writes descriptions, organizes photos and publishes listings across several marketplaces.
It even answers customer questions instantly. Our store looks more professional and sales have noticeably increased.
AI Customer Journey Automation
We wanted a smoother path from first contact to purchase. BoldBellows built an AI system that guides each customer there automatically.
It sends personalized messages, recommends products and follows up at just the right moment. Customer retention has improved dramatically.
AI Document & Contract Automation
Onboarding was slow because we wrote every contract by hand. BoldBellows automated the lot: contracts, welcome emails and client setup.
What took 48 hours now takes under 10 minutes, and clients regularly tell us how professional it feels.
AI Chatbot & Customer Support
BoldBellows built an AI support chatbot for our online boutique, and it has changed how we run the business. We used to have two full-time staff answering the same questions all day. Now the AI handles order tracking, product recommendations and even refund requests on its own.
What surprised me most is how natural it sounds. Customers compliment the ‘agent’ without realizing it’s AI. Our support workload dropped by 75% and customer satisfaction went up dramatically.
AI Content & Social Media Automation
Our marketing agency couldn’t keep up with content. BoldBellows set up an AI content engine that writes blog posts and captions and even designs our social media creatives.
It spots trends and suggests topics for us, so we stay ahead of competitors. We now produce three times the content with the same team, and engagement has soared. They didn’t just automate our workflow, they lifted our whole brand.
AI Video & Voice Automation
We publish product videos every week, and BoldBellows introduced us to AI video automation. The system writes the script, voices it and produces the finished video in minutes.
The quality is remarkable: professional voiceovers, clean visuals and smooth editing. Production time went from three days to under 30 minutes, and we scaled our video marketing without adding cost.
AI Email & Smart Inbox Management
Our inbox used to be chaos. BoldBellows built an AI email system that sorts messages, drafts replies and flags anything urgent.
It learns how we write and gets better every week. We reply faster and no longer miss important messages. It feels like having a personal assistant working around the clock.
AI Workflow Automation for Agencies
Running a digital agency with many clients was overwhelming. BoldBellows built one automation dashboard that tracks tasks, sends updates and creates client reports automatically.
Clients love the transparency and we love the time we get back. Productivity is up, and project delays have dropped to almost zero.
AI Booking & Scheduling Automation
Our coaching business needed a better way to schedule. BoldBellows automated all of it: bookings, reminders, cancellations and follow-ups.
No-shows fell by 60% and clients enjoy how smooth it is. It feels personal, not robotic. One of the best upgrades we’ve made.
AI Social Comment & DM Automation
We get thousands of comments and messages every week. BoldBellows built an AI system that replies instantly, filters spam and surfaces the important ones.
Engagement is up and our page looks active around the clock. It’s like having a full social media team that never stops.
AI Voice Assistant
BoldBellows built a custom AI voice assistant for our customer hotline. It answers questions, books appointments and handles simple requests.
Customers love how fast it is, and our call-centre workload dropped dramatically. One of the smartest upgrades we’ve made.
AI Automation Partner
BoldBellows is hands-down the best AI automation partner we’ve worked with. Their systems are fast, reliable and built around how our business actually works.
Every automation they’ve delivered, from customer service to content, runs flawlessly. We’ve saved time, cut costs and grown faster than we expected.
Chapter 11 Questions
HubSpot and Salesforce: questions from RevOps and sales teams
A handful of honest answers before you spend anything.
We tried a HubSpot to Salesforce Zapier flow; what changes?
When the same contact, account and deal in both CRMs is all that is wanted, a connector can manage that. It cannot map the objects, upsert by External ID, translate stages and queue rejections for a person. Those gaps are the reason this build exists.
What links a HubSpot record to its Salesforce twin?
An External ID field you create in Salesforce, which the route upserts by so each record is created once.
What does a simple zap miss between HubSpot and Salesforce?
A zap can create a record; upserts by External ID, stage translation, ownership rules and a rejection queue are what this build adds.
Does it sync in both directions?
Yes, with each field owned by one system so they never overwrite each other.
What happens to Salesforce validation errors?
The record is queued with the error and an owner and is retried after the fix.
Will it use up our API limit?
Writes are batched and paced, and the route reports how much of the limit it uses.
Can it work with a Salesforce sandbox first?
Yes. We test the full mapping in a sandbox before anything touches production.
Will you map custom fields as well on the HubSpot to Salesforce route?
Absolutely. Nothing reaches Salesforce until the HubSpot Salesforce field mapping service has your approval on the page.
Is a tailored workflow possible, or only a standard one on the HubSpot to Salesforce route?
Yes. Anything you can state as a rule can become part of a custom HubSpot workflow for Salesforce. That includes HubSpot Salesforce integration consultant advice, from $1,075.
What happens if HubSpot or Salesforce changes something later?
You get a list of the interfaces we rely on. When one shifts, the affected records hold and you are told. Later maintenance is quoted on its own.
Give sales and marketing one record and one set of facts
Hand us the trigger and the target, and we return the means to automate HubSpot data to Salesforce, with tests and documentation, starting at $1,075.
- From $1,075, paid once
- Upsert by External ID
- Field owners
- No monthly fee from us