CRM migration

Migrate from Nutshell to HubSpot

Field-level mapping, validation, and rollback between Nutshell and HubSpot. We move data and schema; workflows are rebuilt natively in HubSpot.

Nutshell logo

Nutshell

Source

HubSpot

Destination

HubSpot logo

Compatibility

92%

11 of 12

objects map 1:1 between Nutshell and HubSpot.

Complexity

BStandard

Timeline

48–72 hours

Rollback included Accuracy guarantee Field-level validation

Try the reverse

HubSpot
Nutshell

Overview

What this migration involves

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

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Nutshell logo

Nutshell

What's pushing teams away

  • Reporting features are considered weak by users—many resort to exporting data and performing analysis in Excel rather than using built-in dashboards.
  • Limited customization options for workflows, fields, and pipeline configurations compared to HubSpot or Salesforce, frustrating power users.
  • Mobile app is described as stripped-down relative to desktop, lacking many features available in the full web application.
  • Jack-of-all-trades positioning means Nutshell lacks the depth in any single area—marketing, service, or advanced sales automation—that growing teams eventually require.
  • Email integration limitations documented by TrustRadius reviewers, with some teams reporting reliability issues during high-volume campaign sends.

Choosing

HubSpot logo

HubSpot

What's pulling them in

  • Lowest barrier to entry of any major CRM — the free tier with unlimited contacts lets teams validate fit before committing to a paid plan, according to G2 and Capterra reviewers.
  • Native integration between the CRM and sales engagement tools (sequences, email tracking, dialer) means no separate sync configuration, a theme across G2 Sales Hub reviews.
  • Pipeline visualization, deal tracking, and automated workflows are consistently praised as intuitive and easy to set up without developer involvement.
  • Strong onboarding for new team members — reviewers on Capterra and G2 highlight how quickly new reps become productive without formal training.
  • The HubSpot platform ecosystem (Marketing, Sales, Service, CMS hubs) allows growing companies to consolidate tools without building new integrations.

Object mapping

How Nutshell objects map to HubSpot

Each row shows how a Nutshell object lands in HubSpot, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Nutshell

People

maps to

HubSpot

Contact / Lead

1:many
Fully supported

Nutshell People split into HubSpot Contact or Lead based on your specified routing rule. 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.

Nutshell

People.status

maps to

HubSpot

HubSpot Contact.lifecycle_stage

1:1
Fully supported

HubSpot has no direct Nutshell status equivalent. 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.

Nutshell

People.custom_fields

maps to

HubSpot

Contact / Lead custom properties

1:1
Fully supported

Nutshell custom fields on People map to HubSpot custom contact or lead properties. 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.

Nutshell

Company

maps to

HubSpot

Company

1:1
Fully supported

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). 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.

Nutshell

Company.custom_fields

maps to

HubSpot

Company custom properties

1:1
Fully supported

Nutshell custom fields attached to Company records are migrated to HubSpot company custom properties using the same pattern applied to People custom fields. 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.

Nutshell

Lead

maps to

HubSpot

Lead

1:1
Fully supported

Nutshell Leads that are not also People records map directly to HubSpot Leads. 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.

Nutshell

Deal

maps to

HubSpot

Deal

1:1
Fully supported

Direct map. Nutshell Deal fields — name, amount, stage, expected_close_date, owner, associated_people, associated_companies — map to HubSpot Deal properties (dealname, amount, dealstage, closedate, hubspot_owner_id, contacts, companies). The Nutshell Deal association to People and Companies maps to HubSpot's deal-to-contact and deal-to-company associations via HubSpot's associations API.

Nutshell

Deal.pipeline

maps to

HubSpot

Deal pipeline

1:1
Fully supported

If Nutshell uses multiple named deal pipelines, each Nutshell pipeline maps to a named HubSpot deal pipeline. HubSpot allows multiple concurrent pipelines — we create a HubSpot pipeline for each Nutshell pipeline, map stage names value-by-value, and configure probability defaults per stage. Single-pipeline Nutshell setups map to a single HubSpot pipeline with the same stage names.

