CRM migration
Field-level mapping, validation, and rollback between HubSpot and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
HubSpot
Source
Nutshell
Destination
Compatibility
11 of 13
objects map 1:1 between HubSpot and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Try the reverse
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Source platform
HubSpot platform overview
Scorecard, SWOT, gotchas, and pricing for HubSpot.
Destination platform
Nutshell platform overview
Scorecard, SWOT, gotchas, and pricing for Nutshell.
Data migration guide
The complete Nutshell migration guide
Data model, import mechanisms, field mapping strategy, pitfalls, and cutover — by the engineers running it.
Source platform guide
HubSpot migration guide
Understand the data you're exporting from HubSpot before mapping it.
Destination checklist
Nutshell migration checklist
Pre- and post-cutover tasks for moving onto Nutshell.
Source checklist
HubSpot migration checklist
Exit checklist for unwinding your HubSpot setup cleanly.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Nutshell
Person
1:1HubSpot 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
Nutshell
Account
1:1HubSpot 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
Nutshell
Lead
1:1HubSpot 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
Nutshell
Lead Stage
lossyEach 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
Nutshell
Pipeline
lossyHubSpot'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
Nutshell
User
1:1HubSpot 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
Nutshell
Activity (Email)
1:1HubSpot 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
Nutshell
Activity (Call)
1:1HubSpot 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
Nutshell
Activity (Meeting)
1:1HubSpot 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
Nutshell
Note
1:1HubSpot 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
Nutshell
Task
1:1HubSpot 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
Nutshell
Product
1:1HubSpot 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
Nutshell
Lead Product
1:1HubSpot 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.
| HubSpot | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Lead1:1 | Fully supported | |
| Deal Stage | Lead Stagelossy | Fully supported | |
| Pipeline | Pipelinelossy | Fully supported | |
| Owner | User1:1 | Fully supported | |
| Engagement: Email | Activity (Email)1:1 | Fully supported | |
| Engagement: Call | Activity (Call)1:1 | Fully supported | |
| Engagement: Meeting | Activity (Meeting)1:1 | Fully supported | |
| Engagement: Note | Note1:1 | Fully supported | |
| Engagement: Task | Task1:1 | Fully supported | |
| Product | Product1:1 | Fully supported | |
| Line Item | Lead Product1:1 | Fully supported |
Gotchas + challenges
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 gotchas
Marketing Contacts billing model is migration-critical
Feature tier gating is not visible until onboarding
Mandatory onboarding fees inflate year-one cost
HubSpot CSV importer cannot migrate engagements or attachments
Custom objects require Enterprise and a pre-existing schema
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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
HubSpot
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across HubSpot and Nutshell.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
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
HubSpot exposes a bulk API — large-volume migrations stream efficiently.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during HubSpot to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your HubSpot to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave HubSpot
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.