One post tagged with "salesforce for sales teams"

Connecting HubSpot and Salesforce is the single most powerful step you can take to get your marketing and sales teams rowing in the same direction. When you sync this data, sales reps get crucial marketing insights right inside their CRM, and marketers can finally see which campaigns actually make the cash register ring.

This guide will show you exactly how to build a rock-solid, practical integration designed specifically for the needs of an outbound SDR team. We'll move beyond theory and give you actionable steps, comparisons, and workflows to turn this connection into a revenue-driving machine.

Why Bother Integrating HubSpot and Salesforce for Your SDR Team?​

Let's be honest. Your SDRs are probably wasting a huge chunk of their day flipping between browser tabs and copy-pasting information. This isn't just inefficient; it’s a direct hit to your pipeline. When HubSpot's marketing brain isn't talking to Salesforce, your sales floor is flying blind.

SDRs end up chasing leads that marketing already knows are a dead end. Or worse, they call a prospect moments after that person received a completely unrelated marketing blast. This disjointed approach creates a jarring experience for buyers and torches good leads. All the while, sales leaders can't trust their forecasts because the data in Salesforce is only half the story.

Turning Raw Data Into Real Conversations​

The entire point of this integration is to turn passive marketing data into an active, intelligent outbound sales strategy. Instead of reps having to log into HubSpot to see if a lead opened an email, that activity just shows up on the contact record in Salesforce. Simple.

The real magic happens when you turn HubSpot’s marketing intelligence into prioritized, actionable tasks inside Salesforce. This gives reps the context they need for meaningful conversations, moving them from generic "cold calls" to well-timed, informed outreach.

This unified view gives your team immediate answers to the questions that matter most:

• What marketing campaign got this person's attention?
• Did they look at our pricing page in the last 24 hours?
• Have they downloaded a key whitepaper or case study?

This kind of real-time insight is non-negotiable. As of 2026, HubSpot's native Salesforce integration has become essential for mid-market B2B teams. It flawlessly syncs contacts, companies, deals, and activities, breaking down the data silos that frustrate 70% of teams using hybrid CRM setups.

From Disconnected Tools to a Cohesive Sales Engine​

Think about the daily grind with a disconnected tech stack. An SDR wastes their first hour cross-referencing new MQLs in HubSpot against Salesforce to hunt for duplicates. It's a manual, soul-crushing task that’s ripe for errors and a complete waste of selling time.

A properly built integration automates that entire mess. A new lead in HubSpot can instantly create a corresponding record in Salesforce, assign it to the right rep, and even generate a follow-up task—all based on rules you set. This means your speed-to-lead is as fast as it can be, and your reps can spend their time actually selling.

Before you even start the integration, having the right foundation is key. If you're still evaluating your core platform, reviewing a guide on the best CRM for sales teams can help ensure your primary system is built for success.

Common Outbound Challenges and Integration Solutions​

For SDR teams, the gap between marketing and sales isn't just a philosophical problem—it creates tangible, daily roadblocks. The table below breaks down these common headaches and shows exactly how a solid HubSpot-Salesforce sync provides the cure.

SDR Challenge	Impact of Disconnected Systems	How Integration Provides the Solution
Lack of Context	Reps make generic, "cold" calls without knowing a lead's recent marketing engagement.	Marketing activities (email opens, page views) are logged directly on the Salesforce contact record, providing instant context.
Slow Lead Handoff	Marketing Qualified Leads (MQLs) sit in a queue, waiting for manual review and assignment.	Automation rules instantly create and assign new leads in Salesforce the moment they hit the MQL threshold in HubSpot.
Manual Data Entry	SDRs waste hours logging calls, emails, and notes in two separate systems.	Activities logged in one system (e.g., a call in HubSpot) automatically sync to the other, eliminating double work.
Inaccurate Reporting	Sales leadership can't accurately attribute revenue to specific marketing campaigns.	Closed-won deals in Salesforce sync back to HubSpot, providing a clear ROI picture for marketing efforts.
Poor Lead Prioritization	Reps don't know which leads are "hot" right now and treat all MQLs equally.	Lead scoring from HubSpot syncs to Salesforce, allowing reps to build views and prioritize the most engaged prospects first.

