CRM migration
Field-level mapping, validation, and rollback between SmartDesk and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
SmartDesk
Source
Nutshell
Destination
Compatibility
9 of 10
objects map 1:1 between SmartDesk and Nutshell.
Complexity
BStandard
Timeline
2-3 weeks
Overview
SmartDesk and Nutshell occupy different positions in the small-business CRM market. SmartDesk combines CRM, help desk, email marketing, and an AI assistant in a single subscription, which is appealing when teams want to minimize tool sprawl. Nutshell focuses on the sales CRM layer with a simpler object model (People, Companies, Deals, Activities, Campaigns) and is known for an interface that earns high adoption rates from sales reps who are not CRM power users. The primary migration challenge is that SmartDesk's integrated help desk and knowledge base have no direct Nutshell equivalent. We migrate the CRM core objects and preserve custom field definitions for pre-creation in Nutshell, but helpdesk Tickets and Knowledge Base Articles require a separate rebuild approach documented in the handoff package. Workflows, automations, and email marketing sequences do not migrate as code; we inventory every active workflow and sequence and deliver a written rebuild guide for your admin.
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 SmartDesk 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.
SmartDesk
Lead
Nutshell
Lead
1:1SmartDesk Leads map directly to Nutshell Leads. Lead Source and Lead Status stored as custom fields in SmartDesk migrate to Nutshell custom fields on the Lead object, which must be pre-created in the Nutshell admin panel before migration. Nutshell Lead custom fields support Text, Long Text, Currency, and Date types among others. We provide a custom field manifest listing every SmartDesk Lead property that lacks a native Nutshell equivalent so the customer can configure them in advance.
SmartDesk
Contact
Nutshell
Person
1:1SmartDesk Contacts map 1:1 to Nutshell People. The mapping preserves name, email, phone, address, and lifecycle stage. Custom contact properties defined in SmartDesk migrate to Nutshell custom fields on People, which the customer pre-creates before migration. Nutshell People records can be linked to a Company record via a lookup relationship established during migration.
SmartDesk
Account
Nutshell
Company
1:1SmartDesk Accounts map to Nutshell Companies. Industry classification, employee count, and any custom properties attached to the Account migrate as custom fields on the Nutshell Company. Company is imported before People so that the Company lookup relationship is satisfied at the moment of Person insert.
SmartDesk
Deal
Nutshell
Deal
1:1SmartDesk Deals map to Nutshell Deals. Deal name, value, stage, expected close date, and owner migrate directly. Pipeline and stage names require reconciliation because SmartDesk allows fully custom Pipelines and Stages while Nutshell has a configurable but more structured stage set. We enumerate SmartDesk's pipeline stages first, map each to the nearest Nutshell stage or create a new one, and flag any stage mismatch for customer review.
SmartDesk
Pipeline
Nutshell
Pipeline
lossySmartDesk Pipelines map to Nutshell Pipelines. Each SmartDesk pipeline becomes a Nutshell pipeline with its ordered stages. We perform a stage-name reconciliation pass before migration: stages that exist in Nutshell by default (New, Contacted, Qualified, etc.) are matched by name; stages with no Nutshell equivalent are created in the destination before Deals are imported. Stage probability values migrate as a custom field if required for reporting.
SmartDesk
Task
Nutshell
Task
1:1SmartDesk Tasks attached to Contacts or Deals migrate to Nutshell Tasks. Assignee, due date, status, and description preserve. Task linkage to the parent record (Person or Deal) is resolved at migration time via the Nutshell API relationship fields. Completed status maps directly from SmartDesk to Nutshell.
SmartDesk
Activity
Nutshell
Activity
1:1SmartDesk Activities (calls, emails, meetings, notes) logged against Contacts or Deals migrate to Nutshell Activities. Activity type, timestamp, body, and related person or deal migrate. Some SmartDesk activity metadata stored as custom fields requires pre-created custom fields in Nutshell. Activity timeline ordering is preserved by setting the activity timestamp to the original SmartDesk value.
SmartDesk
Campaign
Nutshell
Campaign
1:1SmartDesk Campaigns map to Nutshell Campaigns. Campaign name, type, status, start and end dates migrate. Email send and open tracking data does not migrate because it lives in the email delivery system rather than the CRM record. We recommend the customer configure email tracking separately in Nutshell after migration for future campaign performance data.
SmartDesk
Email Template
Nutshell
Email Template
1:1SmartDesk Email Templates migrate as static text assets with merge field placeholders preserved. Dynamic content or conditional logic embedded in templates may not function identically in Nutshell and requires manual post-migration review. We document every template with its merge fields and conditional logic so the customer can recreate or adapt them in Nutshell's template editor.
SmartDesk
User / Owner
Nutshell
User
1:1SmartDesk Users and Owners map to Nutshell Users by email address match. We extract every distinct owner referenced on Contacts, Companies, Deals, and Activities and attempt to match by email against the Nutshell destination. Users without a match enter a reconciliation queue for the customer's admin to provision in Nutshell before record import resumes. This step is a prerequisite for assigning Deals and Tasks to the correct owner.
| SmartDesk | Nutshell | Compatibility | |
|---|---|---|---|
| Lead | Lead1:1 | Fully supported | |
| Contact | Person1:1 | Fully supported | |
| Account | Company1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Pipeline | Pipelinelossy | Fully supported | |
| Task | Task1:1 | Fully supported | |
| Activity | Activity1:1 | Fully supported | |
| Campaign | Campaign1:1 | Fully supported | |
| Email Template | Email Template1:1 | Fully supported | |
| User / Owner | User1: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.
SmartDesk gotchas
No publicly documented public API endpoint reference
Pipeline stage count and naming differ between accounts
Custom Fields must be pre-created in the destination
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
Schema discovery and credentials
We request SmartDesk API access credentials or an admin-panel export to enumerate the live schema: objects, fields, custom field definitions, pipeline configurations, and record counts. Simultaneously, we enumerate the Nutshell destination: existing People fields, Company fields, Lead fields, Deal stages, pipelines, and any pre-existing custom fields. The output is a written schema delta showing which SmartDesk fields have native Nutshell counterparts, which require custom fields, and which have no equivalent.
Custom field pre-creation coordination
We deliver the custom field manifest to the customer with instructions for pre-creating each field in Nutshell. Fields are listed by target object (Person, Company, Lead), field name, and Nutshell field type (Text, Long Text, Currency, Date, etc.). The customer completes this step in their Nutshell admin panel before we begin the migration run. We validate that the fields exist in Nutshell before attempting to write data to them.
Pipeline and stage reconciliation
We enumerate SmartDesk Pipelines and Stages, then compare them against Nutshell's configured stages. Stages with matching names are linked directly. Stages with no Nutshell equivalent are created in the destination before Deal migration. We document the stage mapping for the customer's review and flag any semantic differences (e.g., a SmartDesk stage named 'Won' may map to Nutshell's 'Closed Won' or a custom equivalent).
Owner and User provisioning
We extract every distinct SmartDesk owner referenced on Contacts, Companies, Deals, and Activities and match by email against the Nutshell destination's User table. Owners without a matching Nutshell User enter a reconciliation queue. The customer's admin provisions any missing Users (active or inactive depending on whether the original SmartDesk user is still with the company). This step is required before Deal and Activity assignment can proceed.
Migration in dependency order
We run production migration in record-dependency order: Companies (from SmartDesk Accounts) first, then People (with CompanyId resolved via the Company lookup), then Leads, then Deals (with OwnerId, CompanyId, and stage resolved), then Activities, then Campaigns, then Tasks. Each phase emits a row-count reconciliation report before the next phase begins. We use Nutshell's REST API with rate-limit handling and exponential backoff for all writes.
Cutover, delta pass, and handoff package
We freeze SmartDesk 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 handoff package: workflow and automation inventory, email template inventory with merge field documentation, ticket and KB article inventory (for manual rebuild), and custom field manifest with any unmapped fields flagged. We support a five-business-day hypercare window for reconciliation issues. Post-migration admin training, workflow rebuild, and helpdesk setup are outside standard scope and require a separate engagement.
Platform deep dives
SmartDesk
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 SmartDesk 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
SmartDesk: Not publicly documented.
Data volume sensitivity
SmartDesk 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 SmartDesk to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your SmartDesk 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 SmartDesk
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.