Skip to content
Get a quote

Nutshell to HubSpot migration

Moving from Nutshell to HubSpot CRM unlocks HubSpot's marketing automation, multi-pipeline management, and the full free CRM tier — but Nutshell's flat people/company model requires careful mapping to HubSpot's lifecycle_stage, Contact/Lead split, and custom property conventions. FlitStack AI maps every Nutshell person, company, deal, and activity into HubSpot objects, preserves original create dates, and handles the Contact-versus-Lead routing decision your team specifies before any data moves.

Short answer

FlitStack AI migrates contact / leads, hubspot contact.lifecycle_stages, contact / lead custom properties, companies and company custom properties from Nutshell 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 50,000 Nutshell records.

By

Source Nutshell
DestinationHubSpot
Contact / LeadHubSpot Contact.lifecycle_stageContact / Lead custom propertiesCompanyCompany custom properties
Mapped field by field · sample run · one-click rollback

What moves from Nutshell to HubSpot?

Teams migrate from Nutshell to HubSpot when they have outgrown Nutshell's feature set — specifically when they need HubSpot's free CRM tier with unlimited contacts, built-in marketing automation, multi-deal pipeline reporting, or integration with a partner ecosystem already running HubSpot.

Read the full summary

Nutshell stores People (contacts), Companies, Leads, Deals, and Activities in a flat object model without a native lifecycle-stage concept. HubSpot uses Contacts and Leads as separate objects, tracks lifecycle_stage as a required property for Contact records, supports multiple parallel deal pipelines, and requires custom properties to follow HubSpot's naming conventions. FlitStack AI extracts Nutshell data via the Nutshell JSON-RPC API and loads it into HubSpot via the HubSpot REST API and Bulk API, applying a Contact/Lead split rule that your team configures before migration, mapping Nutshell custom fields to HubSpot custom properties, and preserving original create dates as custom datetime fields since HubSpot's standard createdate field reflects the import timestamp. Workflows, sequences, email templates, and Nutshell sales automation do not migrate — those must be rebuilt in HubSpot's workflow engine, and we provide an export of Nutshell workflow definitions as a rebuild reference. Delta-pickup captures any records modified during the cutover window.

split

People → Contact / Lead

Nutshell People split into HubSpot Contact or Lead based on your specified routing rule.

How it maps

The default rule sends active customers and recent engaged contacts to HubSpot Contact; everything else routes to HubSpot Lead. We apply the rule at migration time using Nutshell's last_activity_date and any custom status field your team defines as the trigger.

custom_field_required

People.status → HubSpot Contact.lifecycle_stage

HubSpot has no direct Nutshell status equivalent.

How it maps

We create a custom HubSpot contact property (Nutshell_Status__c or a name you specify) to preserve the original Nutshell status label. If your team has defined a lifecycle progression in Nutshell, we map the final status value into HubSpot's lifecycle_stage picklist options and set the contact's HubSpot lifecycle_stage to match.

custom_field_required

People.custom_fields → Contact / Lead custom properties

Nutshell custom fields on People map to HubSpot custom contact or lead properties.

How it maps

HubSpot requires each custom property to be created via the HubSpot Properties API before import. We create the properties using the same field type (text, number, date, picklist) and then map the values. Picklist custom fields in Nutshell require value-by-value mapping to HubSpot's picklist options.

direct

Company → Company

Direct map. Nutshell Company fields (name, domain, industry, phone, address) map to HubSpot company properties using HubSpot's standard field names (name, domain, industry, phone, address).

How it maps

HubSpot's company object also supports a city/state/country split on address fields — we map the single Nutshell address string to HubSpot's address fields or preserve it as a single address_line1 property.

custom_field_required

Company.custom_fields → Company custom properties

Nutshell custom fields attached to Company records are migrated to HubSpot company custom properties using the same pattern applied to People custom fields.

How it maps

Each HubSpot property is created first via the HubSpot Properties API before any data is loaded, preserving the original field type such as text, number, date, picklist, or multi-checkbox. For Nutshell Company custom fields that use multi-select picklist values, these map to HubSpot multi-checkbox properties with individual checkbox options corresponding to each Nutshell picklist choice. All custom field values are populated during the migration run once the property schema is in place.