As you can see, the integration isn't just about moving data around. It's about creating a smarter, faster, and more informed sales process that directly impacts your team's ability to hit its numbers.

Your Pre-Integration Strategic Checklist​

Jumping straight into the technical setup without a solid game plan is a classic recipe for disaster. A truly successful HubSpot ↔ Salesforce integration starts with strategy, not software. Before you even think about connecting the two, you need a blueprint. This is what separates a clean, efficient sync from the all-too-common "plug and pray" approach that leaves you with a data nightmare.

This whole planning phase is really about asking the tough questions upfront. Who actually owns the data? Which system gets the final say on a contact's lifecycle stage? What’s the rule for when a record gets updated in both systems at the same time? Answering these questions now will save you countless hours of untangling messy data and chasing sync errors later.

Define Your Single Source of Truth​

This is probably the most critical decision you'll make. You have to define the single source of truth for each core data object. This is what tells the integration which platform's data wins out and overwrites the other during a conflict. If you get this wrong, your SDRs could be working with stale contact info while marketing runs campaigns based on totally incorrect sales statuses.

There’s no one-size-fits-all answer here; it’s all about how your teams actually work. For most outbound SDR teams I've worked with, this is a pretty effective setup:

Data Object	Recommended Source of Truth	Why It Works for SDR Teams
New Leads	HubSpot	Marketing is generating the inbound leads from web forms, content, and campaigns. Let that be the entry point.
Contact Info	Salesforce	SDRs and AEs are on the front lines, constantly enriching and verifying phone numbers, titles, etc. Their data should be king.
Lead Status	Salesforce	Your sales team owns the lead lifecycle, hands down. From 'New' to 'Disqualified' or 'Converted,' Salesforce dictates the stage.
Company Data	Salesforce	Sales typically owns the account-level details like firmographics and complex parent-child relationships.

Getting this logic nailed down from the start prevents a ton of confusion and protects the integrity of your most valuable asset—your data.

Audit and Clean Your Existing Data​

Look, connecting two messy databases just creates one giant, exponentially messier database. Before you sync anything, you absolutely have to audit the data in both HubSpot and Salesforce. This step is non-negotiable if you want to avoid a flood of duplicate records and frustrating sync failures.

Start by running some simple reports in both systems to flag:

• Duplicate Records: Hunt for contacts and companies that share the same email or company domain.
• Inconsistent Data: Standardize your picklist values. "USA," "United States," and "U.S.A." should all be the same thing.
• Outdated Information: Find those contacts with no activity for over a year or accounts for companies that no longer exist.

Pro Tip: Don't just clean up the current mess and call it a day. Use this as a chance to build a real, long-term data hygiene strategy. Document the rules and set up processes to keep it clean. For a much deeper look at this, our guide on automating your CRM hygiene has some great frameworks.

This isn’t just busywork; it's directly tied to the integration's ROI. A clean, well-oiled integration can deliver an average ROI of 324% within the first year. Why? Because it slashes manual data entry—saving reps up to 15 hours a week—and finally gives you unified reporting that connects marketing spend directly to revenue. If you need to build a business case, these integration ROI statistics are pretty compelling.

Map Your End-to-End Customer Journey​

Last but not least, you need to document every single field and process that a lead touches, from their very first visit to your website all the way to a closed-won deal. This means mapping out every lifecycle stage, every custom property in HubSpot, and every corresponding custom field in Salesforce.

You'll find the native integration app right in the HubSpot Marketplace, and this is your technical starting point.

This screen is just the gateway. The real work is in making sure the data structures behind it are ready for a smooth handoff.

