CRM migration

Migrate from Close to Nutshell

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

Close logo

Close

Source

Nutshell

Destination

Nutshell logo

Compatibility

58%

7 of 12

objects map 1:1 between Close and Nutshell.

Complexity

BStandard

Timeline

2-4 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Close and Nutshell share a similar record model — Leads, Contacts, Opportunities, and Pipelines — but the activity export mechanism and Custom Activity handling differ significantly. Close's CSV export silently drops call, email, SMS, and task history, so we always request JSON for activity-bearing records before any migration scoping begins. Nutshell's standard import flow (which runs via Import2) supports Leads, Contacts, Companies, and Opportunities from CSV, but large engagement histories require API-based sequencing rather than the standard CSV loader. We map Close's Custom Activities in a three-phase pipeline (type, type-scoped fields, then records) matching the dependency order Close enforces. Workflows built in Close's Growth or Scale plans do not migrate to Nutshell; we deliver a written inventory for the customer's admin to rebuild.

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

Close logo

Close

What's pushing teams away

  • The feature set is deliberately narrower than enterprise CRMs — advanced reporting, deep customisation, and workflow complexity lag behind Salesforce and HubSpot.
  • Mobile app navigation receives consistent complaints; users report missed call notifications and the need to reopen the app frequently to stay current.
  • Teams needing native Slack integration without a Zapier workaround find the gap frustrating, especially at the lower pricing tiers.
  • Some users report that Close lacks Serbian number support and has limited inbox management compared to dedicated helpdesk tools.

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 Close objects map to Nutshell

Each row shows how a Close 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.

Close

Lead

maps to

Nutshell

Lead

1:1
Fully supported

Close Lead records migrate directly to Nutshell Lead. We preserve the lead status label, owner assignment (via email match to Nutshell User), and all standard fields (name, email, phone, address). Close's lead status values map to Nutshell's Lead Status picklist, and any custom Lead Custom Fields are pre-created in Nutshell before the import phase begins.

Close

Contact

maps to

Nutshell

Contact

1:1
Fully supported

Close Contact records migrate to Nutshell Contact, linked to the corresponding Nutshell Company (the Close Organisation becomes the Nutshell Company). The Contact-Company lookup is resolved at migration time by matching the Close Organisation name to the Nutshell Company record created in the previous phase. Contact owner resolves by email match to Nutshell User.

Close

Organisation

maps to

Nutshell

Company

1:1
Fully supported

Close Organisation records map to Nutshell Company. Company name, domain, address, and industry fields migrate 1:1. We create the Company record first so that Contact imports can resolve the Company lookup immediately. If multiple Close Contacts share the same Organisation, they all link to the single Nutshell Company record.

Close

Opportunity

maps to

Nutshell

Opportunity

1:1
Fully supported

Close Opportunities map to Nutshell Opportunities with value, stage, expected close date, and owner preserved. The Close pipeline reference maps to Nutshell's single pipeline structure. If the Close account has multiple pipelines, we consolidate them into one Nutshell pipeline and document the original pipeline name on a custom field for reference. Close Custom Fields on Opportunities are pre-created in Nutshell before Opportunity import.

Close

Pipeline

maps to

Nutshell

Pipeline

lossy
Fully supported

Close Pipelines are containers for stages. Nutshell supports one pipeline per workspace, so if the Close account uses multiple pipelines, we create a single Nutshell pipeline and map each Close pipeline to a named group within it, preserving the original pipeline name as a custom field on each Opportunity. Stage order and probability weights migrate to Nutshell stage configuration.

Close

Pipeline Stage

maps to

Nutshell

Stage

lossy
Fully supported

Close Pipeline Stages migrate as Nutshell Stages within the consolidated pipeline. Stage display names and ordering are preserved. Stage probability weights map to Nutshell's stage probability field. If a Close pipeline has custom stage columns beyond the standard name and probability, those migrate as Opportunity Custom Fields.

Close

Activity: Call

maps to

Nutshell

Call

1:1
Fully supported

Close call logs migrate to Nutshell Call records linked to the parent Contact or Lead. We use the JSON export from Close because CSV export omits all activity data. Call duration, disposition, direction (inbound/outbound), and the recording URL migrate to Nutshell Call fields. Activity timestamps are preserved to maintain the chronological timeline.

Close

Activity: Email