direct

Lead → Lead

Nutshell Leads that are not also People records map directly to HubSpot Leads.

How it maps

Fields (name, email, phone, company, status, source) map to HubSpot Lead properties. Nutshell Lead custom fields migrate as HubSpot lead custom properties. Nutshell Leads that are also People records are already handled by the People split.

What moves12 objects
NutshellHubSpot
  • PeopleContactsplit
  • People.statusHubSpot Contact.lifecycle_stagetransformed
  • People.custom_fieldsContacttransformed
  • CompanyCompany1:1
  • Company.custom_fieldsCompany custom propertiestransformed
  • LeadLead1:1

+ 6 more in the mapping below

How Nutshell 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.

DimensionNutshellHubSpot
Contact vs Lead modelNutshell has one 'People' object for all contacts and leads with no required status field; a Lead status is a custom field.HubSpot separates Contacts and Leads into distinct objects with different property sets; lifecycle_stage is a required property on Contact.
Custom property namingNutshell custom fields use whatever name you assign; no suffix convention; stored per object (People, Company, Lead).HubSpot custom properties use snake_case names; stored on the Contact, Company, Deal, or Ticket object; accessible via the properties API.
Pipeline modelNutshell supports one deal pipeline per account by default; stages are a picklist on the Deal record.HubSpot supports multiple named deal pipelines simultaneously; each pipeline has its own stage names, probabilities, and report views.
Workflows and automationNutshell has built-in sales automation, email sequences, and task rules that live inside the Nutshell account.HubSpot workflows are separate from data; they must be recreated in HubSpot's workflow editor; no automated transfer exists.
Reporting modelNutshell provides standard reports; users note reporting depth is limited and often requires manual Excel exports for detailed analysis.HubSpot offers revenue analytics, attribution reporting, and the analytics add-on; deal-specific reporting ties to pipeline and stage.
Pricing structureNutshell charges $13–$79 per user per month; pricing includes contacts and storage without per-contact billing.HubSpot's free CRM tier is contact-unlimited; paid Starter at $50/month; Professional at $890/month for five users; marketing automation billed separately.

Nutshell to HubSpot field mapping

The 30 most-used fields of 43 mapped for this pair. Custom fields are added from your own schema during scoping. Download the full mapping (CSV) ↓ or open it in the field mapping template.

Field mapping5 shown
NutshellHubSpot
  1. first_namePeople firstnameContact
  2. last_namePeople lastnameContact
  3. emailPeople emailContact
  4. phonePeople phoneContact
  5. titlePeople jobtitleContact
Nutshell fieldHubSpot fieldMappingNote
People.first_nameContact.firstnamedirect
People.last_nameContact.lastnamedirect
People.emailContact.emaildirect
People.phoneContact.phonedirect
People.titleContact.jobtitledirect
People.addressContact.addressdirect
People.cityContact.citydirect
People.stateContact.statedirect
People.postal_codeContact.zipdirect
People.countryContact.countrydirect
People.webContact.websitedirect
People.linkedin_urlContact.linkedin_imdirect
People.twitter_handleContact.twitter_handledirect
People.created_dateContact.original_create_date__ccustom_field_requiredHubSpot sets Createdate at import time; original Nutshell created_date preserved as a custom datetime property for reporting continuity.
People.last_activity_dateContact.notes_last_updateddirect
People.owner_emailContact.hubspot_owner_idtransformedOwner email resolves to HubSpot owner ID by email match. Unmatched owners are flagged; assign to a fallback HubSpot owner or invite the user before migration.
People.nutshell_idContact.source_system_id__ccustom_field_requiredNutshell internal ID stored as a custom property for traceability and delta-run de-duplication.
People.statusContact.lifecycle_stagevalue_mappingNutshell status picklist values map to HubSpot lifecycle_stage values. Your team specifies the mapping rule (e.g., Nutshell 'Customer' → HubSpot 'customer').
Company.nameCompany.namedirect
Company.domainCompany.domaindirect
Company.industryCompany.industryvalue_mappingHubSpot industry picklist values may not match Nutshell industry labels exactly; unmapped values default to 'OTHER' or a custom picklist option.
Company.phoneCompany.phonedirect
Company.addressCompany.addressdirect
Company.cityCompany.citydirect
Company.stateCompany.statedirect
Company.postal_codeCompany.zipdirect
Company.countryCompany.countrydirect
Company.employee_countCompany.number_of_employeesdirect
Company.annual_revenueCompany.annual_revenuedirect
Company.created_dateCompany.original_create_date__ccustom_field_requiredOriginal Nutshell company create date preserved as custom datetime for reporting continuity.