This exercise forces you to be ruthless about what data is actually essential for your SDR team. Do they really need all 50 of marketing’s custom properties cluttering up the Salesforce contact record? Probably not. A clear data map ensures you only sync the information that drives action, keeping Salesforce clean and your reps focused on what matters.

Getting Your Hands Dirty: A Practical Walkthrough of the Connection​

Alright, you've done the strategic thinking. Now it's time to roll up your sleeves and actually connect the two platforms. Don't worry, this isn't nearly as intimidating as it sounds. The HubSpot integration wizard does a great job of holding your hand, but knowing the critical decision points before you start clicking is the key to a smooth, error-free setup.

The whole process kicks off in HubSpot, not Salesforce. You'll just head over to the App Marketplace, search for the official Salesforce integration, and get started. Make sure you use the native, HubSpot-built app—steer clear of any third-party connectors for now. Keeping it simple and officially supported is the name of the game.

Making the Handshake: Authentication and Permissions​

Once you find the app and click install, you’ll be prompted to log into your Salesforce account. This is your first major checkpoint, and it's a big one. You absolutely must authenticate with a Salesforce user that has the right permissions.

Trying to use a standard user profile will cause headaches right out of the gate. You need a Salesforce user with "Modify All Data" and "API Enabled" permissions, which usually means a System Administrator profile. Giving the integration this level of access is non-negotiable; it's what allows it to freely create, read, and update records between both systems as you've intended.

I've seen teams try to use a lower-permission user to "limit" the integration's scope. It always backfires. This leads to a constant stream of frustrating sync errors for records the integration user can't "see" or edit in Salesforce. Just use a dedicated integration user or a full System Admin and save yourself the trouble.

Setting Up the Bouncer: Your Inclusion List​

After you've logged in, HubSpot will walk you through setting up an inclusion list. Honestly, this is probably the single most powerful feature for preventing data chaos. Instead of just opening the floodgates and syncing your entire Salesforce database, the inclusion list acts as a bouncer at the door, only letting specific, pre-approved records pass between systems.

This is the critical difference between a clean, intentional setup and a "sync everything" disaster. A wide-open sync can instantly pull thousands of old, irrelevant contacts into HubSpot, blowing up your contact tier limits and filling your marketing database with junk.

For an SDR-focused setup, a Salesforce Active Rule is the perfect starting point for your inclusion list.

• Actionable Step: Create a new Salesforce Active List in HubSpot with a rule like: Lead Status is not one of (Unqualified, Bad Data) AND Contact: Do Not Email is False. This simple but effective rule ensures only active, contactable leads and contacts ever make it into HubSpot. Your marketing database stays clean and focused on engageable prospects from the very beginning.

Choosing What to Sync: Objects, Fields, and Activities​

Next up, you'll decide which objects to sync. The standards are Contacts, Companies, and Deals. For most teams, syncing all three is the right call. You'll also configure how activities—like tasks, emails, and notes—flow between the systems. This is where you really start to dial in the integration for your SDR team's specific workflow.

A key decision here is the direction of your activity sync. Should a logged call in HubSpot create a completed task in Salesforce, or should it work the other way around?

Activity Sync Direction	The Good	The Bad	Who It's For
HubSpot to Salesforce	Captures every marketing and sales touchpoint in your system of record (Salesforce).	Can clutter the Salesforce activity timeline if you don't manage it carefully.	Teams where SDRs live in HubSpot tools (sequences, dialer) but leadership lives in Salesforce reports.
Salesforce to HubSpot	Keeps the HubSpot contact timeline fresh with sales activities, which is great for lead scoring and automation.	A less common setup, since Salesforce is usually the main activity hub.	Niche cases where HubSpot automation relies heavily on specific sales actions being logged.

When you're starting out, a one-way sync from HubSpot to Salesforce for tasks and engagements is a fantastic choice. It enriches the Salesforce record with all that great activity context without creating confusing bidirectional loops. If you want to dive deeper, a good HubSpot Salesforce integration guide can walk you through all the nuances of connecting your platforms and mapping your fields.

