CRM migration

Migrate from HubSpot to Nutshell

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

HubSpot logo

HubSpot

Source

Nutshell

Destination

Nutshell logo

Compatibility

85%

11 of 13

objects map 1:1 between HubSpot and Nutshell.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Try the reverse

Nutshell
HubSpot

Overview

What this migration involves

Moving from HubSpot Sales Hub to Nutshell is a simplification migration driven by cost predictability and usability. Nutshell uses a per-user pricing model with no marketing contact metering, no mandatory onboarding fees, and a flatter feature tier that covers pipelines, reporting, and basic automation on its entry paid plan. We migrate HubSpot's Contact, Company, Deal, and Engagement records in dependency order: owners first, then organizations, then people with AccountId resolved, then opportunities with owner and stage assignments, then activity history via batched API calls. HubSpot Sequences, Workflows, and engagement Templates do not migrate as automation code; we deliver a written inventory of every active workflow and sequence with the recommended Nutshell equivalent so the customer's admin rebuilds them post-migration. Custom objects require schema pre-creation in Nutshell before any records transfer.

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

HubSpot logo

HubSpot

What's pushing teams away

  • Feature tier surprises drive churn — sequences, calling, quoting, and advanced automation are locked behind Professional at $100/seat, causing sticker shock when teams outgrow Starter.
  • Workflow configuration complexity increases at scale — multiple reviewers on Capterra and G2 note that HubSpot experts or significant admin time are required to maintain advanced automation.
  • Cost scales linearly with seats and marketing contacts, creating large bills for teams that grow quickly or inherit high contact counts from a previous CRM.
  • Frequent product updates and UI changes force ongoing re-training — Reddit reviewers in r/hubspot cite difficulty keeping up with constant new features and interface shifts.
  • Multi-brand, multi-region, and complex permission structures expose friction that Enterprise pricing cannot fully resolve, according to RevOps feedback in HubSpot community discussions.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How HubSpot objects map to Nutshell

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

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

HubSpot

Contact

maps to

Nutshell

Person

1:1
Fully supported

HubSpot Contact records map directly to Nutshell Person records. The HubSpot contact's email address becomes the primary identifier and dedupe key. We preserve all standard and custom contact properties as Nutshell custom fields during import, mapping HubSpot property types (text, number, date, picklist) to their Nutshell equivalents. The HubSpot Lifecycle Stage property is preserved as a custom text field hs_lifecycle_stage__c on the Person for audit and segmentation reference.

HubSpot

Company

maps to

Nutshell

Account

1:1
Fully supported

HubSpot Company records map to Nutshell Account (Organization). The company domain from HubSpot populates the Account's website field. We establish the Account-Parent relationship where it exists in HubSpot. The Account is created before any Person import so that the organization_id lookup is satisfied at the moment of Person insert, preventing orphaned Person records without an organization.

HubSpot

Deal

maps to

Nutshell

Lead

1:1
Fully supported

HubSpot Deal records map to Nutshell Lead. Note that Nutshell Lead is an opportunity record (a deal in flight) rather than an unqualified prospect record. The HubSpot dealstage property maps to a Nutshell pipeline stage. Closed-Lost and Closed-Won status from HubSpot map to Nutshell's lost and won Lead statuses. We resolve the owner_id and account_id (organization) references at migration time before inserting each Lead record.

HubSpot

Deal Stage

maps to

Nutshell

Lead Stage

lossy
Fully supported

Each HubSpot deal pipeline becomes a Nutshell pipeline. HubSpot stage names, probabilities, and display order transfer to Nutshell pipeline stages. We configure the pipeline in Nutshell before any Deal records import so that stage references are valid at insert time. Stage probability percentages migrate from HubSpot and round to Nutshell's stage probability field if Nutshell's plan supports probability tracking.

HubSpot

Pipeline

maps to

Nutshell

Pipeline

lossy
Fully supported

HubSpot's multiple deal pipelines (Starter 1, Professional 15, Enterprise 100) map to Nutshell's pipeline model. Nutshell supports multiple pipelines on Standard and Pro plans. We create each pipeline in Nutshell during the configuration phase, map its stages, and assign it to the relevant team or user group based on HubSpot's pipeline-to-owner assignment.

