Migrate your Nutshell data
All the CRM you need, none of the bloat. Pipelines, email sequences, and reporting that small sales teams can master in an afternoon.
Migrating to Nutshell? Jump to sources →
In its favor
Why people choose Nutshell
The signal that keeps Nutshell on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
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.
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.
Reasons to switch
Why people leave Nutshell
The recurring reasons buyers give for replacing Nutshell. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Nutshell fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Nutshell pricing overview
Nutshell uses a per-seat model with annual billing. Costs add up quickly due to per-company add-ons for Email Marketing ($5/month), SMS ($15/month), Nutshell IQ ($37/month), and Forms ($67/month). The Foundation tier has significant feature restrictions, so most professional sales teams require the Pro or Business tier.
Foundation
Tier 1 of 4
$13/user/month (annual)
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Nutshell's schedule — see our quote-based pricing →
What gets migrated
Nutshell object support
Object-by-object support for Nutshell migrations. Per-pair details surface during scoping.
People
Fully supportedPeople records are the core contact object in Nutshell, holding name, email, phone, address, and standard fields. We extract all standard fields via API and map them directly to Contacts or Leads in destination CRMs. Custom fields per Person are supported and mapped 1:1.
Companies
Fully supportedCompanies represent organizations and serve as the parent record for People in Nutshell's flat hierarchy. We map Company records to Accounts in destination CRMs, preserving the company-level custom fields and any associated People links.
Leads
Mapping requiredLeads in Nutshell are distinct records separate from People, with their own custom fields and lifecycle. We merge Leads into Contacts or map them to a separate Leads object depending on destination capabilities, preserving Lead source and status as custom Contact properties.
Activities
Fully supportedActivities capture calls, emails, meetings, and tasks tied to People or Companies. We extract the full activity timeline per record and recreate it as Activities or Engagements in the destination, maintaining the date, type, and notes.
Pipelines
Fully supportedNutshell supports multiple pipelines, each with configurable stages. We extract pipeline definitions including stage names, order, and win/loss status, then recreate them in the destination CRM using the equivalent pipeline configuration interface.
Pipeline Stages
Mapping requiredStage-level data including probability, stage order, and stage-specific automation triggers are extracted. We map these to destination stage definitions but note that probability percentages and automation triggers may require manual reconfiguration post-migration.
Custom Fields
Fully supportedCustom fields can be created for Companies, People, and Leads via Settings. We enumerate all custom field definitions across objects before migration and create matching custom fields in the destination CRM, preserving field type and option lists.
Attachments
Not in this platformThe Nutshell API exposes attachment metadata and references but does not return binary file blobs directly. We export attachment filenames and URLs but cannot automatically download and re-upload files. Customers must manually re-attach files post-migration or use a separate file transfer method.
Tags
Mapping requiredNutshell uses a tag-based taxonomy for categorizing People and Companies. Tags are exported and mapped to Tags or Labels in destination CRMs, but tag hierarchy (if any) is flattened during transfer.
Users/Owners
Mapping requiredUsers in Nutshell serve as record owners and appear in activity logs. We map Nutshell users to Owner or User records in the destination CRM. Users without email access in the destination may be mapped as historical owners rather than active seats.
Email Sequences
Not in this platformEmail sequences are stored as automation configurations on the Pro and Business plans. These are not exportable via API. We do not migrate sequences—we migrate the People and their activity history so follow-up can be restarted in the destination CRM.
Nutshell IQ (Enrichment)
Not in this platformNutshell IQ provides contact and company data enrichment via a credit-based system. Enrichment data is not separately stored as a migrateable field—it is displayed inline in the Nutshell UI. We do not attempt to transfer IQ enrichment data.
| Object | Support | Notes |
|---|---|---|
| People | Fully supported | People records are the core contact object in Nutshell, holding name, email, phone, address, and standard fields. We extract all standard fields via API and map them directly to Contacts or Leads in destination CRMs. Custom fields per Person are supported and mapped 1:1. |
| Companies | Fully supported | Companies represent organizations and serve as the parent record for People in Nutshell's flat hierarchy. We map Company records to Accounts in destination CRMs, preserving the company-level custom fields and any associated People links. |
| Leads | Mapping required | Leads in Nutshell are distinct records separate from People, with their own custom fields and lifecycle. We merge Leads into Contacts or map them to a separate Leads object depending on destination capabilities, preserving Lead source and status as custom Contact properties. |
| Activities | Fully supported | Activities capture calls, emails, meetings, and tasks tied to People or Companies. We extract the full activity timeline per record and recreate it as Activities or Engagements in the destination, maintaining the date, type, and notes. |
| Pipelines | Fully supported | Nutshell supports multiple pipelines, each with configurable stages. We extract pipeline definitions including stage names, order, and win/loss status, then recreate them in the destination CRM using the equivalent pipeline configuration interface. |
| Pipeline Stages | Mapping required | Stage-level data including probability, stage order, and stage-specific automation triggers are extracted. We map these to destination stage definitions but note that probability percentages and automation triggers may require manual reconfiguration post-migration. |
| Custom Fields | Fully supported | Custom fields can be created for Companies, People, and Leads via Settings. We enumerate all custom field definitions across objects before migration and create matching custom fields in the destination CRM, preserving field type and option lists. |
| Attachments | Not in this platform | The Nutshell API exposes attachment metadata and references but does not return binary file blobs directly. We export attachment filenames and URLs but cannot automatically download and re-upload files. Customers must manually re-attach files post-migration or use a separate file transfer method. |
| Tags | Mapping required | Nutshell uses a tag-based taxonomy for categorizing People and Companies. Tags are exported and mapped to Tags or Labels in destination CRMs, but tag hierarchy (if any) is flattened during transfer. |
| Users/Owners | Mapping required | Users in Nutshell serve as record owners and appear in activity logs. We map Nutshell users to Owner or User records in the destination CRM. Users without email access in the destination may be mapped as historical owners rather than active seats. |
| Email Sequences | Not in this platform | Email sequences are stored as automation configurations on the Pro and Business plans. These are not exportable via API. We do not migrate sequences—we migrate the People and their activity history so follow-up can be restarted in the destination CRM. |
| Nutshell IQ (Enrichment) | Not in this platform | Nutshell IQ provides contact and company data enrichment via a credit-based system. Enrichment data is not separately stored as a migrateable field—it is displayed inline in the Nutshell UI. We do not attempt to transfer IQ enrichment data. |
Gotchas
What to watch for in Nutshell migrations
Issues we've hit on past Nutshell migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
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
| Severity | Issue |
|---|---|
| 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 |
Leaving Nutshell?
Where Nutshell customers move next
11 destinations Nutshell can migrate to.
Coming to Nutshell?
Migrating in from another CRM
856 sources can migrate into Nutshell.
How a Nutshell migration works
Four steps, Nutshell-specific
Connect
HTTP Basic auth: username = company domain or email, password = API key. OAuth user-impersonation supported for specific integrations (e.g., Zapier). into Nutshell. Scopes limited to read-only on the data we move.
Map
We translate Nutshell-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Nutshell quirks before production.
Migrate
Full migration with Nutshell rate-limit handling. Rollback available throughout.
FAQ
Nutshell migration FAQ
Answers to the questions buyers ask most during Nutshell migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Nutshell.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Nutshell setup and destination — written quote back within a business day.