Flipping the Switch: The First Sync and Monitoring​

Once you've locked in your settings, you're ready to start the initial data sync. Now, be patient. Depending on the size of your inclusion list, this can take several hours. HubSpot gives you a health dashboard where you can watch the progress and, more importantly, see any sync errors that pop up.

Don't panic when you see errors. They are 100% normal during the first pass as the integration bumps into unique data validation rules or weird formatting in your records. The dashboard will tell you exactly which records failed and why, so you can fix them one by one. Think of this initial sync as the final, real-world test of your planning and data hygiene—it’s the last layer of validation before you let your teams loose on the new setup.

2. Nailing the Field Mapping and Sync Logic​

Okay, getting the two platforms connected is the first step, but it’s just the plumbing. The real magic happens when you control exactly what data flows through those pipes, how it flows, and what happens when there's a disagreement. This is where you graduate from a simple data mirror to an intelligent system that actually helps your SDRs sell.

This is all about field mapping and sync logic. You're essentially telling the integration which pieces of information to share, which direction they should travel, and which system gets the final say. Get this right, and your SDRs will have unshakable trust in their Salesforce data. Get it wrong, and you introduce a subtle but constant drag on their productivity and confidence.

This flowchart walks through the essential checkpoints for getting the connection right before you even think about syncing data.

As you can see, confirming user permissions and setting up a clear inclusion list aren't just suggestions—they are foundational steps to prevent absolute data chaos down the line.

Turning Marketing Signals into Sales Actions​

Let's get practical. A generic field map is fine, but one designed specifically for an SDR workflow is a massive advantage. The goal is to translate HubSpot's rich marketing engagement data into specific, actionable fields inside Salesforce that your reps can use to prioritize their day.

Think about it this way: a prospect opens your latest marketing email three times and clicks through to the pricing page. In a disconnected setup, that’s just a number on a marketing dashboard. With smart mapping, it becomes an immediate, high-priority sales trigger.

Here’s an actionable playbook to build this:

• Step 1: Create a custom field in Salesforce. Go to the Contact object and add a new date field called something like "Last Marketing Engagement Date."
• Step 2: Map the HubSpot property. Jump into your integration settings and map the standard HubSpot property "Last marketing email open date" directly to that new custom field in Salesforce.
• Step 3: Build the automation in Salesforce. Use a simple Flow that says, "When the 'Last Marketing Engagement Date' field is updated today, automatically create a high-priority task for the contact owner."

Just like that, your SDRs are no longer just working down a static list. They're getting real-time alerts about who's most engaged right now, letting them strike while the iron is hot.

One-Way vs. Bidirectional Syncs: A Comparison for SDR Teams​

Choosing between a one-way and a two-way (bidirectional) sync is a critical decision. It dictates who "owns" the data and can prevent valuable sales insights from being accidentally overwritten by marketing automation.

Sync Type	How It Works	Best For	SDR Team Impact
One-Way Sync	Data flows in only one direction (e.g., HubSpot → Salesforce). Changes in the destination system are ignored.	Data points with a single, clear owner, like Lead Source from marketing or Lead Status from sales.	High Predictability. Reps know that certain fields won't change unexpectedly. This builds trust in the data.
Bidirectional Sync	Data flows in both directions. An update in either system will sync to the other.	Fields that both teams need to update, like First Name or basic contact info.	High Flexibility, Higher Risk. Makes it easy for anyone to update data, but requires strict "source of truth" rules to prevent data conflicts.

The secret is to use a hybrid approach. Don’t set everything to be bidirectional. Instead, establish a clear "owner" for every important piece of data and set the sync direction accordingly.

Sample Sync Logic and Rules for an SDR Team​

Here’s a practical, actionable template for setting up your field-level sync logic.

