Agency Migration Guide
Close to HubSpot Migration
What actually transfers, what quietly does not, and what has to be rebuilt by hand.
We mapped Close against HubSpot feature by feature: 46 features, 6 synced objects, 11 documented traps and 38 items that have to be rebuilt. The whole map is on this page, ungated.
The PDF is the same reference, formatted to send to a client.
Get The Guide And The Calculator
The full Close to HubSpot reference as a branded PDF you can send straight to a client, plus the Excel calculator we scope these migrations with: every one of the 46 features as a row, enter your counts, get hours.
Three files: the guide as a PDF, the same guide unbranded in Markdown for your AI tool, and the full Excel effort calculator.
Close to HubSpot is a medium migration, typically 3-5 weeks. Of 46 features we mapped, 31 carry across as they are and 11 land with something lost. The work is not moving records: it is the 38 items nothing moves for you.
Migration Scorecard
- Migration complexity
- Medium
- Typical timeline
- 3-5 weeks
- Recommended method
- Sync then migrate
- Native sync
- Data sync, two way
- Smart transfer
- Not supported
- HubSpot subscription
- Free integration. Data Hub Starter or higher required for custom field mappings and editing default mappings.
Feature parity across 46 capabilities
- Maps directly: 31 (67%)
- Maps partially: 11 (24%)
- No equivalent: 4 (9%)
6
Objects synced natively
11
Limitations and traps
38
Manual rebuild items
3
Source editions covered
Where this comes from: Our own research corpus, verified 2026-08-01, behind every number on this page.
The Six Objects That Sync Natively
What the connector moves for you, and which way each one flows.
Leads (Organizations)
Two wayBecomes Companies
Close 'Leads' are organizational entities (equivalent to companies). Matched by company name. Lead Owner syncs via email address; if unavailable, uses Name field. Users must exist in both platforms for owner sync.
Contacts
Two wayBecomes Contacts
By default, HubSpot only syncs contacts with valid email addresses. Close uses a single full name field while HubSpot splits into First/Last Name - the first word becomes First Name, remainder becomes Last Name.
Opportunities
Two wayBecomes Deals
Deal sync requires accompanying contact/company sync to maintain associations.
Calls
Two wayBecomes Calls
Call activity sync is supported natively.
Emails
Two wayBecomes Emails
Email activity sync is supported natively.
Tasks
Two wayBecomes Tasks
Task sync is supported natively.
Eleven Things the Sync Does Not Tell You
Each one is documented, and each one has ended a migration in a bad week.
Notes Do Not Sync
Close Notes are not supported by the native HubSpot sync integration. Note content will not transfer between systems. UNRESOLVED SOURCE CONFLICT (2026-07-31). HubSpot's marketplace listing for close-data-sync lists Notes as a shared object syncing BOTH ways with 4 default field mappings, and Custom Objects as syncing INBOUND. Close's own current documentation states that Notes, Custom Objects and Custom Activities are not supported. Both sources are first-party and they cannot both be right. The corpus keeps the conservative position (treat these as manual work) because overstating effort is the safer error in a quote, but this must be settled empirically by configuring a sync before it is published or used to justify a large manual-migration line item.
Workaround: Export notes from Close via API and import to HubSpot via API as note engagements attached to the appropriate records.
SMS and Meeting Activities Do Not Sync
Activities data such as SMSes and meetings are not supported by the sync integration.
Workaround: Export SMS and meeting data from Close via API and import to HubSpot manually.
Custom Objects and Custom Activities Do Not Sync
Close Custom Objects and Custom Activities are not supported by the native sync integration. UNRESOLVED SOURCE CONFLICT (2026-07-31). HubSpot's marketplace listing for close-data-sync lists Notes as a shared object syncing BOTH ways with 4 default field mappings, and Custom Objects as syncing INBOUND. Close's own current documentation states that Notes, Custom Objects and Custom Activities are not supported. Both sources are first-party and they cannot both be right. The corpus keeps the conservative position (treat these as manual work) because overstating effort is the safer error in a quote, but this must be settled empirically by configuring a sync before it is published or used to justify a large manual-migration line item.
Workaround: Map Close custom objects to HubSpot custom objects (Enterprise) or standard objects with custom properties. Migrate via API or CSV.
Name Field Splitting Issues
HubSpot splits names into First Name and Last Name fields, while Close uses a single full name field. The system treats the first word of the full name as First Name and the remaining text as Last Name, which can cause issues with multi-word first names or single-word names.
Workaround: Review and correct name field mappings after initial sync. May need manual cleanup for records with unusual name formats.
Phone Number Label Mapping Is Limited
Close supports multiple phone labels per contact, but only numbers labeled 'Mobile' or 'Fax' sync to the corresponding HubSpot fields. Other phone labels may not map correctly. HubSpot only has three default phone properties.
Workaround: Standardize phone labels in Close before migration. Create additional custom phone properties in HubSpot if needed.
Address Field Mapping Requires Correct Identification
HubSpot will only map address fields correctly if the address field is correctly identified in Close using their default field names.
Workaround: Verify address fields in Close use default field identifiers before configuring sync.
Associations Only Sync When Both Object Types Are Actively Synced
Associated records will only be created if there is an active sync running for that object type. For example, if you have a Contact sync but no Company sync, the associated Company will not be kept in sync. A Contact in HubSpot cannot exist without an associated Lead in Close.
Workaround: Enable sync for all related object types (Leads/Companies, Contacts, and Opportunities/Deals) to maintain complete associations.
Only Primary Company Associations Sync
Only primary company associations transfer between systems. Secondary or additional company links do not sync.
Workaround: Manually recreate secondary company associations in the target system after migration.
Custom Field Mappings Require Data Hub Starter
Default field mappings can be disabled or edited only with Data Hub Starter or higher. Custom field mappings also require this subscription.
Workaround: Subscribe to Data Hub Starter for custom mapping capability.
Some Field Types Are One-way Only
Multiple checkbox and calculation/score fields sync one-way only (from HubSpot to Close as text). Two-way sync is supported for Number, Date picker, Datetime, Single checkbox, and most Dropdown/Radio/Owner fields.
Workaround: Accept one-way sync for these field types or maintain dual data entry for critical fields.
Email Address Required for Contact Matching
By default, HubSpot will only sync contacts that have a valid email address. Contacts without email will not match or sync.
Workaround: Ensure all contacts have valid email addresses before syncing. Import contacts without emails via CSV separately.
Four Close Features HubSpot Cannot Replace
Not a workaround away. If a client depends on one of these, it belongs in the conversation before the contract.
Predictive Dialer
No native predictive dialer in HubSpot at any tier. Available through specialized providers (Orum, ConnectAndSell). Compliance considerations (TCPA) apply.
Voicemail Drop
No native voicemail drop in HubSpot. Available through third-party dialers (Kixie, PhoneBurner).
Call Forwarding & Transfer
Not available in HubSpot's basic calling. Third-party telephony providers handle call forwarding and transfer.
Global Calling & Local Presence
HubSpot's built-in calling has limited country support. Global calling with local presence requires Aircall, RingCentral, or similar.
The 38 Items That Get Rebuilt by Hand
This is the list that separates a quote that holds from one that does not.
Data And Objects
Notes (not Supported by Native Sync)
SMS Messages and History
Meeting Records
Custom Objects and Custom Activities
File Attachments on Records
Secondary Company Associations
Contacts Without Email Addresses
Smart Views (Close's Saved Filter Views)
Automation
Close Workflows (automated Action Sequences)
Email Sequences and Cadences
Auto-assignment Rules and Round-robin Logic
Smart Views With Automated Actions
Pipeline Trigger Automations
Follow-up Reminders and Task Automations
Reporting
Sales Leaderboard Configurations
Activity Reports (call, Email, SMS Metrics)
Pipeline Reports and Forecasting
Custom Report Configurations
Goal Tracking Dashboards
Revenue Reports
Sales And Marketing Config
Pipeline Stages and Configuration
Email Templates and Snippets
Call Scripts and Dispositions
Smart Views and Saved Filters
Lead Scoring/qualification Criteria
Power Dialer Configurations
Predictive Dialer Settings
SMS Templates
Users And Permissions
User Roles and Permissions
Team/group Configurations
Visibility Settings
API Key and Webhook Configurations
Integrations
Close Native Integrations (Zapier, Slack, Etc.)
Telephony/VoIP Configurations (built-in Calling)
Email Provider Connections
Calendar Sync Configurations
Third-party App Connections
Webhook Configurations
The Sequence
Sync First, Then Migrate
Order is the content here. These are a dependency chain, and running them out of order is a documented way these migrations fail.
- 1
Audit Close CRM
catalog all fields, pipelines, Smart Views, workflows, sequences, and integrations
- 2
Clean Data
deduplicate leads/contacts, verify email addresses, standardize phone labels and address fields
- 3
Set up HubSpot
create custom properties, configure pipelines, map deal stages
- 4
Install Close Data Sync App From HubSpot Marketplace
Install Close Data Sync app from HubSpot Marketplace
- 5
Enable Sync for All Three Object Types
Leads (Companies), Contacts, and Opportunities (Deals)
- 6
Enable Call, Email, and Task Sync
Enable Call, Email, and Task sync
- 7
Configure Field Mappings (Data Hub Starter for Custom Mappings)
Configure field mappings (Data Hub Starter for custom mappings)
- 8
Run Initial Sync and Verify Data Accuracy, Especially Name Splitting and Phone Mappings
Run initial sync and verify data accuracy, especially name splitting and phone mappings
- 9
Migrate Notes, SMS History, and Custom Objects via Close API Export and HubSpot API Import
Migrate Notes, SMS history, and Custom Objects via Close API export and HubSpot API import
- 10
Rebuild Email Sequences, Workflows, and Automation in HubSpot
Rebuild email sequences, workflows, and automation in HubSpot
- 11
Recreate Reports, Dashboards, and Smart Views as HubSpot Saved Views/reports
Recreate reports, dashboards, and Smart Views as HubSpot saved views/reports
- 12
Reconfigure Telephony (Close Built-in Calling to HubSpot Calling or Third-party)
Reconfigure telephony (Close built-in calling to HubSpot calling or third-party)
- 13
Train Team on HubSpot, Validate All Data, Then Cut Over
Train team on HubSpot, validate all data, then cut over
Typically 3-5 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 email required. The ranges come from the research above: every feature we mapped carries an effort figure, and this adds up the ones that apply to you.
Estimated Effort
Answer a couple of questions and an hours range appears here.
Built from our research on 46 Close features. It is a range, not a quote.
A planning range, not a quote. It is delivery effort only, with no project management line and no agency markup, so add your own. 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.
Close's Full Name Field Splits Into First/Last Name in HubSpot - Verify Correct Splitting
Close's full name field splits into First/Last Name in HubSpot - verify correct splitting
Phone Labels Beyond Mobile/Fax May Not Map Correctly to HubSpot's Limited Phone Fields
Phone labels beyond Mobile/Fax may not map correctly to HubSpot's limited phone fields
Must Enable Sync for All Related Object Types or Associations Will Break
Must enable sync for all related object types or associations will break
Only Primary Company Associations Sync - Secondary Links Are Lost
Only primary company associations sync - secondary links are lost
Notes Are a Major Gap - They Must Be Migrated Separately via API
Notes are a major gap - they must be migrated separately via API
Close's Built-in Calling Is Only Partly Replaceable
task queues cover sequential call-through, but there is no automatic dialling and no predictive dialer at any tier, so high-volume outbound teams need a third-party dialer.
SMS Data and Templates Do Not Sync and Have Limited HubSpot Equivalent
SMS data and templates do not sync and have limited HubSpot equivalent
Custom Objects and Custom Activities Require Enterprise HubSpot and Separate Migration
Custom Objects and Custom Activities require Enterprise HubSpot and separate migration
Close Smart Views Need to Be Recreated as HubSpot Saved Views/filters
Close Smart Views need to be recreated as HubSpot saved views/filters
Questions
Close To HubSpot, Answered
Yes. Data sync, two way, covering 6 objects. What it does not do is rebuild configuration: that is the 38 items below.
Typically 3-5 weeks. Complexity is driven by automation and reporting depth, not by record count: the connector moves records, so a large database is not by itself a long project.
Of 46 features we mapped, 31 (67%) carry across directly and 11 (24%) map partially, meaning something is lost or reshaped. 4 have no HubSpot equivalent at any tier.
38 items have to be rebuilt by hand, and 11 documented limitations are not surfaced by the connector at all. The full list of both is on this page.
Free integration. Data Hub Starter or higher required for custom field mappings and editing default mappings.
4: Predictive Dialer, Voicemail Drop, Call Forwarding & Transfer, Global Calling & Local Presence. If a client depends on one, it belongs in the conversation before the contract.
Only in one direction. The sync is not bidirectional here, so a parallel period means picking a system of record and accepting drift in the other.
Ready to get started?
Let's do something great together.
Augment your agency's marketing team's bench with our end-to-end inbound and digital solutions and find out why we're "The HubSpot Agency for HubSpot Agencies."
Fill out this form, and someone from our Solutions team will be in touch with you soon!