CRM migration
Field-level mapping, validation, and rollback between Close and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Close
Source
Nutshell
Destination
Compatibility
7 of 12
objects map 1:1 between Close and Nutshell.
Complexity
BStandard
Timeline
2-4 weeks
Overview
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.
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.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Nutshell
Lead
1:1Close 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
Nutshell
Contact
1:1Close 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
Nutshell
Company
1:1Close 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
Nutshell
Opportunity
1:1Close 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
Nutshell
Pipeline
lossyClose 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
Nutshell
Stage
lossyClose 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
Nutshell
Call
1:1Close 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
Nutshell
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
Nutshell
Email or Note
lossyClose 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
Nutshell
Task
1:1Close 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
Nutshell
Custom Field
lossyCustom 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
Nutshell
Note with metadata
lossyClose 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.
| Close | Nutshell | Compatibility | |
|---|---|---|---|
| Lead | Lead1:1 | Fully supported | |
| Contact | Contact1:1 | Fully supported | |
| Organisation | Company1:1 | Fully supported | |
| Opportunity | Opportunity1:1 | Fully supported | |
| Pipeline | Pipelinelossy | Fully supported | |
| Pipeline Stage | Stagelossy | Fully supported | |
| Activity: Call | Call1:1 | Fully supported | |
| Activity: Email | Email1:1 | Fully supported | |
| Activity: SMS | Email or Notelossy | Fully supported | |
| Activity: Task | Task1:1 | Fully supported | |
| Custom Field | Custom Fieldlossy | Fully supported | |
| Custom Activity | Note with metadatalossy | 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.
Close gotchas
CSV exports drop all activity history silently
Smart Views can only export from the Leads tab
Workflows gatekept behind Growth and Scale plans
Custom Activities require strict dependency ordering
Rate limits enforced per endpoint group
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 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.
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.
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.
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.
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
Close
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 3 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 Close and Nutshell.
Object compatibility
3 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
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
Close doesn't expose a bulk API — REST + parallelization used for high-volume runs.
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 Close to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your Close 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 Close
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.