Data Field	Recommended Source of Truth	Sync Direction and Rule	SDR Workflow Impact
First Name, Last Name, Email	Salesforce	Bidirectional	Both teams can update, but Salesforce wins in a conflict. Ensures the SDR's direct contact info is always preserved.
Lead Source	HubSpot	One-Way: HubSpot to Salesforce	Marketing owns the initial source. SDRs see exactly where the lead came from (e.g., "Webinar," "eBook Download").
Lead/Contact Status	Salesforce	One-Way: Salesforce to HubSpot	Sales owns the pipeline stage. This prevents marketing from nurturing a lead an SDR has already disqualified or is actively working.
MQL Date	HubSpot	One-Way: HubSpot to Salesforce	The date a lead met marketing's criteria is a key piece of context. It’s a marketing-owned data point that SDRs need to see.
Last SDR Activity Date	Salesforce	One-Way: Salesforce to HubSpot	SDRs log calls/emails in SFDC. This data flows to HubSpot to suppress these contacts from general marketing campaigns.

This kind of hybrid approach gives each team autonomy over their core data while providing everyone with the visibility they need to do their jobs effectively. If you're managing even more complex data flows, you can find great strategies for managing multi-CRM sync automation that build on these same principles.

Making Sense of Conflict Resolution​

Even with the best logic, conflicts are inevitable. An SDR updates a phone number in Salesforce at the exact same moment an automation rule updates a different field on the same record in HubSpot. Who wins? That’s where your conflict resolution settings come in.

You essentially have two choices:

• Prefer Salesforce: If a record is updated in both systems simultaneously, the Salesforce value is kept.
• Prefer HubSpot: In the same situation, the HubSpot value overwrites the change made in Salesforce.

The rule of thumb here is dead simple: Always set your conflict resolution to prefer your designated source of truth. If Salesforce is where your official contact data lives, the rule should be "Prefer Salesforce." This is your safety net.

While you can set it to prefer the most recent update, I strongly advise against it. It can be wildly unpredictable and is a nightmare for SDR teams who live and breathe out of Salesforce as their system of record. Sticking with a clear "prefer X" rule removes all ambiguity.

Automating SDR Tasks and Activity Logging​

Alright, your data is flowing cleanly between HubSpot and Salesforce. Now for the fun part: turning that passive data stream into an active, intelligent engine that fuels your SDR team. This is where the integration moves beyond simple data hygiene and starts making a real impact on productivity.

We're going to take those rich marketing signals from HubSpot and use them to automatically tee up the next best action for your reps, right inside Salesforce.

First things first, let's talk about visibility. Out of the box, the integration adds a HubSpot Intelligence Visualforce component to your page layouts. This is your SDR's secret weapon. It gives them a clean, chronological view of every email open, website visit, and form submission without junking up the main Salesforce activity timeline. Reps get instant context on a prospect’s entire journey before they ever pick up the phone.

Building Proactive Task Creation in Salesforce​

Passive activity logs are great for context, but proactive task creation is what really moves the needle. You want to use HubSpot's data to explicitly tell your SDRs what to do next. Instead of making them hunt through activity feeds for a buying signal, we can build automations that create and assign tasks the moment a high-intent action happens.

Think about a prospect who fills out a "Request a Demo" form. In a disconnected world, that lead might sit in a marketing inbox for hours. With this integration, you can build a Salesforce Flow that fires the instant that form submission syncs from HubSpot.

Here is an actionable recipe for this automation:

• Trigger: Create a Record-Triggered Flow in Salesforce on the Contact object that runs when a record is updated.
• Condition: Set the entry condition to hs_latest_source contains "Demo Request Form."
• Action: Add a "Create Records" element to create a new Task.
• Details: Assign it to the Contact Owner ($Record.OwnerId), set the priority to "High," and use a crystal-clear subject like "Follow Up on Demo Request."

This one automation can slash your speed-to-lead time from hours down to seconds. That’s a massive advantage when research shows that 35-50% of sales go to the vendor that responds first.