HubSpot

Owner

maps to

Nutshell

User

1:1
Fully supported

HubSpot Owner records map to Nutshell User accounts. We resolve by email address match. Any HubSpot Owner without a matching Nutshell User goes to a reconciliation queue for the customer's admin to provision before Deal and Contact migration resumes. Nutshell User records must exist before Deals and Persons can be assigned to them.

HubSpot

Engagement: Email

maps to

Nutshell

Activity (Email)

1:1
Fully supported

HubSpot email engagements map to Nutshell Activity records of type email. We preserve the email subject, body (plain text or HTML), timestamp, direction (sent/received), and recipient. The activity is linked to the target Person or Account by resolving the HubSpot contact_id and company_id to Nutshell person_id and account_id at migration time. Engagement association records preserve the email-to-contact link.

HubSpot

Engagement: Call

maps to

Nutshell

Activity (Call)

1:1
Fully supported

HubSpot call engagements map to Nutshell Activity records of type call. Call duration, disposition (HubSpot call_disposition property), and timestamp migrate to Nutshell's activity duration and custom fields. The call outcome is preserved in a custom field. Activity is linked to the target Person or Account using the resolved IDs.

HubSpot

Engagement: Meeting

maps to

Nutshell

Activity (Meeting)

1:1
Fully supported

HubSpot meeting engagements map to Nutshell Activity records of type meeting. Start time, end time, location, and attendees migrate. Attendee emails from HubSpot are matched to Nutshell Person records; any unmatched attendee emails are preserved in a custom field on the activity for post-migration resolution.

HubSpot

Engagement: Note

maps to

Nutshell

Note

1:1
Fully supported

HubSpot Note engagements (associated to contacts, companies, or deals) map to Nutshell Note records. The note body and timestamp migrate. Notes linked to a specific record in HubSpot are linked to the corresponding Person, Account, or Lead in Nutshell using the resolved target IDs.

HubSpot

Engagement: Task

maps to

Nutshell

Task

1:1
Fully supported

HubSpot Task engagements map to Nutshell Task records. Status, due date, priority, and assignment migrate. HubSpot task completion status (complete/incomplete) maps to Nutshell's task completion. Owner assignment migrates by resolving the HubSpot owner_id to the Nutshell User ID.

HubSpot

Product

maps to

Nutshell

Product

1:1
Fully supported

HubSpot Products map to Nutshell Product records. Product name, SKU, description, and price migrate directly. Nutshell's product structure supports the same fields needed for deal line items.

HubSpot

Line Item

maps to

Nutshell

Lead Product

1:1
Fully supported

HubSpot Line Items map to Nutshell Lead Product associations. We resolve the Product reference and the parent Deal (Nutshell Lead) at migration time. Quantity, unit price, and total price transfer directly. Line items import after Leads are confirmed in Nutshell to satisfy the parent reference.

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.

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

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

Pair-specific challenges

  • HubSpot CSV importer cannot export engagements or attachments

    HubSpot's native CSV export supports contacts, companies, deals, products, and notes only. Tasks, calls, emails, meetings, and file attachments cannot be exported via CSV. We extract these via HubSpot's CRM API in chronological batches, handling the 100-200 req/10sec burst and 4 req/sec search rate limits with exponential backoff and jitter. Attachments (file links and URLs) migrate as URL references in custom fields; the files themselves require separate download-and-reupload handling if the destination requires physical file migration.

  • HubSpot Lead object has no Nutshell equivalent

    HubSpot introduced a separate Lead object in 2023, available only on Sales Hub Enterprise. Nutshell does not have a separate Lead record type; all prospects enter as Person records or directly as Leads (opportunity records). We resolve HubSpot Lead records by mapping them to Nutshell Person records with the original Lead status preserved in a custom field. Any lifecycle-specific fields on the HubSpot Lead are appended as custom fields on the Nutshell Person.

  • Marketing Contact billing flag does not transfer

    HubSpot's Marketing Contacts model flags contacts for marketing-tier billing. Nutshell does not have a marketing contact billing model. All migrated contacts enter as active Person records. We preserve the HubSpot marketing_contact flag value in a custom field on each Person so the customer's admin can segment post-migration if needed. Email opt-in and opt-out preferences migrate to Nutshell's contact preferences fields.

  • Workflows and Sequences do not migrate as automation code

    HubSpot Workflows and engagement Sequences are automation templates, not CRM data objects. Nutshell's workflow model differs from HubSpot's property-triggered visual builder. We do not migrate Workflows or Sequences as code. We deliver a written inventory of every active HubSpot Workflow and Sequence with its trigger, conditions, actions, and a recommended Nutshell automation equivalent. The customer's admin rebuilds these in Nutshell post-migration.

  • Custom objects require destination schema pre-creation

    HubSpot custom objects (Enterprise-only) and their associated records require pre-creation of an equivalent schema in Nutshell before any data transfer. We work with the customer during scoping to define the target data model in Nutshell, including custom fields and any lookup relationships, before touching any record data. This prevents schema-mismatch errors during import.