What to watch for in a Nutshell to HubSpot migration

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

high

Contact/Lead split rule requires pre-migration configuration

HubSpot separates Contacts and Leads into distinct objects with different property sets, whereas Nutshell has a single People record for both.

How we handle it

Before migration begins, your team must define the routing rule that determines which Nutshell People become HubSpot Contacts versus HubSpot Leads. The most common rule uses Nutshell's status or last_activity_date field — active customers route to Contact, everything else routes to Lead. This decision affects every record and must be locked in before the migration mapping is validated. If no rule is specified, we default to routing anyone with a HubSpot-relevant engagement history to Contact.

high

HubSpot lifecycle_stage is a Contact-level property with a finite picklist

HubSpot's lifecycle_stage field exists only on the Contact object and accepts a predefined set of values (subscriber, lead, MQL, SQL, opportunity, customer, evangelist).

How we handle it

Nutshell has no native equivalent — any lifecycle or status concept in Nutshell is stored as a custom field. When migrating Nutshell People to HubSpot Contact, we create a custom property to hold the original Nutshell status and then map the final value to the HubSpot lifecycle_stage picklist. If the Nutshell status value has no HubSpot lifecycle_stage equivalent, it is preserved as a custom property only and lifecycle_stage is left blank or set to the closest match your team approves.

medium

Nutshell custom fields require HubSpot property pre-creation

HubSpot's custom properties must exist before data is imported — you cannot create a property and load data in the same operation without using HubSpot's bulk import workaround.

How we handle it

FlitStack AI creates all required HubSpot custom contact, company, and deal properties via the HubSpot Properties API before loading any records. For picklist and multi-checkbox custom fields, we also create the corresponding HubSpot picklist options matching the Nutshell field values. This pre-creation step adds planning time for accounts with more than 20 custom fields.

medium

Workflows and automation do not migrate — they must be rebuilt

Nutshell's sales automation rules, email sequences, task triggers, and lead assignment workflows are proprietary constructs that have no HubSpot equivalent.

How we handle it

HubSpot's workflow engine uses different concepts (trigger objects, enrollment criteria, action types) that do not accept a direct import of Nutshell workflow definitions. FlitStack AI exports your Nutshell workflow definitions as a structured document that your HubSpot admin can use as a rebuild reference. Automations are not run during migration — they are a post-migration configuration step.

low

Multi-company associations on Nutshell People collapse to primary company only

Nutshell allows a single Person to be associated with multiple Companies (N:1 on the Nutshell company side).

How we handle it

HubSpot's Contact object has a single primary company association plus optional secondary associations via the Account Contact Relationships feature. For Nutshell People with multiple company associations, we migrate the most recently active or most recently modified company as the primary HubSpot company association and surface the rest in a custom multi-company reference property for manual reconciliation if needed.