The goal isn't just to move data; it's to create motion. By automating task creation based on real-time engagement, you're building a system that ensures no hot lead ever goes cold due to manual delays. Your SDRs can stop hunting for opportunities and start working them.

Comparing Automation Tools: HubSpot vs. Salesforce​

A question I get all the time is where to actually build these automations—should you use HubSpot Workflows or Salesforce Flow? While both are fantastic tools, for any SDR-focused process, Salesforce is almost always the right answer for task creation.

Here’s a quick breakdown of why:

Automation Platform	Best For	SDR Workflow Implications
HubSpot Workflows	Marketing nurturing, internal notifications, and updating HubSpot properties.	Great for enrolling leads into email sequences but not ideal for creating tasks that need to live permanently in the sales CRM.
Salesforce Flow/Process Builder	Creating and assigning sales-owned records like Tasks, Opportunities, and Cases.	This is the native environment for sales. Tasks follow Salesforce assignment rules and are instantly visible in the reports and dashboards your sales leaders live in.

Building your task automations in Salesforce keeps your reps in their primary system, reinforces Salesforce as the source of truth for all sales activities, and makes reporting on SDR productivity a breeze for leadership.

Logging Outbound Calls and Emails​

Finally, we need to close the loop by making sure your SDRs' own outbound activities get logged back correctly. Sure, reps can create records manually, but a truly efficient setup automates this away. This is where tools with native CRM dialers are an absolute must.

For instance, when an SDR uses a Salesforce-native dialer to make a call, the system should automatically log that activity, its outcome ("Connected," "Left Voicemail," etc.), and any notes right on the Contact record. This completely eliminates the manual "after-call work" that slows reps down and ensures your activity data is 100% accurate. For a deeper dive, check out our guide on the best practices for logging phone calls and outcomes in your CRM.

This automated two-way street—marketing signals creating tasks in Salesforce and sales activities logging back—is the hallmark of an integration that genuinely empowers your outbound team.

Troubleshooting Common Integration Pitfalls​

Let’s be real: no matter how carefully you plan, every integration project hits a few snags. The real test isn't avoiding problems, but knowing how to squash them quickly before your teams lose faith in the data. Think of this as your field manual for the most common issues you'll run into when connecting HubSpot and Salesforce.

When things go wrong, your first stop should always be HubSpot’s Sync Health dashboard. This is command central for seeing what’s breaking and why. It gives you specific reasons a record failed to sync, so you can fix the root cause instead of just patching over the symptoms.

Decoding API Limit Errors​

One of the first brick walls you might hit is the Salesforce API call limit. Salesforce gives your organization a set number of API calls it can make every 24 hours. A busy integration, especially during the initial sync or after a big data import, can chew through that limit faster than you’d think.

Once you hit the cap, the sync simply stops, and your dashboard will light up with API limit errors.

The quick fix is just to wait for the 24-hour clock to reset. But for a real, long-term solution, you need to get smarter about your inclusion list. Are you trying to sync every single record? Probably not. Tighten up those sync criteria to reduce the noise, and you'll drastically cut down on the API calls needed to keep everything up to date.

Managing Sync Delays and Latency​

Sometimes the sync just feels slow. An SDR updates a lead in Salesforce, grabs a coffee, comes back, and the change still isn't showing up in HubSpot. When your team's workflow depends on timely data, these delays can be more than just a minor annoyance.

It's crucial to remember that the native integration isn't instantaneous. It syncs data in batches, usually every 5 to 10 minutes. This is perfectly normal, but if you're pushing huge volumes of data or have a ton of complex rules, that timeframe can stretch out.

If you’re consistently seeing frustrating delays, it's often a sign the integration is overloaded. Take a hard look at your field mappings. Do you really need to sync all 50 of those custom fields? Every mapped field adds a little bit of processing overhead, and syncing dozens of Salesforce formula fields, for example, can really slow things down.

Salesforce Validation Rules Blocking HubSpot Updates​

