Migration Reference
ActiveCampaign to HubSpot Migration
What actually transfers, what quietly does not, and what has to be rebuilt by hand.
We mapped ActiveCampaign against HubSpot feature by feature: 43 features, 7 synced objects, 7 documented traps and 37 items that have to be rebuilt. The whole map is on this page, ungated.
The PDF is the same reference, formatted for a procurement file.
Get The Reference And The Calculator
The full ActiveCampaign to HubSpot reference as a PDF, plus the Excel calculator we scope these migrations with: every one of the 43 features as a row, enter your counts, get hours.
Three files: the reference as a PDF, the same reference in Markdown for your AI tool, and the full Excel effort calculator.
ActiveCampaign to HubSpot is a moderate migration, typically 3-6 weeks. Of the 43 features we mapped, 31 carry across as they are and 11 land with something lost: the 37 items nothing moves for you is what will actually set your timeline, not the sync.
Migration Scorecard
- Migration complexity
- Moderate
- Typical timeline
- 3-6 weeks
- Recommended method
- HubSpot Smart Transfer handles the initial migration: contacts, lists and tag data together. Once that is done, Data Sync takes over for an ongoing, two-way sync of contacts, accounts and deals through whatever transition period you run. Automations, templates and marketing assets sit outside both tools and need a manual rebuild regardless.
- Native sync
- Data sync, two way
- Smart transfer
- Supported
- HubSpot subscription
- Data Sync is free for default fields. Custom field mappings step up to Data Hub Starter at $45/mo, and the advanced data quality tools sit a tier higher again, under Data Hub Professional.
Feature parity across 43 capabilities
- Maps directly: 31 (72%)
- Maps partially: 11 (26%)
- No equivalent: 1 (2%)
7
Objects synced natively
7
Limitations and traps
37
Manual rebuild items
4
Source editions covered
Where this comes from: Our own research corpus, verified 2026-08-01, behind every number on this page.
The Seven Objects That Sync Natively
What the connector moves for you, and which way each one flows.
Contacts
Two wayBecomes Contacts
Contact sync runs in both directions, with a property change on either platform propagating to the other in real time and email address serving as the match key throughout. Both default and custom fields map across, though a brand new or deleted contact only gets picked up on the roughly two-hourly check, not on that same real-time cycle.
Accounts
Two wayBecomes Companies
An ActiveCampaign Account becomes a HubSpot Company on sync, with association mapping keeping each contact linked to the right one. Custom field mappings on this object need a paid tier to switch on, not the free sync alone.
Deals
Two wayBecomes Deals
Deal sync runs both ways in real time: change the stage, the value or the owner on either platform and it shows up immediately on the other. None of that works, though, until pipeline stage mapping has actually been configured during setup.
Tags
Into HubSpotBecomes Contact Properties (multi-checkbox)
A tag can be mapped, one direction only, onto a HubSpot custom multi-checkbox property built for filtering and segmentation, since HubSpot has no native tag concept of its own: it works instead through properties and list membership. Nothing writes back the other way, so a change made to that property inside HubSpot never becomes a tag in ActiveCampaign.
Email Activity
Into HubSpotBecomes Contact Timeline Events
Email opens, clicks and automation entries flow one way only, from ActiveCampaign onto the HubSpot contact record's timeline, and none of it appears unless event sync has been switched on directly in the integration settings first.
Lists
Into HubSpotBecomes Lists
Lists and their membership only make the crossing once, through a one-time Smart Transfer run after the main sync: nothing about them stays live afterwards, so a list built in ActiveCampaign after that point never appears in HubSpot on its own.
Email templates
Into HubSpotBecomes Email templates
Email templates are one of the few assets that genuinely transfer rather than needing a manual rebuild, per HubSpot's Smart Transfer data sync object mappings (knowledge.hubspot.com/integrations/supported-apps-for-hubspot-smart-transfer, read 2026-07-31).
Seven Things the Sync Does Not Tell You
Each one is documented, and each one has ended a migration in a bad week.
Tags Require Custom Property Mapping
Years of segmentation built entirely on tags is the ActiveCampaign default, and HubSpot simply has no tag object to receive it: what survives the move is the ability to segment, not the container that held it, since each tag lands as a contact property value, a multi-checkbox option or list membership instead. The mapping only runs one way, ActiveCampaign to HubSpot, so a tag applied from the HubSpot side afterwards will not write back.
Workaround: Build a custom multi-checkbox property in HubSpot and map each ActiveCampaign tag onto it as its value, then rebuild the segmentation itself as active lists filtered against that one property. Whoever owns the tag list today should decide the mapping, since a tag applied loosely for years does not always deserve to survive into the new system unchanged.
Historical Activity Data Does Not Migrate Natively
Every open, click, page visit and automation entry sitting behind a contact in ActiveCampaign stays there: neither the native integration nor a CSV export carries activity detail across, so HubSpot's record of that contact effectively starts from zero on the day it lands.
Workaround: A third-party tool such as Skyvia or Outfunnel can pull the raw activity data out through the ActiveCampaign API and map it back onto the right contacts during import, which is the route to take if the detail genuinely matters. Where a summary is enough, store the engagement history as custom contact properties instead and skip the API work entirely.
New Contact Sync Delay
A field change on a contact who is already syncing reaches HubSpot in near real time, but a brand new contact, or one just removed, waits on a check that only runs roughly every two hours. On a fast-moving inbound lead, that gap is the difference between a same-day follow-up and one that quietly slips to tomorrow.
Workaround: The manual 'Sync now' button in the integration settings forces an immediate sync whenever that two-hour wait genuinely cannot be afforded.
Field Mapping Incompatibilities
A field can simply fail to sync, either because of an API limitation or because ActiveCampaign holds it as read-only, and a mandatory field on either platform with no equivalent on the other is enough on its own to fail the whole sync.
Workaround: Work through every field mapping conflict at setup, before the first real sync runs, and set a default value for any mandatory field that has no source data to draw on.
Automation Architecture Fundamentally Different
There is no direct transfer path from an ActiveCampaign automation to a HubSpot workflow: the two platforms are built on genuinely different automation architectures, with different triggers and different action types underneath.
Workaround: Document every ActiveCampaign automation in full first, triggers, conditions and actions all included, then redesign and rebuild each one natively in HubSpot rather than trying to import the logic directly. Do this documentation pass with whoever actually built the automations, since a years-old canvas is rarely written down anywhere else.
Lists Only Available via One-time Smart Transfer
Lists and tags cannot travel through the ongoing Data Sync at all: the only path either has into HubSpot is a one-time post-sync transfer through Smart Transfer, and once made, that transfer does not stay live.
Workaround: Run Smart Transfer for the initial list migration, then rebuild the equivalent logic as HubSpot active lists so segmentation keeps working going forward rather than freezing at the point of transfer.
Deal Pipeline Stage Mapping Requires Manual Configuration
Pipeline stages do not map across automatically at all, and the two platforms' pipeline architectures can differ significantly enough that a stage-for-stage match is not something to assume going in.
Workaround: Map every ActiveCampaign pipeline stage to its HubSpot equivalent during setup, and expect to either create new stages or consolidate a few together where the two structures genuinely do not line up one to one.
One ActiveCampaign Feature HubSpot Cannot Replace
No workaround closes these. Each one is a capability you would be giving up, so decide who in the business can live without it before you commit to a date.
Automation Map
HubSpot doesn't have a visual map of workflow interconnections. Custom documentation needed.
The 37 Items That Get Rebuilt by Hand
This is the list that separates a quote that holds from one that does not.
Data And Objects
Contact Segments
A saved filter rule over contacts and their engagement history: what ActiveCampaign calls a segment.
HubSpot: Active lists
Treat a segment as a rule to rebuild, not a list of members to export: bring across only the membership and the segment freezes on the day it lands, static from that point on.
Tag-based Organisation
The whole ActiveCampaign database is organised around tags rather than fields, which is the opposite of how HubSpot expects a contact record to be structured.
HubSpot: Contact properties and active lists
This is the single biggest design decision the whole migration turns on, and it usually needs the person who actually built the tag structure in the room, since a tag list assembled by hand over several years rarely has a system anyone else can read straight off it. A tag-centric database and a property-centric one are not the same shape underneath, so every tag needs its own decision: does it become a property value, a list, or nothing at all. Import every tag as its own property without making that call first, and the result is a HubSpot account with hundreds of properties and a database nobody can actually use.
Custom Field Structures
Every custom field built up over the years on contacts, accounts and deals.
HubSpot: Custom properties
Match the underlying data type as carefully as the field name: a date sitting in a text field looks fine on the way in and makes every downstream filter on it useless.
Suppression and Unsubscribe Lists
Everyone who has opted out or been actively suppressed from sending.
HubSpot: Unsubscribed contacts and the opt-out list
Bring this list across before the first HubSpot send goes out, never after: mailing a previously suppressed address is the one migration mistake that lands as a complaint every single time it happens.
Bounced Contact Lists
The list of addresses that have already hard bounced.
HubSpot: Non-marketable contacts
Import the list marked non-marketable, which keeps every one of those addresses both out of the marketing contact tier count and out of any future send.
Historical Engagement Data
The open-by-open, click-by-click history sitting behind every ActiveCampaign contact's reporting.
HubSpot: No equivalent import path
The only way to recover it at all is through the API with third-party tooling, and even then it lands as raw data rather than as timeline engagement HubSpot can act on. Decide whether that history is actually worth paying to recover before committing the budget to it.
Site and Event Tracking
The tracking script sitting on every page, plus the custom events feeding ActiveCampaign's behavioural triggers.
HubSpot: The HubSpot tracking code and behavioural events
Replace the script on every web property the business runs, not just the primary site. Custom events are wired directly into the application, so whoever actually owns the site needs a seat at this part of the plan rather than hearing about it afterwards.
Automation
Automation Workflows
What sits on the ActiveCampaign automation canvas, for a team that has kept it for years, is not a handful of workflows but the operational memory of how the business actually runs.
HubSpot: Workflows
None of it moves across, because the two automation engines disagree at the root: this is design time, not translation time, and on most ActiveCampaign migrations it is the single largest line in the whole plan. Set aside real time with whoever actually built the automations, since the logic they hold is very often something only that one person fully understands.
Email Sequences and Drip Campaigns
A series of emails that ActiveCampaign sends out on a fixed delay between each one.
HubSpot: Workflows with delay steps, or sequences
Work through each series individually and decide whether it belongs in marketing or in sales: HubSpot treats the two as separate tools with separate consent rules, so the classification is not a formality.
Conditional and Branching Logic
The if/then branching that sits inside an automation.
HubSpot: Workflow branching logic
A branch condition is exactly where the meaning of an automation tends to shift between platforms, so translate nothing on sight: walk every branch with whoever actually owns that campaign before rebuilding it.
Goal-based Automations
An automation that pulls a contact ahead in the flow the moment a set goal is reached.
HubSpot: Workflow goals and list-based enrolment
A goal in ActiveCampaign can reach in and pull a contact out of any point in a flow, and HubSpot has no equivalent mechanic: an automation built around several goals needs a genuine redesign, not a port.
Tag-based Automation Triggers
An automation that fires the moment a tag lands on a contact.
HubSpot: Property-based workflow enrolment
This one waits on the tag decision made earlier: nothing here can be rebuilt until every tag it depends on has already been mapped to a property.
Split Testing in Automations
The A/B split running inside an automation.
HubSpot: Workflow A/B testing
Rebuild the test itself rather than trying to import its results, since no historical winner carries across: write down whatever conclusion the old test already reached before cutover, or it is lost the moment the account closes.
SMS Automations
Any SMS step built into an automation, where the account actually used one.
HubSpot: HubSpot SMS or a marketplace SMS app
Consent records travel with the phone numbers themselves, so confirm which SMS route is actually in scope, HubSpot SMS or a marketplace app, before pricing the rebuild rather than after.
Lead Scoring Models
The scoring ActiveCampaign runs on both contacts and deals.
HubSpot: Score properties
HubSpot's scoring mechanics work differently underneath, so treat the old point values as a hypothesis worth testing rather than a specification to reproduce exactly.
Reporting
Campaign Performance Reports
The open, click and bounce numbers reported per individual send.
HubSpot: Marketing email analytics
None of the historical send data transfers, so pull a final export of it before the ActiveCampaign account is actually closed, not after.
Automation Performance Reports
The reporting that shows how contacts actually move through an automation.
HubSpot: Workflow analytics
This reporting starts from zero on day one, simply because the workflows generating it are new, so expect the first month of data to read quieter than the old ActiveCampaign baseline ever did.
Deal Pipeline Reports
Whatever sales reporting was built on top of ActiveCampaign's deals.
HubSpot: Deal reports
This reporting only works if the deal import behind it is clean, with every owner resolving to a real HubSpot user rather than an unmatched name.
Contact Engagement Reports
Reporting that tracks how a contact's engagement changes over time.
HubSpot: Contact and engagement reporting
This gets rebuilt against HubSpot's own metrics, which are simply not counted the same way ActiveCampaign counted them, so expect the new numbers to genuinely disagree with the old ones rather than treating any mismatch as an error.
Attribution Reporting
Attribution reporting: whatever credits revenue back to a specific marketing touchpoint.
HubSpot: Attribution reports
Attribution sits behind a specific HubSpot plan rather than coming with every tier, so confirm it is actually included in whichever subscription is being bought before promising it, and check the tier's feature list directly rather than assuming.
Custom Report Dashboards
Whatever dashboard layouts were saved and shared inside ActiveCampaign.
HubSpot: Dashboards
Build these only once the underlying reports already exist in HubSpot, not in parallel with them, or the dashboard is finished before the numbers behind it are trustworthy.
Sales And Marketing Config
Email Templates
Every branded email template built in ActiveCampaign's own editor.
HubSpot: Marketing email templates
Exported HTML carries the old editor's structure with it and renders noticeably differently once it lands in HubSpot, so rebuilding each template from the original brand assets is usually quicker than fighting the export into shape. Build an Arabic template as its own right-to-left layout rather than a translated copy of the English one, since a mirrored layout is usually the first thing a bilingual reader notices is wrong.
Landing Pages
Any page currently hosted on ActiveCampaign itself.
HubSpot: Landing pages
This is a page-by-page rebuild, worth building the Arabic pages as their own right-to-left layout from the start rather than mirroring the English one, and any URL still linked from an active ad or from printed material needs a redirect in place before the old page actually comes down.
Forms
Every embedded or hosted form that currently feeds contacts into ActiveCampaign.
HubSpot: Forms
Swap every single embed, across every web property, at the moment of cutover, on both the Arabic and English versions of the site where the two run separately: miss even one and it keeps quietly sending contacts into an ActiveCampaign account that nobody is watching any more.
Deal Pipelines and Stages
The sales pipelines ActiveCampaign was running.
HubSpot: Deal pipelines and stages
Build this before anything else on the list: deals, workflows and reports all sit downstream of it and have nothing correct to attach to until it exists.
Lead Scoring Rules
Every rule that currently adds or subtracts a point of score.
HubSpot: Score properties
These get redesigned rather than copied over, since the signals HubSpot has available to score against are not the same set ActiveCampaign was working from.
Conversations Automations
Whatever chat automation is currently running inside ActiveCampaign Conversations.
HubSpot: Chatflows
Swapping the chat widget itself is the easy part; the routing and availability logic sitting behind it is where the actual rebuild work is.
Sending Domain Authentication
The SPF, DKIM and DMARC records that currently authorise ActiveCampaign to send on the domain's behalf.
HubSpot: Connected email sending domain
This is a small task with one hard dependency: whoever actually controls the DNS. Start it early regardless, since waiting on a DNS change is one of the most common ways a go-live date slips.
Sending Domain Warm-up
The deliberate ramp in send volume that lets a new sending reputation build up cleanly.
HubSpot: A staged sending ramp
This costs calendar time far more than it costs effort, and it runs for several weeks regardless of how quickly the rest of the migration moves. Build that time into the plan from the outset, or the first full-volume send after go-live lands straight in spam.
Users And Permissions
User Accounts and Permission Groups
Every login, plus the groups that actually control what each one can access.
HubSpot: Users, teams and permission sets
Set these up before a single record is imported, so ownership resolves correctly on the way in rather than needing a clean-up pass afterwards.
Deal Owner Assignments
The record of exactly which user owns which deal.
HubSpot: Deal owner
Map every ActiveCampaign user to a HubSpot user before a single deal is imported: skip this step and every deal arrives unowned, which is how a sales report ends up reading empty for no reason anyone can immediately explain.
Integrations
Webhook Integrations
Any outbound webhook that an ActiveCampaign event currently fires.
HubSpot: Workflow webhook actions
Whatever sits on the receiving end still expects the old payload shape, so plan for work on both sides of the webhook rather than assuming a like-for-like swap on HubSpot's end alone.
E-commerce Integrations
The Deep Data connection running into Shopify, WooCommerce or a similar storefront.
HubSpot: App Marketplace commerce integrations
Deep Data pulls in order and product history in a shape the HubSpot connector may not scope the same way, so check what genuinely crosses rather than assuming it matches feature for feature.
Connected CRM
Whatever CRM was previously wired into ActiveCampaign alongside it.
HubSpot: HubSpot CRM itself
This integration tends to disappear rather than move, since HubSpot is now doing the CRM's job itself: worth flagging to the business as one fewer moving part rather than one more thing to rebuild.
Zapier and Third-party Automations
Any Zapier scenario or similar external automation that ActiveCampaign currently triggers.
HubSpot: Updated scenarios or native workflows
Every one of these needs editing on both ends, not just repointed at a new trigger, and some are genuinely better replaced with a native HubSpot workflow than carried forward at all.
Calendar and Scheduling Integrations
Whatever booking tool or calendar connection was wired into ActiveCampaign.
HubSpot: The meetings tool and calendar integration
This is a per-user rebuild, and every old booking link stops working the moment it happens, so track down and replace each one everywhere it was published rather than assuming a redirect will cover it.
Custom API Integrations
Any bespoke code written directly against the ActiveCampaign API.
HubSpot: HubSpot APIs
HubSpot's object model is different enough underneath that this gets rewritten, not ported, so scope the work from the actual code rather than from a summary of what it is supposed to do.
The Sequence
Sync First, Then Migrate
Order is the content here. These steps form a dependency chain, and running them out of sequence is a documented way this kind of migration fails.
- 1
Audit ActiveCampaign in Full
contacts, lists, tags, automations, deal pipelines, email templates, forms, landing pages and every integration, inventoried in one pass rather than assembled from memory partway through
- 2
Document Every Automation Properly
map each workflow's triggers, conditions, wait steps and actions with whoever actually built it, and sort what is still genuinely active and necessary from what has quietly gone obsolete
- 3
Export the Data Itself
contacts across every status, deals, automation reports, campaign performance figures and the engagement history behind all of it
- 4
Configure HubSpot Before a Single Record Lands
set up SPF, DKIM and DMARC on the sending domain, create the subscription types, configure the compliance settings, and build the deal pipelines
- 5
Create the HubSpot Properties
map every ActiveCampaign custom field and every tag onto a contact, company or deal property before the import begins, not after
- 6
Run Smart Transfer for the Initial Migration of Contacts, Lists and Tags, the One-time Transfer None of the Ongoing Sync Steps Below Will Repeat
Run Smart Transfer for the initial migration of contacts, lists and tags, the one-time transfer none of the ongoing sync steps below will repeat
- 7
Enable Data Sync
turn on ongoing bidirectional sync for contacts, accounts and deals to carry the two platforms through the transition period together
- 8
Import the Suppression Data
unsubscribed, bounced and complained contacts all need to land with non-marketable status attached, not as an afterthought once sending has already started
- 9
Rebuild the Automations
recreate each one as a HubSpot workflow, starting with whichever ones the revenue actually depends on rather than working through the list in the order it happens to sit
- 10
Rebuild the Templates and Assets
email templates, landing pages and forms all get recreated directly in HubSpot rather than imported
- 11
Configure Lead Scoring Fresh, Rebuilding the Old Models Inside HubSpot's Own Contact Scoring Rather Than Porting the Point Values Across
Configure lead scoring fresh, rebuilding the old models inside HubSpot's own contact scoring rather than porting the point values across
- 12
Warm up the Sending Domain Deliberately
start with small, already-engaged segments and ramp the volume by 10 to 20 percent a week across four to six weeks
- 13
Test the Whole Build Thoroughly
validate every workflow, form, deal pipeline rule and integration before a live audience ever sees it
- 14
Cut Over
switch off ActiveCampaign sending and automations at the same moment every HubSpot equivalent goes live, not before and not after
- 15
Keep Monitoring After Go-live
watch deliverability, workflow performance and data integrity for 30 to 60 days rather than treating cutover itself as the finish line
Typically 3-6 weeks end to end, depending on how much of the source configuration is actually in use.
Effort Estimator
How Big Is This Migration?
A handful of questions, no sign-up required. The ranges come from the research above: every feature we mapped carries an effort figure, and this totals the ones that apply to your instance.
Estimated Effort
Answer a couple of questions and an hours range appears here.
Built from our research on 43 ActiveCampaign features. It is a range, not a quote.
A planning range, not a quote. It is delivery effort only, with no project management line. What moves it most in practice is data quality.
What Goes Wrong Most Often
The failures that show up again and again, in roughly the order they bite.
A Tag-based Database and a Property-based One Are Not the Same Shape, So the Tag-to-property Mapping Needs Real Planning Before Migration Starts, Not a Decision Made Tag by Tag as the Import Runs
A tag-based database and a property-based one are not the same shape, so the tag-to-property mapping needs real planning before migration starts, not a decision made tag by tag as the import runs
Nothing About the Historical Activity, Opens, Clicks, Page Visits, Moves Natively
engagement history starts completely fresh in HubSpot unless it has been deliberately extracted through the API beforehand
An Automation Workflow Cannot Simply Be Copied Across; It Has to Be Redesigned for an Architecture That Works Differently Underneath, Ideally With the Same Person Who Built the Original Still Available to Explain What Each Branch Was Actually For, Since That Logic Rarely Exists Anywhere Else
An automation workflow cannot simply be copied across; it has to be redesigned for an architecture that works differently underneath, ideally with the same person who built the original still available to explain what each branch was actually for, since that logic rarely exists anywhere else
ActiveCampaign's Own CRM, Its Deals and Pipelines, Is Simpler Than What HubSpot Offers, Which Makes This Migration a Genuine Opportunity to Build Something More Sophisticated Rather Than Just a Like-for-like Swap, Provided the Extra Structure Is Actually Planned Rather Than Improvised
ActiveCampaign's own CRM, its deals and pipelines, is simpler than what HubSpot offers, which makes this migration a genuine opportunity to build something more sophisticated rather than just a like-for-like swap, provided the extra structure is actually planned rather than improvised
Skip the Suppression List Import, Unsubscribed and Bounced Contacts Both, and the Very First HubSpot Send to Any of Them Is a Compliance Violation, Not a Near Miss
Skip the suppression list import, unsubscribed and bounced contacts both, and the very first HubSpot send to any of them is a compliance violation, not a near miss
Every ActiveCampaign Form Embedded Anywhere Across the Website Estate Has to Be Replaced With a HubSpot Form, and a Partial Swap Leaves Some Traffic Still Arriving at an Account Nobody Is Checking
Every ActiveCampaign form embedded anywhere across the website estate has to be replaced with a HubSpot form, and a partial swap leaves some traffic still arriving at an account nobody is checking
Send to the Full List Before the New Domain Has Been Warmed up and the Damage to Sender Reputation Is Immediate, Not Something That Shows up Gradually
Send to the full list before the new domain has been warmed up and the damage to sender reputation is immediate, not something that shows up gradually
Where ActiveCampaign Was Also Sending Transactional Email, That Job May Need a Separate Solution Entirely, Since HubSpot's Own Transactional Email Sits Behind the Enterprise Tier Rather Than Coming Standard
Where ActiveCampaign was also sending transactional email, that job may need a separate solution entirely, since HubSpot's own transactional email sits behind the Enterprise tier rather than coming standard
Site Tracking Has to Be Reconfigured Deliberately
pull the ActiveCampaign tracking code and install HubSpot's in its place, across every web property the business runs, not just the flagship site
Whatever SMS Functionality ActiveCampaign Was Running Has No Direct HubSpot Equivalent Without Bringing in an Add-on, So Price That Add-on in From the Start If SMS Is Genuinely Part of the Current Workflow
Whatever SMS functionality ActiveCampaign was running has no direct HubSpot equivalent without bringing in an add-on, so price that add-on in from the start if SMS is genuinely part of the current workflow
Questions
ActiveCampaign To HubSpot, Answered
Yes. Data sync, two way, covering 7 objects. Smart transfer is supported. What it will not do is rebuild your configuration: that is the 37 items below.
Typically 3-6 weeks. Complexity is driven by automation and reporting depth, not by record count: the connector moves records, so a large database on its own will not extend the timeline.
Of 43 features we mapped, 31 (72%) carry across directly and 11 (26%) map partially, meaning something is lost or reshaped along the way. 1 has no HubSpot equivalent at any tier, worth raising before sign-off rather than after.
37 items have to be rebuilt by hand, and 7 documented limitations are not surfaced by the connector at all. Both lists are on this page, in full, for whoever is scoping the work.
Data Sync is free for default fields. Custom field mappings step up to Data Hub Starter at $45/mo, and the advanced data quality tools sit a tier higher again, under Data Hub Professional.
1: Automation Map. If your team depends on one of these, settle it before you sign rather than discovering it at cutover, when the alternative is a custom build.
Only in one direction. The sync is not bidirectional here, so running both systems means choosing a system of record up front and accepting drift in the other.
Ready to Get Started?
Plan Your Migration
Tell us which platform you are leaving, how much of it is custom, and when you need to be live in HubSpot. We will tell you what transfers directly, what needs rebuilding, and how long the move actually takes.