How the migration runs

  1. Audit Nutshell data and define Contact/Lead routing rule

    FlitStack AI connects to your Nutshell account via the JSON-RPC API and pulls a full data export: all People (active and inactive), Companies, Leads, Deals, and Activities.

    What this step covers

    We profile the data to surface duplicate records, blank required fields, and custom field usage. During this step your team specifies the Contact/Lead routing rule — typically based on Nutshell status, last_activity_date, or a custom field value — and approves the custom property names we will create in HubSpot for fields that have no native HubSpot equivalent.

  2. Create HubSpot custom properties and configure pipelines

    Before any data loads, we create all required HubSpot custom contact, lead, company, and deal properties via the HubSpot Properties API.

    What this step covers

    For picklist fields, we create the picklist options matching the Nutshell values. If your Nutshell account uses multiple deal pipelines, we create corresponding HubSpot deal pipelines and configure stage names, probabilities, and display order per pipeline. This step requires a HubSpot admin to grant FlitStack AI access to the HubSpot account with sufficient permissions to create properties and pipelines.

  3. Resolve owners and run sample migration with field-level diff

    Nutshell owner email addresses are matched to HubSpot user emails.

    What this step covers

    Unmatched owners are flagged for your team to either invite them to HubSpot or assign their records to a fallback HubSpot user. We run a sample migration of 100–500 representative records — spanning contacts, companies, deals, and activities — and generate a field-level diff showing source values and destination values for every mapped field. You review the diff, confirm the Contact/Lead routing is correct, and approve the full migration plan.

  4. Run full migration with delta-pickup and audit log

    The full migration loads into HubSpot via the HubSpot REST and Bulk APIs, respecting HubSpot's rate limits to avoid throttling.

    What this step covers

    During the cutover window your team continues working in Nutshell; a delta-pickup window (typically 24–48 hours) captures any records created or modified in Nutshell after the initial load. Every operation is recorded in an audit log. If reconciliation identifies missing or misaligned records, one-click rollback reverts the HubSpot state to the pre-migration snapshot so the team can investigate and re-run without data loss.

  5. Deliver export package for HubSpot workflow rebuild

    FlitStack AI exports your Nutshell workflow definitions, sequence settings, task rules, and lead assignment logic as a structured JSON and PDF reference package.

    What this step covers

    This package is handed off to your HubSpot admin to recreate automations in HubSpot's workflow editor. We do not migrate workflows — they require destination-specific recreation — but the export reduces rebuild effort by surfacing the exact trigger conditions and actions your team configured in Nutshell.

Nutshell HubSpot
  1. Connect
  2. Map
  3. Sample
  4. Migrate
  5. Verify
  • Contacts48,210 / 48,210 Done
  • Companies9,134 / 9,134 Done
  • Deals6,377 / 11,920 In progress
Example run
Restore points · HubSpotRollback ready
  1. Before sample runRestore point 01Restore
  2. Before full migrationRestore point 02Restore
  3. After verificationRestore point 03Current
Example

How long it takes, and what drives the quote

48–72 hours for under 50,000 Nutshell recordsTypical, smaller accounts
5–8 days for over 250,000 records or setups with many Nutshell custom fields, multiple deal types, or a large activity historyLarge or heavily customised accounts

Nutshell-to-HubSpot migration pricing scales with three variables: total record count (contacts, companies, deals, activities), number of Nutshell custom fields requiring HubSpot custom property creation, and the number of Nutshell deal pipelines that must map to separate HubSpot pipelines with independent stage configurations. The Contact/Lead split decision, while requiring upfront configuration, adds minimal cost since it is a mapping rule rather than per-record work. Every quote is scoped with you; there is no self-serve pricing.

Get a quote for Nutshell to HubSpot →

Why teams move from Nutshell to HubSpot

  • Nutshell's feature set is capped at mid-market capabilities — users report limited automation options, weak out-of-the-box reporting that requires manual Excel exports for meaningful analysis, and a mobile app that lacks desktop functionality. When teams need advanced reporting, multi-channel marketing automation, or a deeper integration ecosystem, HubSpot's platform at the same team size becomes the pragmatic choice rather than adding another point solution.
  • HubSpot's free CRM tier with unlimited contacts removes the per-contact pricing anxiety that grows as Nutshell accounts scale. Teams that started on Nutshell at 500 contacts find themselves paying for contacts they have already worked — HubSpot's contact-unlimited free tier eliminates that billing friction entirely for the CRM core.
  • A partner, acquisition target, or key integration requires HubSpot — either the team is being asked to standardise on HubSpot as part of a vendor relationship, a parent company mandate, or a strategic alliance that makes HubSpot the de facto CRM. Running a second CRM alongside HubSpot creates data silos and reconciliation overhead that is harder to sustain than a single cutover.
  • Nutshell's one-deal-pipeline model works for single-product teams but creates visibility problems for businesses with multiple product lines, service tiers, or channel-specific deal tracking. HubSpot's multi-pipeline reporting lets each business unit maintain its own stage names, probability curves, and revenue forecasts without forcing a single taxonomy onto heterogeneous deal types.