Nutshell

Activity: Task

maps to

HubSpot

Engagement / Timeline

1:1
Fully supported

Nutshell tasks (to-do items, action items) map to HubSpot engagements of type TASK. The task subject, body, due date, and owner email resolve to a HubSpot owner by email match. HubSpot engagements attach to the associated Contact or Company record using the associations API. Original Nutshell task timestamps are preserved as a custom property on the engagement.

Nutshell

Activity: Call / Email / Meeting

maps to

HubSpot

Engagement / Timeline

1:1
Fully supported

Nutshell call logs, email records, and meeting records map to HubSpot engagements of types CALL, EMAIL, and MEETING respectively. HubSpot stores these as engagements attached to the relevant Contact or Company. Original timestamps, owners, and body content are preserved. Nutshell call duration and outcome fields map to HubSpot engagement metadata properties.

Nutshell

Activity: Note

maps to

HubSpot

Note / Timeline

1:1
Fully supported

Nutshell notes map to HubSpot notes attached to the relevant Contact, Company, or Deal record. We use HubSpot's notes API (v3) to create engagements of type NOTE, preserving the note body and original creation timestamp. Rich text in Nutshell notes is preserved as HTML in HubSpot.

Nutshell

Attachment

maps to

HubSpot

File

1:1
Fully supported

Nutshell file attachments download from Nutshell's storage and re-upload to HubSpot's file management. Files attach to the relevant Contact, Company, or Deal record via HubSpot's file associations API. HubSpot's default file size limit is 25MB per file — files exceeding this are flagged for manual handling or chunked upload.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

HubSpot logo

HubSpot gotchas

High

Marketing Contacts billing model is migration-critical

High

Feature tier gating is not visible until onboarding

Medium

Mandatory onboarding fees inflate year-one cost

Medium

HubSpot CSV importer cannot migrate engagements or attachments

Medium

Custom objects require Enterprise and a pre-existing schema

Pair-specific challenges

  • 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. 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.

  • 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). 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.

  • 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. 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.

  • 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. 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.

  • 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). 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.

Migration approach

Six steps for a successful Nutshell to HubSpot data migration

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

Platform deep dives

Context on both ends of the pair

Nutshell logo

Nutshell

Source

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation
HubSpot logo

HubSpot

Destination

Strengths

  • Genuinely useful free CRM tier with no seat limit on contact records.
  • All-in-one sales engagement layer (sequences, email tracking, calling, dialer) embedded natively in the CRM, eliminating a separate integration.
  • Intuitive interface and fast onboarding for individual reps, per G2 and Capterra reviews.
  • Workflow automation triggers across contacts, deals, and tickets with a visual builder.
  • API coverage for all standard objects including custom objects at Enterprise tier.

Weaknesses

  • Pricing model is contact-based at the marketing layer — importing all records as marketing contacts can multiply the monthly bill by 4×.
  • Feature tier cliffs are frequent surprises: sequences, calling, advanced reporting, and quoting are all gated, often requiring plan upgrades mid-implementation.
  • Mandatory onboarding fees at Professional ($1,500) and Enterprise ($3,500) are not prominently disclosed on the pricing page.
  • API rate limits are restrictive for bulk migration — burst limits of 100-200 req/10sec and search endpoint limits of 4 req/sec require careful job queuing.
  • Custom objects, additional pipelines, and advanced forecasting are Enterprise-only, making cost projections difficult for growing teams.

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Nutshell and HubSpot.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Nutshell: Not publicly documented in summary form..

  • Data volume sensitivity

    A

    Nutshell exposes a bulk API — large-volume migrations stream efficiently.

Estimator

Estimate your Nutshell to HubSpot migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Nutshell to HubSpot data migrations

Answers to the questions buyers ask most during Nutshell to HubSpot migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Nutshell to HubSpot migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

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.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Nutshell.
Land in HubSpot, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day