Close to HubSpot
Lead-centric sales CRM with built-in calling, email and SMS. Contacts and opportunities sit under a Lead.
Close data can move into HubSpot, landing mainly in Sales Hub. 3 of 8 mapped objects move directly (Leads, Contacts and Opportunities); 4 items need manual work and 2 do not move. Plan roughly 1-2 weeks for a small move and 6-12 weeks for a large one.
Migration checklist for Close
Three phases, specific to this system. Tick steps off as you go.
Before
0 of 6 doneDuring
0 of 5 doneAfter
0 of 5 doneWhat will it take?
No price list: cost follows volume, custom objects and how much logic must be rebuilt. Answer four quick questions for a planning range.
The three scenarios
Small migration
Under 10k leads, a few custom fields
CSV import plus notes.
Mid migration
10k-100k leads with activity history
JSON export, scripted activity import, workflow rebuild.
Large migration
100k+ leads, millions of activities, recordings
Delta syncs, custom objects, reporting rebuild.
What moves the number
Timeline ranges are planning estimates, not a quote. A partner confirms scope after discovery.
Access, mapping and limits
Start with how data leaves Close: what you need to get in, what lands in HubSpot, and what will not.
REST (JSON), with an asynchronous Export API that returns CSV or JSON by email link
Choose your route
How will you move the data?
No native connector was found.
- You need: To confirm
- Permission: To confirm
Native imports often bring over only some data, so check coverage per object in the mapping below.
Export each object, clean it, then import it into HubSpot.
- Leads page > Export: Leads, Contacts or Opportunities as CSV or JSON, common or all fields
- JSON export or API for full activity history (emails, calls, SMS, notes); CSV omits activities
- REST list endpoints for leads, contacts, opportunities and activities, with pagination
- Download link is emailed and expires after 7 days; the file is GZIP compressed
- Pipelines, statuses and custom field definitions are readable via the API
Limits: To confirm
Migration and sync tools can move more than a plain import. Confirm which objects each one supports before you choose.
Best when volume is high, custom objects are many or automation is heavy. That is the Large scenario: 6-12 weeks, usually phased.
Talk to a partnerWhere each object lands
In Close
In HubSpot
Hover or tap anything on the left to see where it lands.
| Source object | In HubSpot | Moves | Notes |
|---|---|---|---|
| Leads | Companies | yes | A Lead is the account container, so it maps to a Company. Keep the Close lead ID as a custom property for joins. |
| Contacts | Contacts | yes | Export from the Leads page. Lead-level custom fields are excluded, so join on Lead ID. Close has a single name field and HubSpot needs first and last name split. |
| Opportunities | Deals | yes | Opportunities include Lead name and ID for association. Pipelines and stages must be built in HubSpot first. |
| Activities: notes, calls, emails, meetings | Notes, Calls, Emails, Meetings | partial | Full history requires JSON export or API, then a scripted or partner import. Call recordings need API URLs downloaded separately. |
| SMS activity | Notes | manual | HubSpot has no native SMS object, so logs would be stored as notes or custom data. This mapping is analyst judgment. |
| Tasks | Tasks | partial | Task export coverage was not confirmed in the sources. |
| Users / owners | Contacts, Companies, Deals (owner property) | manual | Users must be matched to HubSpot users before import. |
| Custom activities and custom fields | Custom objects | partial | The JSON export includes custom activities. Mapping to custom objects or properties is a design decision. |
What to expect
These are configuration objects. Rebuild as HubSpot workflows, sequences and lists; sequences are API-readable per one guide.
HubSpot deal stage dates are derived from movement inside HubSpot, so imported deals start fresh.
Not importable through the HubSpot import tool.
Close roles and reports do not map to HubSpot teams, permission sets and dashboards.
CSV drops activities and lead-level fields, so reconcile counts per Lead against HubSpot associations.
Close supports many phone labels while HubSpot has few; names need splitting.
Use JSON export or API and reconcile activity counts.
Export Leads and Contacts separately and join on Lead ID.
Store the original stage dates as custom properties.
Pull recording URLs via the API and download the files.
Download promptly and store the file securely.
Data governance and compliance
Decide what is allowed to move before anything is exported. Tick each gate once it is agreed.
How we researched this page
How much to trust each section, and where it comes from.
Export paths and object model are backed by Close's help centre and third-party guides. Auth, rate limits, and Close's own security and compliance details were not verified from vendor API docs. There is also no confirmed native Close-to-HubSpot import connector.
Sources
Related migrations
Frequently asked questions
How do I migrate Close to HubSpot?
1. Inventory Leads, Contacts, Opportunities, activity types and custom fields, including lead-level and contact-level. 2. Create an API key for a Close admin and test pulling GET /lead/ and a sample activity. 3. Design the Lead-to-Company and Contact mapping, including multiple contacts per lead. 4. Build HubSpot pipelines, deal stages and custom properties (Close lead ID, opportunity ID) first.
What data can move from Close to HubSpot?
These objects move directly: Leads, Contacts and Opportunities. Check the mapping table for partial and manual items.
What does not move from Close to HubSpot?
Workflows, sequences and Smart Views and Historical stage-change timestamps. Plan to rebuild or retire these.
How long does a Close to HubSpot migration take?
Small (Under 10k leads, a few custom fields): 1-2 weeks. Mid (10k-100k leads with activity history): 3-6 weeks. Large (100k+ leads, millions of activities, recordings): 6-12 weeks. These are planning estimates, not a quote.
What compliance issues apply when moving Close data?
Check: Call recordings may need recording-consent evidence, SMS consent (TCPA) records and Sector-specific data if the customer is in a regulated industry. Agree consent, retention and access rules before exporting.
Moving Close into HubSpot?
A network of 153+ tiered HubSpot partners and 1,800+ accounts of experience. Tell us what you are moving and which hub matters most.
Talk to a partner