Questions, answered

Nutshell to HubSpot migration questions

How long does a Nutshell to HubSpot migration take?

Most Nutshell-to-HubSpot migrations complete in 48–72 hours for under 50,000 total records including contacts, companies, deals, and activities combined. Accounts with 250,000–500,000 records or extensive activity history extend to 5–8 days. The longest single step is the pre-migration planning phase — defining the Contact/Lead routing rule and creating all required HubSpot custom properties via the HubSpot Properties API — which typically takes 1–3 business days before any data extraction begins. Actual data transfer is constrained by HubSpot's API rate limits, which FlitStack AI respects to avoid throttling during the migration run.

Will my Nutshell workflows and automation rules migrate to HubSpot?

No. FlitStack AI migrates data and schema only — Nutshell workflows, email sequences, task triggers, and lead assignment rules do not transfer to HubSpot. HubSpot's workflow engine uses a different model and cannot import Nutshell automation definitions. We export your Nutshell workflow configurations as a structured rebuild reference so your HubSpot admin can recreate them in HubSpot's workflow editor after the data migration is complete and validated.

What happens to my Nutshell custom fields in HubSpot?

Nutshell custom fields on People, Companies, and Deals migrate to HubSpot custom properties on the corresponding Contact/Lead, Company, and Deal objects. Each HubSpot custom property is created via the HubSpot Properties API before migration, preserving the field type (text, number, date, picklist, multi-checkbox). For Nutshell picklist fields, the options are created in HubSpot and mapped value-by-value. Custom field values on all migrated records are populated during the migration run.

What does a Nutshell deal become in HubSpot?

Each Nutshell deal maps directly to a HubSpot deal. The deal name, amount, close date, and owner email (resolved to HubSpot owner ID) migrate as direct field mappings. Nutshell deal stages map to HubSpot pipeline stage names value-by-value. If your Nutshell account uses multiple deal pipelines, each becomes a named HubSpot pipeline with its own stage configuration. Nutshell deal associations to People and Companies map to HubSpot deal-to-contact and deal-to-company associations via HubSpot's associations API.

Can I migrate Nutshell leads that are not yet customers?

Yes. Nutshell Leads that are not also People records migrate directly to HubSpot Leads. For Nutshell People who are leads (not yet customers), the Contact/Lead routing rule your team defines before migration determines their destination — typically contacts with a Nutshell status of 'Lead' or 'Prospect' route to HubSpot Lead, while active customers route to HubSpot Contact. Nutshell Lead custom fields migrate as HubSpot lead custom properties.

Does the migration affect my Nutshell account during the cutover?

No. FlitStack AI uses scoped read-only access to your Nutshell account via the API — your team continues working in Nutshell without interruption during the migration. A delta-pickup window (24–48 hours) after the initial load captures any Nutshell records created or modified during the cutover period. Once delta-pickup completes, you can shut down Nutshell access and run exclusively in HubSpot. The delta window is configurable based on your team's cutover schedule.

How does FlitStack AI handle the Contact versus Lead split for Nutshell People?

The split is configured before migration starts. Your team specifies the routing rule — most commonly based on Nutshell status field value, last_activity_date threshold, or a custom field. We apply the rule programmatically at migration time: records matching the Contact criteria insert into HubSpot as Contacts; all others insert as Leads. You review the rule and a sample migration diff before the full run commits. This approach avoids manual per-record sorting and ensures the split is consistent across all migrated records.

Get a quote

Moving from Nutshell 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