Migration approach

Six steps for a successful HubSpot to Nutshell data migration

  1. Discovery and scoping

    We audit the source HubSpot portal across tier, custom properties, custom objects, pipeline count, active sequences, active workflows, and engagement volume. We pair this with a Nutshell plan decision: Standard covers most migrations with pipelines, basic reporting, and custom fields; Pro adds advanced reporting and workflow rules. The discovery output is a written migration scope document listing all objects to migrate, the owner reconciliation list, and the pipeline configuration requirements for Nutshell.

  2. Schema design and pipeline configuration

    We configure Nutshell's data model before any data moves. This includes creating the pipelines and stages (mapped from HubSpot deal pipelines), setting stage probabilities, creating any custom fields that correspond to HubSpot custom properties, and defining the field mapping from each HubSpot property to its Nutshell field or custom field. Schema is validated in Nutshell during a sandbox or staging pass before production migration.

  3. Owner reconciliation

    We extract every distinct HubSpot Owner referenced on Contact, Company, Deal, and Engagement records and match by email against Nutshell's User table. Owners without a matching Nutshell User go to a reconciliation queue for the customer's admin to provision. Migration cannot proceed past this step because Nutshell User assignments are required on Deals and can be required on Activities depending on the configuration.

  4. Production migration in dependency order

    We run production migration in record-dependency order: Users (manual provisioning, validated), Organizations (from HubSpot Companies), People (with organization_id resolved), Leads (from HubSpot Deals with owner_id and pipeline assignment resolved), Products, Activity history (calls, emails, meetings, tasks via batched API calls), Notes, and Custom Object records (last, after parent record lookups are confirmed). Each phase emits a row-count reconciliation report before the next phase begins.

  5. Cutover, delta migration, and Workflow handoff

    We freeze HubSpot writes during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver the Workflow and Sequence inventory document to the customer's admin team with Nutshell automation equivalents. We support a one-week hypercare window where we resolve reconciliation issues raised by the customer's team. We do not rebuild HubSpot Workflows in Nutshell as part of the migration scope.

Platform deep dives

Context on both ends of the pair

HubSpot logo

HubSpot

Source

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

Nutshell

Destination

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

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 HubSpot and Nutshell.

  • 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

    HubSpot: 110 requests per 10 seconds per installed account for OAuth apps on the latest platform versions (2025.2 / 2026.03). Free accounts: 100 req/10s and 250,000 daily requests. Professional and Enterprise: 190 req/10s. The CRM Search API has a separate ceiling of 4 requests per second per auth token. 429 is returned on exhaust..

  • Data volume sensitivity

    A

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

Estimator

Estimate your HubSpot to Nutshell 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 HubSpot to Nutshell data migrations

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

Can't find your answer?

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

Book a free 30 minute consultation

Most migrations land between two and four weeks for accounts under 10,000 Contacts and 2,000 Deals with no custom objects and a clean owner list. Migrations with large engagement histories (over 200,000 activity records), multiple pipelines, custom objects, or complex owner structures move to six to ten weeks because of engagement batching, pipeline configuration, and owner reconciliation work.

Adjacent paths

Related migrations to explore

Ready when you are

Move from HubSpot.
Land in Nutshell, 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