maps to

Nutshell

Email

1:1
Fully supported

Close email engagements migrate to Nutshell Email records. The email body, subject, direction, and timestamp migrate. Recipients and CC addresses resolve to Nutshell Contact or Lead records via email address matching. If the recipient Contact has not yet been migrated, the email is held in a queue until the Contact import completes.

Close

Activity: SMS

maps to

Nutshell

Email or Note

lossy
Fully supported

Close SMS engagements have no direct Nutshell equivalent, so we migrate them as Nutshell Email records with the SMS label flagged or as Note records with the sms_source__c custom field set. The customer chooses the preferred representation during scoping. We always use Close's JSON export to capture SMS; CSV does not include it.

Close

Activity: Task

maps to

Nutshell

Task

1:1
Fully supported

Close Tasks migrate to Nutshell Task records with status, priority, due date, and assigned owner preserved. Task assignment resolves by email match to the Nutshell User. Open and completed task status carries over directly. Task body migrates as the Nutshell Task description.

Close

Custom Field

maps to

Nutshell

Custom Field

lossy
Fully supported

Custom Fields exist per-object in Close (Lead Custom Fields, Contact Custom Fields, Opportunity Custom Fields). We read the field definition — type (text, number, date, picklist, checkbox), choice options, required flag — via the Close API and create matching fields in Nutshell before importing any records. Picklist choice labels are preserved; the customer confirms label parity during scoping.

Close

Custom Activity

maps to

Nutshell

Note with metadata

lossy
Fully supported

Close Custom Activities are user-defined activity types with their own schema. Nutshell does not have a Custom Activity Type registry, so we migrate Custom Activity instances as Nutshell Note records with a custom field nut_custom_activity_type__c carrying the original Close activity type name, and any type-specific Custom Fields carried as additional custom Note fields. We sequence the import as: create Nutshell custom fields, then import Custom Activity records. This is the highest-effort object in the mapping.

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.

Close logo

Close gotchas

High

CSV exports drop all activity history silently

Medium

Smart Views can only export from the Leads tab

Medium

Workflows gatekept behind Growth and Scale plans

Medium

Custom Activities require strict dependency ordering

Low

Rate limits enforced per endpoint group

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

  • CSV export silently drops all activity history

    Close's CSV export format intentionally omits call logs, emails, SMS, and tasks. Any customer who has been using CSV exports for their data inventory will have a full activity gap if we rely on the CSV alone. We always request JSON export from Close for activity-bearing records. During scoping, we ask whether the customer has used CSV exports exclusively and flag that their activity history needs to be re-exported as JSON before migration scoping begins. If the JSON is unavailable (account deleted, data expired), we document the gap explicitly.

  • Smart Views only export from the Leads tab

    Close exports are only accessible from Smart Views created in the Leads tab. Smart Views built from the Contacts tab produce no export button in the UI. We handle this by querying Leads via the Close API directly rather than relying on Smart View exports, ensuring all Lead records are retrieved regardless of how the customer's saved views are structured. Contacts export is handled separately via the Contacts API endpoint.

  • Close Workflows do not migrate to Nutshell

    Close Automated Workflows — available on Growth ($99/seat) and Scale ($139/seat) plans — contain rule logic tightly coupled to Close's event model and have no direct Nutshell equivalent. We do not migrate Workflows. During scoping, we ask the customer to document all active Workflows and we deliver a written inventory listing each Workflow's trigger, conditions, and actions with a recommended Nutshell workflow rule equivalent. The customer's admin rebuilds them post-migration.

  • Custom Activities require strict three-phase dependency ordering

    A Custom Activity Type must exist in the destination before any type-scoped Custom Field, and both must exist before any Custom Activity record can be imported. Attempting to import out of order returns validation errors. We sequence Custom Activity migration as a three-phase pipeline: create the Custom Activity Type metadata, create the type-scoped Custom Fields in Nutshell, then import the activity records. This adds a minimum of one additional migration phase and requires upfront schema discovery of every Custom Activity Type in the Close account.

  • Multiple Close pipelines must consolidate into one Nutshell pipeline

    Close supports multiple independent Pipelines, each with their own stages and probability weights. Nutshell uses a single pipeline per workspace. If the customer has more than one Close Pipeline, we consolidate them into one Nutshell pipeline and preserve the original pipeline name as a custom Opportunity field. Stage names that duplicate across pipelines require renaming or scoping. We design the consolidation map during scoping and validate with the customer before migration begins.

