--- title: "HubSpot Salesforce Integration: Connect or Move Off One?" description: "HubSpot Salesforce integration explained: what syncs, what a full migration to HubSpot changes, and decision rules to connect them or move off one." image: https://www.finemediabw.com/hubfs/Blog/Technology%20and%20RevOps/Revenue%20Operations/Decision/HubSpot%20Salesforce%20Integration%20-%20Connect%20Them%20or%20Move%20Off%20One/hubspot-salesforce-integration-share-1200x630.png --- [![Fine\_Media\_logo\_Set\_HubSpot Website Logo Stacked](https://www.finemediabw.com/hubfs/Fine_Media_logo_Set_HubSpot%20Website%20Logo%20Stacked.svg "Fine_Media_logo_Set_HubSpot Website Logo Stacked")](https://www.finemediabw.com/) - Solutions - [Inbound Marketing](https://www.finemediabw.com/inbound-marketing) - [Website Design](https://www.finemediabw.com/website-design-and-development) - [Sales Enablement](https://www.finemediabw.com/sales-enablement) - [Customer Success](https://www.finemediabw.com/customer-success) - [HubSpot Services](https://www.finemediabw.com/hubspot-services) - [Insights](https://www.finemediabw.com/blog) - [About](https://www.finemediabw.com/about-us) Show submenu for About - [About us](https://www.finemediabw.com/about-us) - [Meet the Team](https://www.finemediabw.com/our-team) - [Our Story](https://www.finemediabw.com/our-story) - Solutions - [Inbound Marketing](https://www.finemediabw.com/inbound-marketing) - [Website Design](https://www.finemediabw.com/website-design-and-development) - [Sales Enablement](https://www.finemediabw.com/sales-enablement) - [Customer Success](https://www.finemediabw.com/customer-success) - [HubSpot Services](https://www.finemediabw.com/hubspot-services) - [Insights](https://www.finemediabw.com/blog) - [About](https://www.finemediabw.com/about-us) Show submenu for About - [About us](https://www.finemediabw.com/about-us) - [Meet the Team](https://www.finemediabw.com/our-team) - [Our Story](https://www.finemediabw.com/our-story) - [Contact us](https://www.finemediabw.com/contact) - [Contact us](https://www.finemediabw.com/contact) ![HubSpot Salesforce Integration: Connect Them or Move Off One? White and dark type on a slate ground, Propello.](https://www.finemediabw.com/hubfs/Blog/Technology%20and%20RevOps/Revenue%20Operations/Decision/HubSpot%20Salesforce%20Integration%20-%20Connect%20Them%20or%20Move%20Off%20One/hubspot-salesforce-integration-share-1200x630.png) Oct 10, 2026, 11:45:45 AM | [HubSpot](https://www.finemediabw.com/blog/tag/hubspot) # HubSpot Salesforce Integration: Connect Them or Move Off One? HubSpot Salesforce integration explained: what syncs, what a full migration to HubSpot changes, and decision rules to connect them or move off one. Share - [mailto:?&subject=HubSpot%20Salesforce%20Integration:%20Connect%20Them%20or%20Move%20Off%20One?&body=HubSpot%20Salesforce%20Integration:%20Connect%20Them%20or%20Move%20Off%20One?%0A(https%3A%2F%2Fwww.finemediabw.com%2Fblog%2Fhubspot-salesforce-integration)](mailto:?&subject=HubSpot%20Salesforce%20Integration:%20Connect%20Them%20or%20Move%20Off%20One?&body=HubSpot%20Salesforce%20Integration:%20Connect%20Them%20or%20Move%20Off%20One?%0A(https%3A%2F%2Fwww.finemediabw.com%2Fblog%2Fhubspot-salesforce-integration)) - - - If your marketing team works in HubSpot and your sales team works in Salesforce, you are choosing between the HubSpot Salesforce integration and one system. Connect them when each team has a real reason to stay put, and move off one when keeping both in agreement costs more than it returns. This article is for CEOs, founders and revenue leaders at growing B2B companies who own that decision. It explains how HubSpot and Salesforce behave once connected, what the integration does and does not sync, and what a full migration involves. Decision rules then help you pick a path and know what to fix first. Our [Salesforce to HubSpot migration](https://www.finemediabw.com/blog/salesforce-to-hubspot-migration) plan shows how to move without losing pipeline. **The short answer:** connect HubSpot and Salesforce when the Salesforce setup is deep, working and owned by a team that will not give it up, and plan to move off one when the integration exists only to paper over a decision nobody has made. Many companies connect first and migrate later.   | **HubSpot Salesforce Integration** The HubSpot Salesforce integration is HubSpot's native connector that keeps records, activities and fields in sync between a HubSpot account and one Salesforce instance, so both systems stay live. | | --- |   | **Full Migration to HubSpot** A full migration to HubSpot moves your records, activities and processes out of Salesforce once, so HubSpot becomes the single CRM and the Salesforce connection is retired. | | --- | ## What the HubSpot Salesforce integration syncs between the two platforms ![One HubSpot account and one Salesforce instance at the centre with seven things the integration syncs or shows: contacts and companies, deals, field mapping, activities, custom objects, inclusion lists and the Embed window.](https://www.finemediabw.com/hs-fs/hubfs/Blog/Technology%20and%20RevOps/Revenue%20Operations/Decision/HubSpot%20Salesforce%20Integration%20-%20Connect%20Them%20or%20Move%20Off%20One/hubspot-salesforce-integration-integration-sync-map-blog-1600x900.png?width=1600&height=900&name=hubspot-salesforce-integration-integration-sync-map-blog-1600x900.png) The integration connects one HubSpot account to one Salesforce instance, and it is the native sync between the two platforms. HubSpot's documentation is explicit that [you can connect only one Salesforce instance per HubSpot account](https://knowledge.hubspot.com/salesforce/install-the-hubspot-salesforce-integration), so a company with several Salesforce orgs needs a plan before it starts. Out of the box it covers the standard objects that make up the revenue record. HubSpot contacts and companies line up with Salesforce leads, contacts and accounts, and deals line up with opportunities. That way marketing and sales data describe the same people. HubSpot and Salesforce use different data structures, so a sync is a translation, not a copy. Contact sync is on by default, and you choose what else moves and in which direction. ### Contacts, accounts and deals follow your sync rules When you are syncing contacts between HubSpot and Salesforce, each mapped field has a rule that decides who wins. HubSpot's [field mapping guide](https://knowledge.hubspot.com/salesforce/map-hubspot-properties-to-salesforce-fields) lists four: prefer Salesforce unless blank, always use Salesforce, two-way, and don't sync. Field mapping is where most of the design work sits, so map Salesforce fields to HubSpot properties on purpose, custom fields included. There is a limit of 500 field mappings per object. Existing values in a newly created mapping do not sync retroactively, so history will not appear for a new custom field. The integration will also not move a HubSpot contact's lifecycle stage backwards. ### Activities and custom objects can ride along HubSpot's [activity sync guide](https://knowledge.hubspot.com/salesforce/sync-activities-and-tasks-between-hubspot-and-salesforce) describes a timeline sync that sends HubSpot events such as form submissions, email opens and meetings to Salesforce as tasks, and a separate two-way sync for tasks, sales emails, calls and meetings. Custom objects can sync too, but they must exist in HubSpot first and need at least one required field. Salesforce lookup fields on custom objects cannot be field-mapped, so that data travels through the association setting instead, as the [custom object sync page](https://knowledge.hubspot.com/salesforce/set-up-and-use-salesforce-custom-object-sync) explains. ### Inclusion lists decide which records cross over You rarely want every record in both systems. Inclusion lists, which HubSpot calls inclusion segments, define which HubSpot records are eligible to sync to Salesforce. Records outside the list do not sync, as the [inclusion list documentation](https://knowledge.hubspot.com/salesforce/create-a-salesforce-inclusion-list) states. Selective sync gives you the same control in the other direction for custom objects, tickets, companies and activities. A clean inclusion rule keeps cold marketing contacts out of the sales team's Salesforce views, whether they came from marketing campaigns or an old list, and is the cheapest way to avoid duplicate records. ### Sales can see HubSpot data without leaving Salesforce The HubSpot Embed window places an iframe inside Salesforce that shows a summary of the HubSpot interactions and activities a Salesforce record has, as [HubSpot's page layout guide](https://knowledge.hubspot.com/salesforce/add-the-hubspot-visualforce-window-to-your-salesforce-page-layouts) describes. Reps get customer interactions and activity tracking on the record they already open. Salesforce users need a HubSpot user account to see the window, so limit Salesforce access to the people who need it. Whoever installs it needs the Customize Application permission in Salesforce. HubSpot is also retiring its legacy Visualforce module and recommends uninstalling the old HubSpot integration package in Salesforce in favor of the Embed window. ### Native connector, third-party tools or a custom build HubSpot offers a built-in connector for Salesforce, and it is the usual starting point. Third-party connectors and a custom API build can give more control over data flows. They also add something else to own, monitor and pay for, so use them only when the native sync cannot express a rule you need. ### How often the sync runs The sync is not instant. HubSpot says it checks for new or updated information across the two accounts [approximately every 15 minutes](https://knowledge.hubspot.com/salesforce/salesforce-integration-sync-triggers). Triggers include a form submission, a changed property, a new lead, an ownership change and a lifecycle stage change. That interval suits reporting and most lead routing. It is a poor fit for any process that needs a rep to see a change within seconds. ## What a full migration to HubSpot changes instead A migration is a different project from an integration. You are not keeping two systems aligned. You are choosing one system of record and moving what the business needs into it. The integration is built for an ongoing relationship, and a migration ends that relationship. The work is moving business processes, not only rows. HubSpot makes the distinction explicit. [Smart Transfer is designed for a one-time migration](https://knowledge.hubspot.com/integrations/transfer-data-from-other-apps-using-hubspot-smart-transfer) of data from another app, and the transfer runs one way into HubSpot. Its steps are to audit your data, prepare your portal, sync your records, transfer the rest, and clean up empty properties. ### The two tools should never run together Smart Transfer and the Salesforce integration match records on different unique identifiers. HubSpot warns that using both at the same time creates duplicate records in HubSpot and in Salesforce. Pick the tool that fits the plan, and switch one off before you switch the other on. ### Getting your data out of Salesforce Salesforce supports a data export as a set of CSV files. Its [export documentation](https://help.salesforce.com/s/articleView?id=000383962&language=en_US&type=1) says each zip archive contains one or more CSV files. An export is only the start. What you cannot export as rows is the logic: validation rules, flows, approval steps and custom code. A migration is mostly the work of deciding which of those still earn their keep and rebuilding them as HubSpot workflows. ## HubSpot Salesforce integration vs full migration: how the two paths compare ![The connect path and the full migration path compared on data model, time to start, ongoing effort and main risk.](https://www.finemediabw.com/hs-fs/hubfs/Blog/Technology%20and%20RevOps/Revenue%20Operations/Decision/HubSpot%20Salesforce%20Integration%20-%20Connect%20Them%20or%20Move%20Off%20One/hubspot-salesforce-integration-connect-vs-migrate-side-by-side-blog-1600x900.png?width=1600&height=900&name=hubspot-salesforce-integration-connect-vs-migrate-side-by-side-blog-1600x900.png) The two paths differ less on features than on commitment. The integration lets two teams keep two tools. The migration removes the duplicate and asks everyone to adopt one set of definitions. This table compares them on the same criteria. | Criterion | Connect with the integration | Migrate fully to HubSpot | | --- | --- | --- | | Question it answers | How do we keep both systems in agreement? | Which one system should hold our revenue data? | | Data model | Two models mapped field by field | One model | | Time to first value | Fast once the connected user and mappings are set | Slower, because history and processes must move | | Ongoing effort | Sync health checks, mapping upkeep and sync error fixes | Normal HubSpot administration | | Main risk | Duplicate records and silent mapping drift | Lost logic and a stalled sales team | | Reporting | Two sources unless you pick one as master | One source for the whole funnel | | Reversibility | Easy to switch off | Hard to reverse once Salesforce is retired | ### Why the integration costs more over time than it first appears Every connected field is a promise that the two systems will agree, and a HubSpot integration is only as good as the definitions behind it. Each new custom property, picklist value or automation can break that promise. HubSpot's own error guide lists picklist mismatches, permission gaps, validation rules and formatting inconsistencies, such as a value that is too long, as causes of sync errors. Improper object mapping leaves fragmented or unusable data. Integration is also part of a wider problem. Salesforce's [2025 MuleSoft Connectivity Benchmark Report](https://www.salesforce.com/blog/mulesoft-connectivity-benchmark-2025/) found that the average enterprise manages 897 applications and only 29% are integrated. A CRM pair held together by mappings is one more connection to maintain. ## Which path fits your business: decision rules ![One question, which path fits your business, with three answers: connect them when each team has a reason to stay put, move to HubSpot when keeping both costs more than it returns, or settle who owns each record first.](https://www.finemediabw.com/hs-fs/hubfs/Blog/Technology%20and%20RevOps/Revenue%20Operations/Decision/HubSpot%20Salesforce%20Integration%20-%20Connect%20Them%20or%20Move%20Off%20One/hubspot-salesforce-integration-connect-or-migrate-decision-path-blog-1600x900.png?width=1600&height=900&name=hubspot-salesforce-integration-connect-or-migrate-decision-path-blog-1600x900.png) Pick by what your sales and marketing teams actually do, not by which logo sounds more serious. Five rules cover most situations, and they run from keep both to move on. ### Connect them when the sales team depends on Salesforce customization If your sales team lives in Salesforce and has built objects, approvals and reports around it, a forced move will cost adoption. Marketing can run campaigns, forms and marketing emails in HubSpot while the integration feeds contacts, lifecycle stages and activity to the people who sell. Teams that run Salesforce and HubSpot side by side do best when each has a clear job: marketing efforts in HubSpot, the sales process in Salesforce. ### Connect them while a migration is still being planned A migration takes weeks of preparation. Running the integration in the meantime keeps the marketing and sales teams working from shared contact records, and a Salesforce sandbox lets you test mappings before touching live data. ### Move to HubSpot when you maintain the integration more than you use it Saving time is the reason to connect two systems, so the test is simple. If one person spends the week clearing sync errors, resolving duplicate records and explaining why two reports disagree, the integration has become a job. That is the signal to price a migration. ### Move to HubSpot when only a small part of Salesforce is still used When most of your sales team works from contacts, deals, tasks and a pipeline view, the extra system buys little. One platform is cheaper to administer and easier to report from. ### Do not connect two systems to avoid a decision A HubSpot integration with Salesforce can hide a disagreement between teams about which system owns the customer. It cannot settle it. Decide who owns each record type first, then choose the path. ## What it takes to run the integration without sync errors If you connect the systems, the technical setup matters more than the connector. A few checks prevent most of the trouble teams run into in the first month, and your Salesforce admin should be in the room for all of them. ### Check the requirements before you install To connect HubSpot you need Account Access permissions in HubSpot, and to connect Salesforce you need an edition with API access, or Salesforce Professional. HubSpot's [installation guide](https://knowledge.hubspot.com/salesforce/install-the-hubspot-salesforce-integration) says the integration does not support Salesforce Group Edition. The Salesforce user who connects it must be a system administrator with permissions that include API Enabled. Check login restrictions too. If your Salesforce account uses login IP restrictions, HubSpot may not be able to connect, because HubSpot uses dynamic IP addresses that you cannot allowlist. ### Treat the integration user as a real role The connected user, also called the integration user, determines what HubSpot can do in Salesforce through the sync. Use a dedicated user that nobody deactivates, with the object and field permissions your mappings need. If you must change the integration user later, the new user needs permissions equal to or greater than the previous one. Review the integration settings after install and again whenever that user changes. A missing permission is one of the listed causes of sync errors. ### Read the Sync Health tab every week The Sync Health tab shows how many API calls you used in the last 24 hours and lists errors by type, including duplicates, permissions, picklists and property mappings. The same page lets you set how many Salesforce API calls are allocated to HubSpot, so base that limit on what Salesforce allows. Treat the sync settings as something you tune, not something you set once. ### Start with essential objects and fields Sync only the objects and fields your teams use at first, and set strict sync rules so one system cannot overwrite the other by accident. Add more once the first set is clean, and audit the integration regularly so the data stays relevant. ### Test in a sandbox before you go live HubSpot lets you connect to a Salesforce sandbox, so you can review sync behavior and validate configuration changes without touching live data. A sandbox environment is also the safe place to test form submissions, lead assignment and lifecycle stage changes first. ### Keep HubSpot workflows and Salesforce automation from fighting HubSpot workflows that update synced properties can collide with Salesforce flows that update the same fields. Write down who owns each field, and keep automation on one side of the sync wherever you can. ## What you gain when this is done properly Whether you connect or consolidate, the goal is one set of facts that marketing, sales and customer success all trust. For Salesforce and HubSpot users alike, that means fewer arguments about whose number is right. When the choice fits your business, the daily friction between systems drops and the handoffs between teams get an owner. ### Sales stops re-entering and second-guessing data Saving time starts here: sales reps see the form submissions, email activity and meetings that marketing created, as tasks on the records they already use. Better visibility into customer engagement makes outreach more relevant, and lead routing can assign new leads to reps by criteria you set. ### Marketing sees what happens to the leads it creates When lifecycle stages and opportunity data flow back to HubSpot, marketing can see which campaigns produce pipeline. Closed-loop reporting compares closed-won revenue against specific campaigns, and synchronized lifecycle stages give both teams the same definitions. ### Customer success starts with the full story A customer success team working from a connected or consolidated record inherits what was promised and who the buyers were. Onboarding starts faster, a consistent customer database means fewer outdated records, and workflow automation cuts administrative tasks. ## How Propello fits when the integration decision is stuck Most stalled decisions here come from unclear ownership, not from the connector. Teams discover that lifecycle stages, field definitions and lead handoffs mean different things on each side, which makes either path harder than it should be. Our post on [HubSpot integrations for the GTM stack](https://www.finemediabw.com/blog/hubspot-integrations-gtm-engineering-stack) covers the wider picture. Propello is a [HubSpot partner](https://www.finemediabw.com/about-us) that designs and builds connected go-to-market systems on HubSpot. If you want the connect-or-migrate decision made against your real data and definitions, an audit is the place to start. [Book a Propello GTM Audit](https://www.finemediabw.com/contact) ## Frequently asked questions How often does HubSpot sync with Salesforce? HubSpot checks for new or updated information across the two accounts approximately every 15 minutes and triggers a sync when needed. That is frequent enough for reporting and most lead routing, but it is not real time, so do not design a process that needs a rep to see a change within seconds. Is HubSpot replacing Salesforce? Not by default. The integration lets both systems run side by side, and many companies keep Salesforce for sales while marketing works in HubSpot. Others move fully to HubSpot once the extra system costs more than it returns. Which one applies depends on how deeply sales relies on Salesforce. Can you connect more than one Salesforce instance to HubSpot? No. HubSpot allows one Salesforce instance per HubSpot account. To connect several HubSpot accounts to one Salesforce instance, you set up and install the integration in each HubSpot account. Companies with several Salesforce orgs should decide which one is the system of record before they start. Can I migrate my data from Salesforce to HubSpot? Yes. Salesforce can export your data as CSV files, and HubSpot Smart Transfer moves data one way from other apps into HubSpot. Smart Transfer is designed for a one-time migration. Do not run it at the same time as the integration, or you will create duplicate records. Which CRM is better, Salesforce or HubSpot? Neither wins on every measure. Salesforce suits companies with deep sales customization and a dedicated administrator. HubSpot suits teams that want marketing, sales and service on one platform with less setup. The better choice is the one your teams will keep clean and use daily. ![Tumisang Bogwasi](https://app.hubspot.com/settings/avatar/77d7e2eaad8ff71b24463dcc39a31e9e) ### Written By: Tumisang Bogwasi Tumisang Bogwasi is the founder and CEO of Propello, a HubSpot partner that designs and builds connected go-to-market systems. [mailto:tumib@finemediabw.com](mailto:tumib@finemediabw.com) ## You May Also Like ### [![HubSpot Audit: What a Proper One Covers. Dark and slate type on a light grey ground, Propello.](https://www.finemediabw.com/hubfs/Blog/Technology%20and%20RevOps/Revenue%20Operations/Decision/HubSpot%20Audit%20-%20What%20a%20Proper%20One%20Covers/hubspot-audit-share-1200x630.png) *Oct 10, 2026, 11:45:36 AM | HubSpot* HubSpot Audit: What a Proper One Covers](https://www.finemediabw.com/blog/hubspot-audit) ### [![What Is HubSpot? A Plain Guide for Revenue Leaders. White and blue-grey type on a dark navy ground beside the HubSpot logo in white, Propello.](https://www.finemediabw.com/hubfs/Blog/Technology%20and%20RevOps/Refresh/What%20Is%20HubSpot%20-%20A%20Plain%20Guide%20for%20Revenue%20Leaders/what-is-hubspot-share-1200x630-v2.png) *Nov 20, 2022, 9:11:49 PM | HubSpot* What Is HubSpot? A Plain Guide for Revenue Leaders](https://www.finemediabw.com/blog/what-is-hubspot) ### [![HubSpot Operations Hub: What It Does for a Revenue Team. White and steel-blue type on a deep blue-grey ground, Propello.](https://www.finemediabw.com/hubfs/Blog/Technology%20and%20RevOps/Revenue%20Operations/Consideration/HubSpot%20Operations%20Hub%20-%20What%20It%20Does%20for%20a%20Revenue%20Team/hubspot-operations-hub-share-1200x630.png) *Oct 10, 2026, 11:44:28 AM | RevOps* HubSpot Operations Hub: What It Does for a Revenue Team](https://www.finemediabw.com/blog/hubspot-operations-hub) [Learn More](https://www.example.com) [![Fine\_Media\_logo\_Set\_HubSpot Website Logo Stacked White BG White-1](https://www.finemediabw.com/hubfs/Fine_Media_logo_Set_HubSpot%20Website%20Logo%20Stacked%20White%20BG%20White-1.svg "Fine_Media_logo_Set_HubSpot Website Logo Stacked White BG White-1")](https://www.finemediabw.com) We help you propel growth at every stage of the customer journey with inbound marketing and Hubspot. ![provider-horizontal-white](https://www.finemediabw.com/hubfs/provider-horizontal-white.svg "provider-horizontal-white") Blogs [What is Inbound Marketing](https://www.finemediabw.com/blog/what-is-inbound-marketing) [Why work with a HubSpot Agency](https://www.finemediabw.com/blog/why-work-with-hubspot-agency) [Benefits of a Website](https://www.finemediabw.com/blog/the-power-of-website-design-a-cornerstone-of-brand-identity) [Ultimate Guide to Closing more Deals](https://www.finemediabw.com/blog/how-to-close-more-deals-with-sales-enablement) [Why Every Business Needs Customer Success](https://www.finemediabw.com/blog/why-customer-success-is-important) Services   [Inbound Marketing](https://www.finemediabw.com/inbound-marketing) [Website Design](https://www.finemediabw.com/website-design-and-development) [Sales Enablement](https://www.finemediabw.com/sales-enablement) [Customer Success](https://www.finemediabw.com/customer-success) [HubSpot Services](https://www.finemediabw.com/hubspot-services) Quick Links   [Home](https://www.finemediabw.com/) Services [About us](https://www.finemediabw.com/about-us) [Contact](https://www.finemediabw.com/contact-us) © 2026 Fine Media (Pty) Ltd. All rights reserved. [Legal Notice](https://www.finemediabw.com/user-agreement) | [Privacy Policy](https://www.finemediabw.com/privacy-policy)  ```json { "@context" : "https://schema.org", "@type" : "BlogPosting", "author" : { "@type" : "Person", "name" : "Tumisang Bogwasi", "url" : "https://www.finemediabw.com/blog/author/tumisang-bogwasi" }, "datePublished" : "2026-10-10T09:45:45.000Z", "headline" : "HubSpot Salesforce Integration: Connect or Move Off One?", "image" : [ "https://www.finemediabw.com/hubfs/Blog/Technology%20and%20RevOps/Revenue%20Operations/Decision/HubSpot%20Salesforce%20Integration%20-%20Connect%20Them%20or%20Move%20Off%20One/hubspot-salesforce-integration-share-1200x630.png" ], "mainEntityOfPage" : { "@id" : "https://www.finemediabw.com/blog/hubspot-salesforce-integration", "@type" : "WebPage" }, "publisher" : { "@type" : "Organization", "logo" : { "@type" : "ImageObject", "url" : "https://www.finemediabw.com/hubfs/Fine_Media_logo_Set%20copy_HubSpot_Logo_Long_Stacked.svg" }, "name" : "Fine Media" } } ``` ```json { "@context" : "https://schema.org", "@type" : "FAQPage", "mainEntity" : [ { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "HubSpot checks for new or updated information across the two accounts approximately every 15 minutes and triggers a sync when needed. That is frequent enough for reporting and most lead routing, but it is not real time, so do not design a process that needs a rep to see a change within seconds." }, "name" : "How often does HubSpot sync with Salesforce?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Not by default. The integration lets both systems run side by side, and many companies keep Salesforce for sales while marketing works in HubSpot. Others move fully to HubSpot once the extra system costs more than it returns. Which one applies depends on how deeply sales relies on Salesforce." }, "name" : "Is HubSpot replacing Salesforce?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "No. HubSpot allows one Salesforce instance per HubSpot account. To connect several HubSpot accounts to one Salesforce instance, you set up and install the integration in each HubSpot account. Companies with several Salesforce orgs should decide which one is the system of record before they start." }, "name" : "Can you connect more than one Salesforce instance to HubSpot?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Yes. Salesforce can export your data as CSV files, and HubSpot Smart Transfer moves data one way from other apps into HubSpot. Smart Transfer is designed for a one-time migration. Do not run it at the same time as the integration, or you will create duplicate records." }, "name" : "Can I migrate my data from Salesforce to HubSpot?" }, { "@type" : "Question", "acceptedAnswer" : { "@type" : "Answer", "text" : "Neither wins on every measure. Salesforce suits companies with deep sales customization and a dedicated administrator. HubSpot suits teams that want marketing, sales and service on one platform with less setup. The better choice is the one your teams will keep clean and use daily." }, "name" : "Which CRM is better, Salesforce or HubSpot?" } ] } ```