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
Free-text notes logged against Close leads and contacts.
HubSpot: Notes on the record timeline
Outside the scope of the native sync, so this is an API extraction and a second import pass after the records land.
SMS Messages and History
Text conversations held inside Close, which has SMS built in.
HubSpot: A marketplace SMS app, with history as notes
Close treats SMS as a first-class channel and HubSpot does not. Decide where SMS lives after the migration before scoping the history, because the answer changes whether the history is even useful.
Meeting Records
Logged meetings and their outcomes.
HubSpot: Meetings on the timeline
Extracted through the API. Reconnecting each user's calendar recovers upcoming meetings more cheaply than importing them.
Custom Objects and Custom Activities
Close's bespoke record types and activity types.
HubSpot: Custom objects and custom activity types
Confirm custom objects are available on the plan being bought before promising the mapping. Where they are not, these collapse into properties, which is a data-model conversation rather than a build task.
File Attachments
Documents attached to Close records.
HubSpot: Attachments on records
Pulled through the API and re-associated after the records land, so a second pass rather than part of the main import.
Secondary Company Associations
Additional company links on a contact beyond the primary one.
HubSpot: Secondary associations with labels
Association labels are a plan-dependent feature, so confirm availability before designing around them. Otherwise only the primary association survives.
Contacts Without Email Addresses
Records held in Close with no email, common where the team works by phone.
HubSpot: Contacts, imported by another key
The native sync skips these silently. Count them before the migration: on a phone-led team it can be a large share of the database.
Smart Views
Close's saved filter views, which the sales team works from all day.
HubSpot: Saved views and active lists
Rebuild the ones in daily use before go-live. This is the single thing a Close team notices missing first.
Automation
Close Workflows
Automated action sequences triggered by record changes.
HubSpot: Workflows
Rebuilt rule by rule. Pipelines and properties have to exist first or the enrolment criteria have nothing to point at.
Email Sequences and Cadences
Multi-touch outbound sequences run by reps.
HubSpot: Sequences
Sequence enrolment is per rep and per mailbox in HubSpot. Sending limits differ from Close, which matters for a high-volume outbound team.
Auto-assignment and Round-robin Rules
Rules distributing new leads across reps.
HubSpot: Workflow rotation actions
Users and teams must exist first. Test with real records, because round-robin that looks even in configuration often is not.
Smart Views With Automated Actions
Saved views that also trigger actions on the records in them.
HubSpot: Active lists plus workflows
One Close object becomes two in HubSpot: a list for the membership and a workflow for the action. Splitting them correctly is the work.
Pipeline Trigger Automations
Actions fired when an opportunity changes stage.
HubSpot: Deal stage workflow enrolment
Stages have to be built before the workflows.
Follow-up Reminders and Task Automation
Automatic task and reminder creation after an activity.
HubSpot: Workflow task actions
Rebuild the trigger as well as the task. Due-date offsets are the detail that gets lost.
Reporting
Sales Leaderboards
Ranked team performance views used to drive activity.
HubSpot: Custom reports and dashboards
Rebuilt as reports. There is no leaderboard object, so the competitive framing has to be recreated in how the dashboard is arranged.
Activity Reports
Call, email and SMS volume reporting per rep.
HubSpot: Activity reports
SMS volume will not be reportable unless SMS lands somewhere that logs to the timeline, which follows from the SMS decision above.
Pipeline Reports and Forecasting
Forward-looking pipeline and forecast reporting.
HubSpot: Deal reports and forecasting
Forecasting is a configuration job before it is a reporting one: amount, close date and stage probability all have to be set deliberately.
Custom Report Configurations
Saved report definitions used for recurring reporting.
HubSpot: Custom reports
Rebuild from the question each answers rather than reproducing the layout.
Goal Tracking Dashboards
Progress-against-target views for reps and the team.
HubSpot: Goals and dashboards
Goals are configured per user, so this is a repeated task across the team rather than one setup.
Revenue Reports
Closed revenue reporting over the pipeline.
HubSpot: Deal reports
Depends on deal amount and close date importing cleanly. Fix the import before rebuilding the report.
Sales And Marketing Config
Pipeline Stages and Configuration
Close's opportunity pipelines and their stages.
HubSpot: Deal pipelines and stages
Build first. Deals, workflows and reports all depend on it.
Email Templates and Snippets
Reusable message templates used by reps.
HubSpot: Email templates and snippets
Rebuilt by hand. Personalisation tokens have different names and will not carry.
Call Scripts and Dispositions
Scripts reps read from and the outcome codes they log.
HubSpot: Playbooks and call outcome properties
Confirm playbooks are on the plan being bought. Dispositions map to call outcomes, and that list should be agreed before reps start logging.
Smart Views and Saved Filters
The saved filters the team works from.
HubSpot: Saved views and active lists
Rebuild the daily ones first and let the rest go.
Lead Scoring and Qualification Criteria
How Close ranks and qualifies inbound leads.
HubSpot: Score properties
Built from scratch. The old weights are a starting hypothesis.
Power Dialer Configuration
Close's sequential dialling setup.
HubSpot: A marketplace dialler
HubSpot calling does not include a power dialler. For an outbound team this is a product purchase, and it should be in the conversation before the contract rather than after.
Predictive Dialer Settings
Close's predictive dialling configuration.
HubSpot: A marketplace dialler
Same conversation as the power dialler, and the more expensive half. Scope them together.
SMS Templates
Saved text message templates.
HubSpot: Templates in whichever SMS app is chosen
Follows the SMS decision. Until that is made this cannot be scoped.
Users And Permissions
User Roles and Permissions
Logins and their access levels.
HubSpot: Users and permission sets
Created before the import so record ownership resolves on the way in.
Team and Group Configuration
How reps are grouped.
HubSpot: Teams
Map intent rather than structure.
Visibility Settings
Rules for who can see whose records.
HubSpot: Record access settings
HubSpot partitions differently. Confirm what genuinely needs hiding before reproducing old restrictions.
API Keys and Webhook Configuration
Credentials and endpoints used by code talking to Close.
HubSpot: Private app tokens and workflow webhook actions
Inventory every consumer of an old key before the account closes, not after.
Integrations
Native Integrations
Close's built-in connections such as Zapier and Slack.
HubSpot: App Marketplace integrations and updated Zapier scenarios
Zapier scenarios need editing on both sides, since triggers and field names both change.
Telephony Configuration
Close's built-in calling, numbers and recording setup.
HubSpot: HubSpot calling or a marketplace provider
Numbers have to be ported or replaced, which has a lead time measured in weeks. Start this before the rest of the migration, not with it.
Email Provider Connection
The mailbox connection that logs conversations.
HubSpot: Connected inbox
Per user, not once for the account. Connect before cutover so logging is continuous.
Calendar Sync
Google or Microsoft calendar connection.
HubSpot: Calendar integration and the meetings tool
Per user again. A missed user stops logging meetings silently.
Third-party App Connections
Other tools joined to Close.
HubSpot: App Marketplace integrations
Reconnected individually, checking field mapping on each.
Webhook Configurations
Outbound webhooks fired by Close events.
HubSpot: Workflow webhook actions
The receiving endpoint expects Close's payload shape, so both ends usually need work.
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!