Migration approach

Six steps for a successful Close to Nutshell data migration

  1. Discovery and export verification

    We audit the Close account for tier (Solo through Scale), record counts per object (Leads, Contacts, Organisations, Opportunities), pipeline count and stage definitions, Custom Field definitions per object, Custom Activity Type list, active Workflow count, and engagement volume. We specifically verify that the customer has access to JSON exports for activity-bearing records — if they have only used CSV exports, we flag this and request a re-export before scoping finalises. We also extract the full Close field schema via the API to map every custom field before migration begins.

  2. Schema design and Nutshell field pre-creation

    We design the destination schema in Nutshell. This includes creating all Lead Custom Fields, Contact Custom Fields, and Opportunity Custom Fields with type-matched Nutshell field types before any record import. For Custom Activities, we create the type name and type-scoped fields in Nutshell first. We configure the consolidated Pipeline with stage names, ordering, and probability weights mapped from Close. If the customer uses Close's Serbian number format or any non-standard phone formatting, we document it for normalisation during the transform phase.

  3. Export, transform, and reconciliation

    We pull all records from Close via the API: Leads, Contacts, Organisations, Opportunities, Users, and all activity types (Calls, Emails, SMS, Tasks) via JSON. The transform layer resolves: Organisation-to-Company linking for Contacts, Owner-to-User matching by email, pipeline and stage mapping, and Custom Field value normalisation. We run a reconciliation count (records out of Close, records in Nutshell) and spot-check 20-30 records against the source before proceeding to production migration.

  4. Production migration in dependency order

    We run production migration in record-dependency order: Companies (from Close Organisations), Leads, Contacts (with CompanyId resolved), Opportunities (with stage, owner, and pipeline resolved), Custom Fields already created, Custom Activity Types and type-scoped fields, Custom Activity records, Activity history (Calls, Emails, SMS, Tasks via batch API calls), Attachments and Call Recordings. Each phase emits a row-count reconciliation report before the next phase begins. Any records that fail validation are held in a error queue and retried after the batch completes.

  5. Cutover, delta sync, and Workflow handoff

    We freeze writes in Close 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 Custom Activity schema map and the Workflow inventory document to the customer's admin team with recommended Nutshell equivalents. We support a one-week hypercare window where we resolve any reconciliation issues raised by the customer's team. We do not rebuild Close Workflows as Nutshell automation rules inside the migration scope; that is a separate engagement or an internal admin task.

Platform deep dives

Context on both ends of the pair

Close logo

Close

Source

Strengths

  • Unified inbox combining email, SMS, and call history in a single thread per Lead or Contact.
  • Built-in dialer stack — Power Dialer and Predictive Dialer — without requiring a third-party VoIP integration.
  • Per-seat pricing with no separate marketing-contact billing model, making cost predictable as teams grow.
  • Clean API with structured endpoints for Leads, Contacts, Opportunities, and Custom Activities using API-key authentication.
  • Strong G2 rating (4.7/5 from 2,030 reviews) with consistent praise for ease of use and onboarding speed.

Weaknesses

  • Mobile app is widely criticised for navigation friction, missed notifications, and the need to reopen to refresh call status.
  • Feature set is intentionally lean — advanced custom reporting, deep customisation, and complex workflow logic are more limited than Salesforce or HubSpot.
  • Native Slack integration is absent without a Zapier or API workaround, frustrating teams that rely on Slack for sales team communication.
  • Custom Objects and Custom Activities are powerful but add migration complexity due to their dependency ordering requirements.
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. 3 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 Close and Nutshell.

  • Object compatibility

    B

    3 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

    Close: Per endpoint group with a lower limit on write operations; 429 response includes rate_reset value; limits enforced at the organisation level across all API keys.

  • Data volume sensitivity

    B

    Close doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

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

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

Can't find your answer?

Walk through your Close 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 Opportunities with no Custom Activities. Migrations with Custom Activities, large engagement histories (over 200,000 activity records), or multiple Close pipelines that require consolidation design move to six to ten weeks because of the three-phase Custom Activity pipeline and pipeline consolidation work. The Close account tier (Solo through Scale) does not significantly affect timeline.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Close.
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