This is, without a doubt, the most common problem I see pop up after an integration goes live. A well-meaning Salesforce admin adds a new validation rule—say, making the "Phone" field required before a Lead Status can be changed to "Working." Suddenly, all your automated updates from HubSpot start failing.

The good news is that the error message in your Sync Health dashboard is usually crystal clear, often even naming the exact validation rule that’s causing the trouble.

Two Ways to Fix This—And One Clear Winner

You have a couple of options here, but one is far more sustainable than the other.

Approach	Description	Pros & Cons
Update the Validation Rule	This involves tweaking the rule in Salesforce to specifically exclude the integration user. The logic might look something like: AND(ISBLANK(Phone), $User.Id <> "INTEGRATION_USER_ID").	Pro: A clean, permanent fix. It lets the integration do its job without compromising data integrity for your human users. Con: Requires you to have (or get) Salesforce admin access.
Adjust HubSpot Workflows	You could try to make sure your HubSpot automations always provide the required data. For example, you could make the phone number field mandatory on a HubSpot form that might trigger the rule.	Pro: Can be handled entirely on the HubSpot side. Con: It’s a reactive fix. You'll constantly be playing whack-a-mole as new validation rules are added.

My advice? Updating the validation rule in Salesforce is almost always the right call. It’s a proactive, robust solution that solves the problem at its source. This approach keeps your integration stable and saves you a world of headaches down the road.

Answering Your Burning Integration Questions​

Even the most meticulously planned integration project will have its share of "what if" moments. It's just the nature of the beast. Here are some of the most common questions that pop up from RevOps leaders and SDR managers, along with straight-to-the-point answers from our experience in the trenches.

How Often Does HubSpot Actually Talk to Salesforce?​

This is a big one for setting team expectations. The native integration doesn't sync in real-time. Instead, it runs in batches, usually every 5 to 10 minutes.

For the most part, that’s perfectly fine. A lead created in HubSpot will show up in Salesforce for your SDRs pretty quickly. But you need to be aware that during a massive data import or the initial sync, things can slow down a bit. It's crucial to tell your team that a new contact won't appear instantaneously. A little bit of patience goes a long way.

What About Our Salesforce Custom Objects? Can We Sync Those?​

Yes, you absolutely can, but there's a catch, and it's a big one. Syncing custom objects between Salesforce and HubSpot is an enterprise-level feature. You'll need a HubSpot Enterprise plan (like Operations Hub or Sales Hub) to make it happen.

This is a make-or-break consideration during your planning phase:

• Standard Integration (Pro Tiers): You're limited to the basics—Contacts, Companies, Deals, and Activities.
• Enterprise Integration: This unlocks the ability to map and sync all those unique custom objects you've built in Salesforce.

If your SDRs live and breathe out of a custom "Target Accounts" or "Product Interest" object in Salesforce, you have to budget for an Enterprise plan. There's no getting around it.

Look, the whole point here is to build a seamless workflow for your reps. If a key piece of their process is locked away in a custom object, that data has to flow into HubSpot. Trying to work around it just creates confusion and kills adoption.

What Happens When Someone Deletes a Record?​

This question trips up a lot of people. By default, when you delete a record in HubSpot, it does not delete the matching record in Salesforce (and vice-versa). This is a safety net built into the integration, designed to prevent a single mistake from wiping out data across both platforms.

You can change this setting to enable deletions to sync, but you need to be extremely careful. We almost always advise clients to leave this setting off. It's far safer to manage record deletion through a deliberate, controlled archival process within each system separately. Think of it as a failsafe; a mistake in one CRM won't cause a permanent, irreversible data catastrophe in the other.

---

Your SDRs shouldn't be guessing what to do next. marketbetter.ai turns buyer signals into a prioritized task list and helps reps execute immediately with AI-powered emails and a dialer that lives inside Salesforce. See how we help you drive more outbound motion at https://www.marketbetter.ai.