---
title: "Close to HubSpot Migration: Field Mapping & Rollback"
description: "Migrate Close to HubSpot with FlitStack AI: field-level mapping, a sample run you approve, full history and one-click rollback."
url: "https://flitstack.ai/migrations/crm/close/to/hubspot"
---

# Close to HubSpot migration

Moving from Close CRM to HubSpot keeps your sales history intact while unlocking HubSpot's marketing automation, multi-hub ecosystem, and enterprise-tier reporting. FlitStack AI maps every Close lead, contact, opportunity, custom activity, and custom field — preserving original create dates, stage-transition timestamps, and owner email matches so your HubSpot account picks up exactly where Close left off.

Short answer

FlitStack AI migrates contacts, companies, deals, deal pipelines and engagements from Close to HubSpot, with their history and the associations between records. Every field is mapped and validated, a sample run is checked with you before the full migration, and the whole move can be rolled back in one click. Typical timeline: 48–72 hours for under 25,000 records.

![](https://flitstack.ai/images/authors/aditya-kumar.webp)By [Aditya Kumar](https://flitstack.ai/about/aditya-kumar) Updated November 5, 2026

[Get a quote ](https://flitstack.ai/contact) [See the field mapping →](https://flitstack.ai/migrations/crm/close/to/hubspot#field-mapping)

![](https://flitstack.ai/images/illustrations/pair-stage.webp)

Source Close ![](https://flitstack.ai/platforms-trim/close.webp)

Destination HubSpot ![](https://flitstack.ai/platforms-trim/hubspot.webp)

Contact Company Deal Deal Pipeline Engagement

Mapped field by field · sample run · one-click rollback

## What moves from Close to HubSpot?

Close CRM and HubSpot CRM take structurally different approaches to the same sales record.

Read the full summary

Close collapses Lead and Contact into a single Lead object with a contact\_name field and uses a separate Opportunity object for deal tracking. HubSpot separates Contacts and Companies as distinct objects, tracks lifecycle stage on the contact record, and uses Deals (with associated Deal Pipelines and Stages) for opportunity management. Close also supports Custom Activities — named activity types defined by the user — which have no direct HubSpot equivalent and must be mapped to either custom HubSpot objects or Deal property fields depending on the activity's purpose. Close's multi-pipeline architecture maps to HubSpot's Deal Pipeline model, where each Close pipeline becomes a separate HubSpot Deal Pipeline with its own stage configuration. Custom fields on Close's Lead, Contact, and Opportunity objects migrate as HubSpot custom properties — text, number, date, picklist, and Boolean types are supported natively; multi-select picklist types require a custom-field configuration step in HubSpot before import. FlitStack's migration engine uses Close's API export endpoints and HubSpot's native import API to transfer records in dependency order: Companies first, then Contacts, then Deals with their stage history, then activity records. The delta-pickup window (24–48 hours) captures any records modified in Close during the cutover window so HubSpot reflects the final source state at go-live. Workflows, sequences, email templates, and calling/SMS configurations are not migrated — those are platform-native logic that must be rebuilt in HubSpot's automation tools.

direct

### Lead → Contact

Close Lead is the primary person record.

How it maps

It maps to HubSpot Contact. The contact's name fields (first\_name, last\_name) from Close are split into HubSpot's structured firstname and lastname fields. Any contact records in Close that represent existing customers route to HubSpot Contact with lifecycle\_stage set to 'customer' during migration.

direct

### Contact → Contact

Close also supports a secondary Contact object on a Lead.

How it maps

These map to HubSpot Contact directly. Each Close contact record receives the same HubSpot Contact field mapping as the parent Lead record. Multiple Close contacts on the same Lead create multiple HubSpot Contact records, each linked to the primary HubSpot Company.

direct

### Organization → Company

Close Organization maps to HubSpot Company.

How it maps

Organization name maps to Company name. Domain is mapped to Website. Industry, employee count, and address fields map to their HubSpot equivalents. Close's Organization hierarchy (parent/child) maps to HubSpot's associated company relationships. Organizations without a domain receive a placeholder website entry.

direct

### Opportunity → Deal

Close Opportunity maps directly to HubSpot Deal.

How it maps

Deal name, amount, expected\_close\_date, probability, and stage\_name all map to HubSpot Deal fields. The pipeline association in Close is preserved as a Deal Pipeline assignment in HubSpot. Each Close Opportunity is associated with a Contact and an Organization, both of which are resolved to their HubSpot equivalents before the Deal is written.

direct

### Pipeline → Deal Pipeline

Close Pipeline maps 1:1 to a HubSpot Deal Pipeline.

How it maps

Each pipeline's stage names are mapped to HubSpot Deal Stages within that pipeline. Probability values per stage are preserved as HubSpot stage metadata. If Close has multiple pipelines, each becomes a separate HubSpot Deal Pipeline — the migration plan includes pipeline creation in HubSpot before any Deal records are written.

transformed

### Activity (Call) → Engagement (Call logged as Note / Task)

Close's built-in call records migrate to HubSpot as logged activities.

How it maps

Call duration, outcome (answered, voicemail, no answer), and caller ID are preserved as properties on the engagement record. Call notes from Close map to a HubSpot Engagement Note. The activity is associated to the correct HubSpot Contact by email match.

******What moves 15 objects

Close HubSpot

- Lead Contact 1:1
- Contact Contact 1:1
- Organization Company 1:1
- Opportunity Deal 1:1
- Pipeline Deal Pipeline 1:1
- Activity Engagement transformed

\+ 9 more in the mapping below

## How Close and HubSpot differ

The differences that decide how each record is mapped. These are what a CSV export and a native importer don't resolve for you.

| Dimension                 | Close                                                                                                                                                                     | HubSpot                                                                                                                                                                                             |
| ------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Primary contact model     | Close uses a single Lead object for both raw leads and contacts; contact\_name is a composite text field, not a structured name object.                                   | HubSpot splits contacts into a structured Contact object with firstname, lastname, email, phone, and company association fields.                                                                    |
| Opportunity / deal object | Close Opportunity object tracks deal name, amount, stage, probability, expected\_close\_date, and is linked to a pipeline.                                                | HubSpot Deal object tracks deal name, amount, pipeline, stage, and close date. Deals are associated to a primary Contact and optionally a Company.                                                  |
| Pipeline model            | Close supports multiple named pipelines, each with its own stage statuses. A deal belongs to one pipeline.                                                                | HubSpot Deal Pipelines are first-class objects; each pipeline holds multiple Stages. A deal belongs to one pipeline. Pipelines can be assigned per deal type.                                       |
| Custom activity model     | Close Custom Activities are user-defined activity types (e.g., 'Demo Request', 'Proposal Sent') with their own custom fields and can be logged against a Lead or Contact. | HubSpot has no direct Custom Activities equivalent. Custom activity data must map to custom Deal properties, custom objects, or Engagement History entries depending on the activity type.          |
| Communication features    | Close includes built-in calling, SMS (US/CA/GB/AU), and email sequencing natively. These are platform-native features tied to Close's telephony stack.                    | HubSpot Sales Hub calling and SMS are paid add-ons. Sequences exist in HubSpot Sales but require configuration. Communication history migrates as logged activities, not as native calling records. |
| Workflow / automation     | Close Workflows (Growth and Scale plans only) automate outreach, task creation, and lead routing based on triggers. Workflows are plan-gated at $99/user/month minimum.   | HubSpot Workflows are a separate product tier within Sales Hub and Operations Hub. Any Close Workflow must be rebuilt manually in HubSpot — no migration path exists for automation logic.          |

## Close to HubSpot field mapping

The 30 most-used fields of 55 mapped for this pair. Custom fields are added from your own schema during scoping. [Download the full mapping (CSV) ↓](https://flitstack.ai/migrations/crm/close/to/hubspot.csv) or open it in the [field mapping template](https://flitstack.ai/tools/field-mapping-template).

******Field mapping 5 shown

Close HubSpot

1. `first_name` Lead `firstname` Contact
2. `last_name` Lead `lastname` Contact
3. `email` Lead `email` Contact
4. `phone` Lead `phone` Contact
5. `phone_number` Lead `phone` Contact

| Close field                        | HubSpot field                 | Mapping                 | Note                                                                                                                                                |
| ---------------------------------- | ----------------------------- | ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Lead.first_name`                  | `Contact.firstname`           | direct                  |                                                                                                                                                     |
| `Lead.last_name`                   | `Contact.lastname`            | direct                  |                                                                                                                                                     |
| `Lead.email`                       | `Contact.email`               | direct                  |                                                                                                                                                     |
| `Lead.phone`                       | `Contact.phone`               | direct                  |                                                                                                                                                     |
| `Lead.phone_number`                | `Contact.phone`               | direct                  |                                                                                                                                                     |
| `Lead.phone_home`                  | `Contact.phone`               | direct                  |                                                                                                                                                     |
| `Lead.phone_mobile`                | `Contact.mobilephone`         | direct                  |                                                                                                                                                     |
| `Lead.title`                       | `Contact.jobtitle`            | direct                  |                                                                                                                                                     |
| `Lead.organization_id`             | `Contact.associatedcompanyid` | transformed             | Resolved via Company lookup after Organization records are migrated to HubSpot Companies.                                                           |
| `Lead.status`                      | `Contact.hs_lead_status`      | value\_mapping          | Close status values (Active, Lost, Dead) map to HubSpot lead\_status picklist. Custom status values require option-level mapping.                   |
| `Lead.date_created`                | `Contact.createdate`          | direct                  |                                                                                                                                                     |
| `Lead.updated_at`                  | `Contact.notes_last_updated`  | direct                  |                                                                                                                                                     |
| `Lead.address.street`              | `Contact.address`             | direct                  |                                                                                                                                                     |
| `Lead.address.city`                | `Contact.city`                | direct                  |                                                                                                                                                     |
| `Lead.address.state`               | `Contact.state`               | direct                  |                                                                                                                                                     |
| `Lead.address.postal_code`         | `Contact.zip`                 | direct                  |                                                                                                                                                     |
| `Lead.address.country`             | `Contact.country`             | direct                  |                                                                                                                                                     |
| `Lead.description`                 | `Contact.notes_last_updated`  | direct                  |                                                                                                                                                     |
| `Lead.custom.cf_lead_score`        | `Contact.hubspot_lead_score`  | custom\_field\_required | Custom field created in HubSpot as a Number property. Preserves Close's lead scoring value for reporting continuity.                                |
| `Lead.custom.cf_source`            | `Contact.hs_analytics_source` | custom\_field\_required | Custom text field in HubSpot capturing the original lead source from Close.                                                                         |
| `Organization.name`                | `Company.name`                | direct                  |                                                                                                                                                     |
| `Organization.url`                 | `Company.website`             | direct                  |                                                                                                                                                     |
| `Organization.industry`            | `Company.industry`            | value\_mapping          | Industry picklist values mapped value-by-value. Close uses a shorter industry list; unmapped values are stored as text in HubSpot's industry field. |
| `Organization.number_of_employees` | `Company.numberofemployees`   | direct                  |                                                                                                                                                     |
| `Organization.created_at`          | `Company.createdate`          | direct                  |                                                                                                                                                     |
| `Organization.address.street`      | `Company.address`             | direct                  |                                                                                                                                                     |
| `Organization.address.city`        | `Company.city`                | direct                  |                                                                                                                                                     |
| `Organization.address.state`       | `Company.state`               | direct                  |                                                                                                                                                     |
| `Organization.address.postal_code` | `Company.zip`                 | direct                  |                                                                                                                                                     |
| `Organization.address.country`     | `Company.country`             | direct                  |                                                                                                                                                     |

## What to watch for in a Close to HubSpot migration

The issues we plan around on this pair: limits and data-model gaps that the official import tools leave to you.

medium

### Close's composite contact\_name field requires a name-splitting step before HubSpot import

Close stores a contact's full name as a single composite contact\_name text field on the Lead object rather than as separate first\_name and last\_name fields.

How we handle it

HubSpot Contact requires structured firstname and lastname fields. FlitStack splits contact\_name on the first space delimiter to populate firstname and lastname. For names with no space (e.g., single-word names like 'Madonna'), the entire value is placed in lastname and firstname is left blank. Multi-word last names or names with non-standard formatting (e.g., 'Jean-Paul' or 'van der Berg') may require manual review after migration for accuracy.

high

### Close Custom Activities have no direct HubSpot equivalent and require a mapping decision per activity type

Close Custom Activities are named, typed activity records that users define to track events like 'Proposal Sent', 'Demo Completed', or 'Contract Sent' — each with its own set of custom fields.

How we handle it

HubSpot has no native Custom Activities object. FlitStack resolves each unique Close Custom Activity Type to either a HubSpot custom Deal property (if the activity is a deal milestone) or a HubSpot custom object (if the activity is a standalone event with multiple fields). The decision is documented in the migration plan before data moves. If a Close account has more than 10 distinct Custom Activity Types, the mapping planning phase extends by 1–2 days to allow proper custom object and property configuration in HubSpot.

medium

### Close's multi-pipeline model maps to HubSpot Deal Pipelines but stage probability defaults must be reapplied

Close pipelines have per-stage probability values that drive weighted pipeline forecasting.

How we handle it

HubSpot Deal Stages also carry probability settings, but they are configured at the pipeline level in HubSpot's Deal Pipeline settings, not per-deal. FlitStack transfers each Close stage's probability percentage and applies it to the corresponding HubSpot Deal Stage. However, if Close has non-standard probability values (e.g., stage 'Negotiation' at 90% in one pipeline but 70% in another), HubSpot's stage probability can only be set once per stage name — teams with pipeline-specific probability overrides need to either rename stages or accept that the HubSpot stage probability will apply uniformly across all deals in that stage, regardless of source pipeline context.

medium

### Close SMS and calling activity migrates as engagement history but HubSpot's native calling product must be separately configured

Close's built-in phone and SMS are platform-native communication features that generate activity records with call outcomes, durations, and recordings.

How we handle it

The activity data (call history, duration, outcome, and notes) migrates to HubSpot as engagement records. However, Close call recordings are stored in Close's own media storage and cannot be rehosted to HubSpot's file storage without manual re-upload. HubSpot's native calling and SMS features (available as Sales Hub add-ons) are separate from the migrated call history — the team must configure a HubSpot calling integration to resume making and logging calls within HubSpot. This is a product decision, not a data migration limitation.

low

### Close Smart Views (saved filter configurations) do not transfer — the filter logic must be manually rebuilt in HubSpot

Close Smart Views save named filter configurations on the Leads, Contacts, and Opportunities tabs.

How we handle it

These saved views are Close-specific — the filter schema does not export as reusable objects and there is no HubSpot equivalent for saved views in the same sense. Each Smart View's filter criteria (field names, operators, and values) are exported as a reference document during the migration. HubSpot list filters and saved filter views can be rebuilt manually in HubSpot's Contacts, Companies, and Deals views, but the rebuild is a manual step for the admin after go-live. Teams with a large number of Smart Views (more than 20) should allocate additional admin time for the rebuild phase.

## How the migration runs

1. ### Export Close data via API and profile the schema

   FlitStack connects to Close's API using the organization's API key and exports all Lead, Contact, Organization, Opportunity, Task, and Activity records in JSON format.

   What this step covers

   Custom field definitions are exported separately from the Close Custom Fields API. Custom Activity Types and their associated field definitions are inventoried. A data profile is run to identify record counts per object, custom field counts per object, the number of unique Close pipelines, and any records with missing required fields (e.g., leads with no email address). This profile generates the migration scope document and flags any data quality issues that need resolution before mapping begins.

2. ### Configure HubSpot destination schema and create custom properties

   Before any data is written, FlitStack creates the HubSpot custom properties needed for the migration.

   What this step covers

   For each Close custom field, a corresponding HubSpot property is created with the matching data type. For each Close Custom Activity Type, a HubSpot custom object or Deal property is created depending on the mapping decision documented in the schema review. Close pipelines are pre-created in HubSpot as Deal Pipelines with stages named and ordered to match the Close pipeline configuration. FlitStack delivers a schema setup checklist so the HubSpot admin can verify all properties are created with the correct types before the import step begins.

3. ### Resolve owner and contact associations by email match

   Close owner IDs are resolved to HubSpot user accounts by matching the owner's email address against HubSpot user emails.

   What this step covers

   Any Close owners without a corresponding HubSpot user are flagged on a pre-migration exception report — the team can either create HubSpot user accounts for them before migration or assign their records to a fallback HubSpot user. Similarly, Opportunity-Lead associations are resolved: each Close Opportunity's lead\_id is matched to the migrated HubSpot Contact's email to establish the HubSpot Deal-Contact association. Organizations are migrated first to ensure Company IDs are available for Contact-to-Company linking before Contact records are written.

4. ### Run a sample migration with field-level diff across all record types

   A representative slice of records — typically 200–500 records spanning Leads, Organizations, Opportunities, Tasks, and a sample of each Custom Activity Type — is migrated to HubSpot in a test run.

   What this step covers

   FlitStack generates a field-level diff comparing each source record's field values against the corresponding destination record in HubSpot. The diff covers custom property values, pipeline assignments, stage names, probability values, and owner resolution. The sample migration results are reviewed with the client before the full run commits. Any field mapping errors or missing HubSpot properties discovered during the sample are corrected in the mapping configuration before the full migration proceeds.

5. ### Execute full migration with delta-pickup window and audit log

   The full migration runs in dependency order: Companies first, then Contacts (with Organization lookups resolved), then Deals (with Contact and Organization associations, pipeline assignments, and stage mapping applied), then Tasks, then Activities, then Custom Activities.

   What this step covers

   A delta-pickup window of 24–48 hours opens at the point of cutover — any records modified or created in Close during this window are captured in a final incremental run. FlitStack generates an audit log covering every record written, every field mapped, and every skipped record with a reason. One-click rollback is available if post-migration reconciliation identifies critical data integrity issues, reverting HubSpot to its pre-migration state while preserving the Close export as a re-importable asset.

6. ### Deliver workflow reference export and rebuild guide for Close automations

   Close Workflow definitions are exported as structured JSON, capturing each workflow's trigger type, conditions, condition logic (AND/OR), and all action steps.

   What this step covers

   This export is delivered alongside a rebuild guide that maps each Close workflow trigger and action to its HubSpot Workflows equivalent. The guide covers: Close trigger types (e.g., Opportunity status change, inbound email) mapped to HubSpot workflow enrollment triggers; Close conditions mapped to HubSpot if/then branches; and Close actions (e.g., send email, create task, update field) mapped to their HubSpot workflow action counterparts. The Close workflow export and rebuild guide are handed off to the HubSpot admin as a self-service reference for recreating automations post-migration.

![](https://flitstack.ai/platforms/close.svg) Close ![](https://flitstack.ai/platforms/hubspot.svg) HubSpot

1. Connect
2. Map
3. Sample
4. Migrate
5. Verify

- **Contacts** 48,210 / 48,210 Done
- **Companies** 9,134 / 9,134 Done
- **Deals** 6,377 / 11,920 In progress

Example run

******Restore points · HubSpot Rollback ready

1. Before sample run Restore point 01 Restore
2. Before full migration Restore point 02 Restore
3. After verification Restore point 03 Current

Example

## How long it takes, and what drives the quote

**48–72 hours for under 25,000 records** Typical, smaller accounts

**5–8 days for over 250,000 records or heavy custom-activity / multi-pipeline setups** Large or heavily customised accounts

Close-to-HubSpot migrations land in the lower-to-middle portion of FlitStack's pricing range because Close's data model is relatively lean — most teams have under 30 custom fields and 2–4 pipelines. The primary cost drivers are the number of custom activities (each unique activity type adds mapping complexity), the count of custom fields requiring HubSpot property creation before import, and whether the Close account uses multi-object custom fields that need HubSpot custom objects to be configured. Heavy use of Close's bulk-email and SMS activity history can increase activity migration time because each engagement log must be written to HubSpot's engagement API individually. Every quote is scoped with you; there is no self-serve pricing.

[Get a quote for Close to HubSpot →](https://flitstack.ai/contact)

## Why teams move from Close to HubSpot

- Close's built-in calling and SMS features are priced into the per-seat plan, but scaling to international teams hits a wall — SMS is US/CA/GB/AU only. Teams requiring broader international outreach or native HubSpot calling integration migrate to HubSpot's Sales Hub to consolidate telephony with the rest of their marketing and sales stack. G2 reviewers on Close note that 'SMS only works in US/CA/GB/AUS' as a recurring frustration at scale.
- HubSpot's free CRM tier provides contact management, company tracking, deal pipelines, and email tracking at no cost, while Close's Essentials plan starts at $49/seat/month. Small teams evaluating total cost of ownership find that HubSpot's free tier with paid add-ons for calling and automation is more flexible than Close's per-seat pricing for outbound-heavy workflows.
- Close's reporting and analytics are praised for pipeline visibility but users report that forecasting depth and dashboard customization cap out sooner than they expect. HubSpot's reporting, combined with its native analytics and the ability to connect to HubSpot's broader marketing and service hubs, offers more unified revenue intelligence for teams outgrowing Close's built-in dashboards.
- Close Workflows are gated behind Growth ($99/user/month) and Scale ($139/user/month) plans. Teams on Close Essentials who need workflow automation must pay for an upgrade. HubSpot offers HubSpot Workflows as a distinct product within Sales Hub and Operations Hub, and teams often find the HubSpot automation ecosystem more extensible when paired with HubSpot's broader platform.
- Acquired companies frequently standardize on HubSpot as their CRM of record, especially when HubSpot's marketing hub is already in use. Migrating from Close to HubSpot is a common post-M\&A data consolidation step, allowing the combined team to operate from a single CRM with shared reporting and a unified customer view.

Questions, answered

## Close to HubSpot migration questions

How long does a Close to HubSpot CRM migration take?

A Close-to-HubSpot migration for under 25,000 total records typically completes within 48–72 hours of clock time once the HubSpot schema is prepared. The longest step is usually the mapping planning phase — specifically resolving Close Custom Activities and creating HubSpot custom properties to receive them. Larger migrations with 250,000+ records, multiple Custom Activity Types, and more than five pipelines extend to 5–8 days. A sample migration run adds 1–2 days to the timeline but significantly reduces the risk of a full-run failure.

Will my Close workflows migrate to HubSpot Workflows?

No. Close Workflows (available on Growth and Scale plans at $99 and $139 per seat) do not migrate to HubSpot. The automation logic — triggers, conditions, branches, and actions — is Close-platform-specific and has no export path to HubSpot's workflow model. FlitStack exports each Close workflow definition as a structured JSON file and delivers a rebuild guide that maps every Close workflow element to its HubSpot Workflows equivalent so your HubSpot admin can recreate the logic manually after migration. Email templates and sequence configurations from Close are also excluded and must be rebuilt in HubSpot's template editor.

What does a Close Custom Activity become in HubSpot?

Close Custom Activities are user-defined activity types with their own custom fields — for example, a 'Proposal Sent' activity that tracks proposal version, sent date, and recipient. HubSpot has no native Custom Activities equivalent, so each Custom Activity Type requires a mapping decision. If the activity represents a deal milestone (e.g., 'Contract Sent'), it maps to a custom Deal property in HubSpot. If it is a standalone event with multiple data fields, it maps to a HubSpot custom object. FlitStack documents this decision for every unique Custom Activity Type in your Close account before migration runs so the HubSpot schema can be prepared accordingly.

Can I migrate Close custom fields to HubSpot custom properties?

Yes. Close custom fields on Lead, Contact, and Opportunity objects all migrate to HubSpot custom properties. The field data type is preserved — text, number, date, and Boolean fields migrate directly. Picklist fields require the picklist options to be pre-created in HubSpot as property options before import; FlitStack generates the option list from the Close custom field definition. Multi-select picklist fields require a HubSpot custom property configuration step because HubSpot handles multi-select options differently than Close. Custom field names are preserved as HubSpot property labels, with the internal field name converted to a HubSpot-compliant format (e.g., lowercase with underscores).

What happens to Close Smart Views after migration to HubSpot?

Close Smart Views — saved filter configurations on Leads, Contacts, and Opportunities — do not migrate because they are platform-native view definitions with no export format. FlitStack exports each Smart View's filter criteria (field names, operators, and values) as a reference document. In HubSpot, your admin can rebuild these as saved filters in the Contacts, Companies, and Deals views, or as HubSpot Lists with static or dynamic enrollment criteria. Teams with many Smart Views (more than 20) should allocate dedicated admin time for this rebuild step — it is a manual post-migration task, not part of the data migration run.

Does the migration affect my Close account during cutover?

No. FlitStack uses scoped read-only API access to Close — your team continues working in Close throughout the migration with no disruption to daily operations. A delta-pickup window (24–48 hours) opens at the cutover point to capture any records created or modified in Close during that window. The delta run merges those changes into HubSpot so the destination reflects Close's final state at go-live. No writes are made to Close at any point during the migration. Your Close account remains fully functional and billing continues unchanged until you decide to offboard Close separately.

What happens to Close's built-in calling and SMS history in HubSpot?

Close call records — including duration, outcome, caller ID, and notes — migrate as HubSpot engagement records linked to the correct Contact. SMS message history migrates similarly as engagement notes with an SMS type marker. However, Close call recordings are stored in Close's media infrastructure and cannot be bulk-transferred to HubSpot's file storage. Teams that need to preserve call recordings must download them from Close separately and manually re-upload to HubSpot's file system or a linked storage service. HubSpot's native calling product must also be configured separately if you want to resume making and logging calls directly within HubSpot — the migrated history does not activate HubSpot's calling feature automatically.

How are Close's multi-pipeline configurations handled in HubSpot?

Each Close pipeline maps to a separate HubSpot Deal Pipeline. Pipeline stage names, ordering, and probability values are transferred to the corresponding HubSpot Deal Pipeline and its stages. HubSpot Deal Pipelines can be set as the default pipeline and can be associated with different teams using HubSpot's team-based pipeline access controls. One nuance: if two Close pipelines share the same stage name but have different probability values for that stage, HubSpot's stage probability can only be set once per stage — the migration plan flags this scenario and your team chooses which pipeline's probability takes precedence or renames the stage to differentiate it.

## Related migrations

[![](https://flitstack.ai/platforms-trim/hubspot.webp) Migrate to **HubSpot** Every source we move into HubSpot, native options and the checklist. Guide, checklist & sources](https://flitstack.ai/migrations/crm/hubspot)

### [HubSpot implementation](https://flitstack.ai/services/hubspot-implementation)

[Set up HubSpot and migrate into it as one engagement.](https://flitstack.ai/services/hubspot-implementation)

[See the service →](https://flitstack.ai/services/hubspot-implementation) [**Act! to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/act/to/hubspot) [**Sentia to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/sentia/to/hubspot) [**Nimble CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/nimble-crm/to/hubspot) [**Zendesk Sell to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/zendesk-sell/to/hubspot) [**Zoho CRM to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/zoho-crm/to/hubspot) [**Mailchimp to HubSpot** Mapping · history · rollback](https://flitstack.ai/migrations/crm/mailchimp/to/hubspot) [**Close to monday CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/close/to/monday-crm) [**Close to Salesforce** Mapping · history · rollback](https://flitstack.ai/migrations/crm/close/to/salesforce-sales-cloud) [**Close to Zoho CRM** Mapping · history · rollback](https://flitstack.ai/migrations/crm/close/to/zoho-crm)

## Sources: official documentation

1. [Format import files — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/set-up-your-import-file)
2. [Create and edit custom objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/object-settings/create-custom-objects)
3. [Import objects programmatically — HubSpot Knowledge Base](https://knowledge.hubspot.com/import-and-export/import-objects)
4. [Understand property field types in HubSpot](https://knowledge.hubspot.com/properties/property-field-types-in-hubspot)
5. [Associate records on CRM objects — HubSpot Knowledge Base](https://knowledge.hubspot.com/records/associate-records)
6. [Integration throughput and limits — HubSpot Knowledge Base](https://knowledge.hubspot.com/integrations/integration-throughput-and-limits)
7. [HubSpot Cloud Infrastructure and Data Hosting FAQ](https://knowledge.hubspot.com/account-security/hubspot-cloud-infrastructure-and-data-hosting-frequently-asked-questions)

Get a quote

## Moving from Close to HubSpot?

Tell us roughly how many records and objects you have. We scope the mapping and the HubSpot setup with you, then send a quote.

[Get a quote](https://flitstack.ai/contact)
