CRM migration
Field-level mapping, validation, and rollback between LionDesk and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
LionDesk
Source
Nutshell
Destination
Compatibility
14 of 14
objects map 1:1 between LionDesk and Nutshell.
Complexity
BStandard
Timeline
24–72 hours
Overview
LionDesk and Nutshell both organize data around Person/Contact, Company/Account, and Deal/Pipeline entities, but the platforms diverge on drip campaign handling, contact-to-company relationships, and custom field architecture. LionDesk stores drip sequences as campaign objects tied to contacts; Nutshell handles email sequences through its Sales Email automation in the Pro tier and does not replicate LionDesk's real-estate-specific drip mechanics. We map LionDesk contacts to Nutshell People, LionDesk companies to Nutshell Companies, and LionDesk deals to Nutshell Deals using pipeline stage value mapping. Custom fields — defined in LionDesk with data_type values of Text, Number, Date, or Dollar Amt — migrate to Nutshell custom fields on the corresponding Person, Company, or Lead tabs. The migration runs via read-only API access to LionDesk, with field-level validation on a sample slice before the full cutover. Drip campaigns, texting automations, and video email configurations do not transfer; we export campaign definitions as structured JSON for manual rebuild in Nutshell's sequence tools. Owner resolution matches LionDesk user emails to Nutshell user accounts. Delta pickup captures in-flight changes during the cutover window.
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 LionDesk 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.
LionDesk
Contact
Nutshell
Person
1:1LionDesk contacts map 1:1 to Nutshell People. All standard fields (name, email, phone, address, title) transfer directly. Nutshell People require a Company link — contacts without a primary company in LionDesk attach to a placeholder 'Unassigned' company or get a placeholder company record created during migration.
LionDesk
Contact (drip_enrolled flag)
Nutshell
Person (custom field)
1:1LionDesk tracks drip enrollment status as a contact property. Nutshell has no native drip enrollment field. We preserve this as a custom checkbox field (Drip_Enrolled__c) on the Person object for reporting and to guide rebuild of sequences in Nutshell Sales Email.
LionDesk
Company
Nutshell
Company
1:1LionDesk companies map directly to Nutshell Companies, preserving fields such as name, domain/website, address, industry, employee count, and phone. Parent‑company hierarchies are transferred to Nutshell's parent company field; when a parent does not exist, FlitStack AI creates a placeholder parent record. Multi‑company contacts are linked to their primary company, with any secondary associations stored in a custom field for reference.
LionDesk
Deal
Nutshell
Deal
1:1LionDesk deals map to Nutshell Deals. Deal name, amount, stage name, and expected close date transfer directly. Stage names are mapped value-by-value to Nutshell pipeline stages. Deal owner maps to Nutshell user by email match. Nutshell supports up to 8 pipeline stages — LionDesk stages exceeding this require consolidation.
LionDesk
Deal stage
Nutshell
Deal pipeline stage
1:1LionDesk deal stage values map to Nutshell pipeline stage values. Each LionDesk stage name is matched to the closest Nutshell stage; if no match exists, the stage is created as a new Nutshell stage. Stage order and probability weights are preserved as custom fields if Nutshell's default weighting does not match.
LionDesk
Task
Nutshell
Activity
1:1LionDesk tasks migrate to Nutshell Activities, preserving subject, due date, completed flag, and assigned user. Task type (call, email, meeting) is stored in the Activity type field, while any description or notes are written to the activity body. Owner resolution uses the email match logic; if a user is missing, the activity is assigned to the migration admin. Recurring tasks are treated as a series of activity records in Nutshell.
LionDesk
Note
Nutshell
Note
1:1LionDesk notes migrate to Nutshell Notes attached to the matching Person, Company, or Deal record. The note body, author, and creation timestamp are transferred directly, and any HTML formatting is preserved as Rich when the export supports it. The linked record type (Person, Company, or Deal) is inferred from LionDesk's association, and if a note references multiple entities, FlitStack AI creates separate Note records for each link to keep context.
LionDesk
Email (sent from LionDesk)
Nutshell
Activity (email type)
1:1LionDesk email records become Nutshell Activity records of type email, preserving subject, body preview, send date, and recipient. If the export includes the HTML body, FlitStack AI stores it as a note attachment on the activity, and any file attachments are uploaded to Nutshell’s file storage. Emails are linked to the correct Person, Company, or Deal using LionDesk’s link data, and the sender is matched to a Nutshell user.
LionDesk
Call log
Nutshell
Activity (call type)
1:1LionDesk call logs become Nutshell Activities of type call, transferring duration, call date, direction, and outcome notes into the activity description. The assigned owner is resolved by email match; if no match is found the activity is assigned to the migration admin. Call recordings are detected and flagged for manual upload to Nutshell’s file storage, and any associated notes are preserved as activity attachments to keep the full call context.
LionDesk
Drip Campaign
Nutshell
No equivalent
1:1LionDesk drip campaigns have no direct Nutshell equivalent. Nutshell Sales Email (Pro tier) handles sequences differently — triggers are based on pipeline stage entry rather than campaign enrollment rules. We export drip campaign definitions as structured JSON including step order, delay intervals, and enrollment criteria for manual rebuild in Nutshell.
LionDesk
Text Message / SMS
Nutshell
Activity (note or external sync)
1:1LionDesk SMS records have no native Nutshell equivalent. SMS threads can be preserved as Notes on the Person record, but Nutshell's built-in engagement tools do not include SMS. Teams using LionDesk texting should configure Nutshell's SMS integration separately after migration.
LionDesk
Custom Field (Text, Number, Date, Dollar Amt)
Nutshell
Custom Field
1:1LionDesk custom fields carry explicit data_type metadata. Text fields map to Nutshell text custom fields; Number to Nutshell number fields; Date to Nutshell date fields; Dollar Amt to Nutshell currency fields. Each custom field is created on the corresponding Nutshell tab (Person, Company, or Lead) before the full migration runs.
LionDesk
User / Owner
Nutshell
User
1:1LionDesk owner IDs resolve to Nutshell users by email address match. Unmatched owners are flagged before migration — teams either invite them to Nutshell or assign records to a designated migration admin user. This ensures no record lands without a valid Nutshell owner.
LionDesk
Video Email
Nutshell
File attachment
1:1LionDesk video email attachments are stored as files in LionDesk's storage. These files download and re-upload to Nutshell's file storage, attached to the corresponding Person record. Video playback functionality is not preserved — Nutshell does not have a native video email player.
| LionDesk | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person1:1 | Fully supported | |
| Contact (drip_enrolled flag) | Person (custom field)1:1 | Fully supported | |
| Company | Company1:1 | Fully supported | |
| Deal | Deal1:1 | Fully supported | |
| Deal stage | Deal pipeline stage1:1 | Fully supported | |
| Task | Activity1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Email (sent from LionDesk) | Activity (email type)1:1 | Fully supported | |
| Call log | Activity (call type)1:1 | Fully supported | |
| Drip Campaign | No equivalent1:1 | Fully supported | |
| Text Message / SMS | Activity (note or external sync)1:1 | Fully supported | |
| Custom Field (Text, Number, Date, Dollar Amt) | Custom Field1:1 | Fully supported | |
| User / Owner | User1:1 | Fully supported | |
| Video Email | File attachment1: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.
LionDesk gotchas
LionDesk discontinuation as of September 2025
Drip campaign automation does not transfer between CRMs
SMS and video email assets are LionDesk-hosted
Bulk export requires API pagination
Custom field type enforcement at write time
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
Extract LionDesk data via API and audit custom field inventory
FlitStack AI connects to LionDesk via read-only API access and pulls all contacts, companies, deals, tasks, notes, activities, and custom field definitions. We catalog every custom field with its data_type (Text, Number, Date, Dollar Amt) and assign each to the correct Nutshell tab (Person, Company, or Lead). The audit report identifies records with missing required fields, duplicate email addresses, and N:N company associations that will collapse to primary links.
Create Nutshell custom fields and validate pipeline stage mapping
Based on the custom field inventory, we create Nutshell custom fields on the appropriate tabs before any data is written. We also document the LionDesk stage-to-Nutshell pipeline stage value map and surface it for your review. If your LionDesk setup exceeds 8 pipeline stages, we flag the consolidation requirement and propose a mapping. Owner resolution matches LionDesk user emails to existing Nutshell users or flags unmatched accounts for team action.
Run a sample migration with field-level diff
A representative sample — typically 200–500 records covering contacts, companies, deals, and activities — migrates first. We generate a field-level diff comparing source values to destination values so you can verify that custom field mapping, stage values, company links, and owner resolution all landed correctly. You approve the sample before the full run commits. Drip campaign definitions are exported as JSON at this stage for rebuild reference.
Execute full migration with delta-pickup cutover
The full migration runs against Nutshell's API. Records write in dependency order: Companies first, then People with company links, then Deals with primary contact links, then Activities. A delta-pickup window of 24–48 hours captures any LionDesk records created or modified during the cutover. All operations are logged to an audit trail, and one-click rollback is available if reconciliation reveals a mapping error.
Deliver reconciliation report and rebuild reference package
Post-migration, we deliver a reconciliation report showing record counts by object, error rates, and any fields that failed validation. The drip campaign export package includes structured JSON for each campaign, step order, delay logic, and enrollment rules — ready for your team to rebuild in Nutshell Sales Email. We also provide a custom field mapping spreadsheet as a living reference for ongoing Nutshell administration.
Platform deep dives
LionDesk
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 LionDesk 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
LionDesk: Not publicly documented in available developer documentation.
Data volume sensitivity
LionDesk 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 LionDesk to Nutshell migration scoping. Not seeing yours? Book a call.
Walk through your LionDesk 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 LionDesk
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.