CRM migration

Migrate from LionDesk to Nutshell

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

LionDesk logo

LionDesk

Source

Nutshell

Destination

Nutshell logo

Compatibility

100%

14 of 14

objects map 1:1 between LionDesk and Nutshell.

Complexity

BStandard

Timeline

24–72 hours

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

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.

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

LionDesk logo

LionDesk

What's pushing teams away

  • Customer support is consistently unresponsive — Capterra support scores of 3.6/5 and Trustpilot at 2.8/5 reflect a pattern of unanswered inquiries and unreachable staff.
  • Users report that add-on costs drive monthly spend significantly above the advertised entry price, making budgeting unpredictable.
  • Multiple users describe the interface as visually dated and functionally basic — suitable for simple workflows but limiting for teams or advanced users.
  • Annual prepayments are difficult to recover; users report refund refusals even when canceling soon after an annual commitment.
  • The platform has a history of glitches and stability issues that agents describe as more trouble than the time savings justify.

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

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

maps to

Nutshell

Person

1:1
Fully supported

LionDesk 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)

maps to

Nutshell

Person (custom field)

1:1
Fully supported

LionDesk 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

maps to

Nutshell

Company

1:1
Fully supported

LionDesk 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

maps to

Nutshell

Deal

1:1
Fully supported

LionDesk 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

maps to

Nutshell

Deal pipeline stage

1:1
Fully supported

LionDesk 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

maps to

Nutshell

Activity

1:1
Fully supported

LionDesk 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

maps to

Nutshell

Note

1:1
Fully supported

LionDesk 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)

maps to

Nutshell

Activity (email type)

1:1
Fully supported

LionDesk 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

maps to

Nutshell

Activity (call type)

1:1
Fully supported

LionDesk 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

maps to

Nutshell

No equivalent

1:1
Fully supported

LionDesk 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

maps to

Nutshell

Activity (note or external sync)

1:1
Fully supported

LionDesk 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)

maps to

Nutshell

Custom Field

1:1
Fully supported

LionDesk 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

maps to

Nutshell

User

1:1
Fully supported

LionDesk 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

maps to

Nutshell

File attachment

1:1
Fully supported

LionDesk 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.

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.

LionDesk logo

LionDesk gotchas

High

LionDesk discontinuation as of September 2025

High

Drip campaign automation does not transfer between CRMs

Medium

SMS and video email assets are LionDesk-hosted

Medium

Bulk export requires API pagination

Low

Custom field type enforcement at write time

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

  • Drip campaigns and texting automations do not migrate and require manual rebuild

    LionDesk's drip campaign engine is the primary differentiator for real estate agents — it stores sequence steps, enrollment triggers, and per-contact drip status in a campaign object that has no equivalent in Nutshell. Nutshell's Sales Email module (Pro tier) handles sequences differently: triggers fire on pipeline stage entry rather than campaign enrollment rules, and Nutshell has no native SMS tool. FlitStack AI exports all drip campaign definitions as structured JSON including step order, delay intervals, subject lines, and body templates, giving your team a rebuild reference for Nutshell's sequence builder. Texting integrations must be reconnected with Nutshell's SMS partners after go-live.

  • LionDesk contact-to-company N:N relationships collapse to a single primary link in Nutshell

    LionDesk allows a contact to be associated with multiple companies simultaneously — an agent may work with a buyer and a seller on the same transaction. Nutshell People have a single primary Company link plus optional secondary relationships. We migrate the most-recently-modified company association as the primary link and surface additional company associations as custom fields on the Person record. Teams that rely heavily on multi-company contact roles should audit the Person records after migration and recreate additional associations manually in Nutshell.

  • LionDesk custom fields must be pre-created in Nutshell before the migration runs

    LionDesk defines custom fields with explicit data_type values (Text, Number, Date, Dollar Amt). Nutshell requires custom fields to be created on the appropriate Person, Company, or Lead tab before data can be written to them. The migration plan includes a custom field creation checklist with the correct data type for each LionDesk field. Fields created with the wrong type require re-migration of the affected records. This pre-creation step typically takes 1–2 hours in Nutshell's settings UI before the migration engine starts.

  • Video email files and attachments re-upload to Nutshell but lose playback context

    LionDesk's video email feature embeds video content as attachments on contact records. These files download from LionDesk storage and re-upload to Nutshell's file storage as standard attachments. The video file itself transfers intact, but LionDesk's built-in video player, play count tracking, and video-specific metadata do not. Recipients of video emails in LionDesk may need to receive a new video message from Nutshell's email integration to preserve the same engagement experience.

  • LionDesk's single pipeline model may require stage consolidation in Nutshell

    LionDesk supports one pipeline with configurable stages. Nutshell's Deal pipeline also defaults to a single pipeline but allows teams to manage stage count and naming. If your LionDesk setup uses more than 8 pipeline stages, the excess stages must be consolidated into Nutshell's 8-stage maximum before the migration plan's value mapping is finalized. Stage consolidation decisions should involve the sales manager to determine which LionDesk stages map to which Nutshell stages and whether probability weights need adjustment.

Migration approach

Six steps for a successful LionDesk to Nutshell data migration

  1. 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.

  2. 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.

  3. 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.

  4. 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.

  5. 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

Context on both ends of the pair

LionDesk logo

LionDesk

Source

Strengths

  • Entry price of $21/month is among the lowest for any full-featured real estate CRM with drip campaigns and texting included.
  • Built-in texting and video email are genuine differentiators that keep agent communication centralized without third-party add-ons.
  • Pre-built real estate drip templates and lead tracking workflows reduce initial setup time for agents unfamiliar with CRM configuration.
  • Open API with OAuth 2.0 authentication allows third-party integrations and programmatic data access for migration tooling.

Weaknesses

  • Support quality is consistently poor across review platforms — agents report long response times and unresolved tickets.
  • The UI is described as basic and visually dated, limiting usability for teams or agents with complex workflows.
  • Annual prepayment refund refusals create a financial risk for agents who need to exit the platform early.
  • LionDesk was discontinued in September 2025, making long-term platform stability a migration urgency factor rather than a future consideration.
  • No publicly documented bulk export or bulk API capability means large contact databases may require iterative API extraction rather than a single pull.
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 LionDesk 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

    LionDesk: Not publicly documented in available developer documentation.

  • Data volume sensitivity

    B

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

Estimator

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

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

Can't find your answer?

Walk through your LionDesk to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most LionDesk-to-Nutshell migrations complete in 24–72 hours for under 25,000 total records. Larger databases with 25,000–100,000 records or complex custom field setups extend to 3–7 days. The custom field pre-creation step (Nutshell side) typically takes 1–2 hours before migration begins. The sample migration validation phase adds another 4–8 hours depending on record diversity. Timeline is primarily driven by total record count, custom field volume, and how many drip campaign definitions need JSON export for rebuild reference.

Adjacent paths

Related migrations to explore

Ready when you are

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