CRM migration
Field-level mapping, validation, and rollback between LionDesk and Salesforce Sales Cloud. We move data and schema; workflows are rebuilt natively in Salesforce Sales Cloud.
LionDesk
Source
Salesforce Sales Cloud
Destination
Compatibility
15 of 16
objects map 1:1 between LionDesk and Salesforce Sales Cloud.
Complexity
BStandard
Timeline
48–72 hours
Overview
LionDesk targets solo agents and small brokerages with a $21–$83/month price point, offering basic contact management, drip campaigns, texting, and video email. Its data model uses flat contact and company objects with custom fields of type Text, Number, Date, or Dollar Amount. Salesforce Sales Cloud splits contacts into Lead and Contact objects, requires AccountId lookups on contacts, and uses record types with stage pick-lists scoped per type on opportunities. The migration carries all LionDesk contacts, companies, deals, and custom field values into Salesforce via the Bulk API, with owners resolved by email match. Custom field types (Dollar Amount, Date) map to Salesforce Number, Date, or Currency fields with the __c suffix. Drip campaigns and texting automations have no Salesforce equivalent and must be rebuilt as Salesforce Flow or Sales Engagement sequences post-migration. The delta-pickup window captures any LionDesk changes during cutover so Salesforce reflects your final source state at go-live.
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 Salesforce Sales Cloud, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
LionDesk
Contact
Salesforce Sales Cloud
Contact
1:1LionDesk contacts map 1:1 to Salesforce Contacts. Each LionDesk contact must resolve to an AccountId — if the contact has no primary company in LionDesk, we attach it to a default 'Unassigned Account' record or split to a Salesforce Lead based on your configured lifecycle rule.
LionDesk
Contact (with lead_status=Lead)
Salesforce Sales Cloud
Lead
1:manyLionDesk contacts flagged as leads by status map to Salesforce Leads. We apply your LionDesk lead-stage values to Salesforce Lead Status via value mapping, ensuring the qualification lifecycle carries forward. Unconverted leads land as Salesforce Leads; converted leads land as Contacts under the Account resolved from their primary company. Status values without a Salesforce equivalent are flagged for manual mapping before migration.
LionDesk
Company
Salesforce Sales Cloud
Account
1:1LionDesk companies map directly to Salesforce Accounts. Parent-child company hierarchies in LionDesk map to Account.ParentId, preserving ownership structure across levels. Multi-company contacts (LionDesk N:N associations) collapse to one primary AccountId on the Contact plus Account Contact Relations for secondary relationships, so the primary brokerage association is always clear.
LionDesk
Deal
Salesforce Sales Cloud
Opportunity
1:1LionDesk deals map to Salesforce Opportunities. Each deal's pipeline and stage map to a Salesforce Sales Process and RecordTypeId combination. If your LionDesk account uses multiple pipelines, we create corresponding record types in Salesforce before the migration runs. Deal owner, amount, and close date transfer directly without transformation.
LionDesk
Pipeline
Salesforce Sales Cloud
Sales Process + Record Type
1:1LionDesk's pipeline concept becomes a Salesforce Sales Process tied to a Record Type. One LionDesk pipeline = one Salesforce record type. Stage pick-list values are scoped per record type in Salesforce — we deliver a record-type setup plan so your admin can pre-create these before data lands.
LionDesk
Pipeline Stage
Salesforce Sales Cloud
Opportunity StageName
1:1Stage names map value-by-value from LionDesk to Salesforce Opportunity StageName. Stage probability and forecast category re-applied from Salesforce's stage configuration. HubSpot-style stage-entered timestamps preserved as custom datetime fields on the Opportunity.
LionDesk
Custom Field (Dollar Amount)
Salesforce Sales Cloud
Custom Field (Currency__c)
1:1LionDesk Dollar Amount custom fields require a Salesforce Currency field with the __c suffix and ISO currency code. We create the field during migration setup and map values directly, preserving decimal precision. The org's default currency ISO code is used unless you specify an alternative during schema planning.
LionDesk
Custom Field (Date)
Salesforce Sales Cloud
Custom Field (Date__c)
1:1LionDesk Date custom fields map directly to Salesforce Date fields with __c suffix. Original date values transfer without transformation. Time-of-day precision requires a separate custom DateTime field if needed — our pre-migration checklist flags any LionDesk Date fields that carry time data for admin review.
LionDesk
Custom Field (Number)
Salesforce Sales Cloud
Custom Field (Number__c)
1:1LionDesk Number custom fields map to Salesforce Number fields with __c suffix. Precision and scale match LionDesk's stored values. Negative values transfer intact. Overflow scenarios — where a LionDesk number exceeds Salesforce's maximum precision for the field — are flagged in the pre-flight validation report.
LionDesk
Custom Field (Text)
Salesforce Sales Cloud
Custom Field (Text__c)
1:1LionDesk Text custom fields map to Salesforce Text fields with __c suffix. Character limits in Salesforce (255 for standard Text, up to 131,072 for Long Text Area) may require truncation for over-length values — flagged before migration runs. We recommend Long Text Area for LionDesk fields with variable-length content such as notes or description fields.
LionDesk
Call Log / Task
Salesforce Sales Cloud
Task
1:1LionDesk call logs and completed tasks map to Salesforce Tasks. Original timestamps, owners (resolved by email match), and subject lines preserved. Task Type set to 'Call' for call logs. Open LionDesk tasks migrate with Status='Not Started' so nothing falls through the cracks during the transition window.
LionDesk
Email Activity
Salesforce Sales Cloud
Task
1:1LionDesk email history maps to Salesforce Tasks with Type='Email'. Subject, body, and direction (sent/received) preserved as Task fields. Attachments re-uploaded to Salesforce Files and linked via ContentDocumentLink. Email threads are reconstructed by grouping tasks by thread ID where LionDesk provides that metadata.
LionDesk
Note
Salesforce Sales Cloud
Note
1:1LionDesk notes map to Salesforce Notes (modern Notes object, not legacy Note). Rich-text formatting preserved where LionDesk supports it. Note title and body transfer as-is; parent record link restored by ContactId or AccountId lookup. Any LionDesk notes attached to deals are linked to the corresponding Opportunity via WhatId.
LionDesk
Drip Campaign / Sequence
Salesforce Sales Cloud
Salesforce Flow / Sales Engagement (rebuild reference)
1:1LionDesk drip campaigns and texting sequences have no direct Salesforce equivalent. We export campaign definitions as a structured rebuild reference (trigger criteria, step order, delay intervals, message content) so your admin can reconstruct them in Salesforce Flow or Sales Engagement. The reference includes step-level timing, conditional branches, and channel type (email, SMS, or task) for each sequence.
LionDesk
Owner / User
Salesforce Sales Cloud
User
1:1LionDesk owner IDs resolve to Salesforce Users by email match. Unmatched owners flagged before migration — your team either invites them to Salesforce or assigns their records to a fallback owner. No record lands without a valid Salesforce OwnerId. Fallback owner assignments are documented in the migration plan for your review before the migration script executes.
LionDesk
Video Email
Salesforce Sales Cloud
ContentDocument (File) + Task note
1:1LionDesk video email attachments download and re-upload to Salesforce Files as ContentDocuments. A Task record links to each file with a note describing the video email content, original send date, and recipient. The interactive playback experience cannot be replicated in Salesforce — this is documented as a functional delta in the migration handoff report.
| LionDesk | Salesforce Sales Cloud | Compatibility | |
|---|---|---|---|
| Contact | Contact1:1 | Fully supported | |
| Contact (with lead_status=Lead) | Lead1:many | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Pipeline | Sales Process + Record Type1:1 | Fully supported | |
| Pipeline Stage | Opportunity StageName1:1 | Fully supported | |
| Custom Field (Dollar Amount) | Custom Field (Currency__c)1:1 | Fully supported | |
| Custom Field (Date) | Custom Field (Date__c)1:1 | Fully supported | |
| Custom Field (Number) | Custom Field (Number__c)1:1 | Fully supported | |
| Custom Field (Text) | Custom Field (Text__c)1:1 | Fully supported | |
| Call Log / Task | Task1:1 | Fully supported | |
| Email Activity | Task1:1 | Fully supported | |
| Note | Note1:1 | Fully supported | |
| Drip Campaign / Sequence | Salesforce Flow / Sales Engagement (rebuild reference)1:1 | Fully supported | |
| Owner / User | User1:1 | Fully supported | |
| Video Email | ContentDocument (File) + Task note1: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
Salesforce Sales Cloud gotchas
Workflow Rules and Process Builder are retired
Bulk API batch quota exhaustion during large imports
Storage overage billing is non-obvious
Account-Contact many-to-many relationship mapping
Territory and team member import ordering dependencies
Pair-specific challenges
Migration approach
Stand up Salesforce schema before data moves
Before extraction begins, your Salesforce admin (or our team) creates the record types, page layouts, custom fields, and Sales Processes needed for the migration. We deliver a schema setup plan based on your LionDesk pipeline count, custom field inventory, and lead-status configuration so the Salesforce side is ready before validation runs. This step prevents the most common migration delay: field-not-found errors on insert.
Resolve owners and users by email match
LionDesk owner IDs are matched against Salesforce Users by email address. We run a pre-flight resolution pass that flags any LionDesk owner without a corresponding Salesforce User record. Your team resolves these gaps — either by inviting the user to Salesforce or by assigning their records to a designated fallback owner — before the migration script commits. No record lands in Salesforce without a valid OwnerId.
Migrate accounts and contacts before deals
Salesforce requires Account records to exist before Contact records can link via AccountId, and Contact records before Opportunity records can use Contact Roles. We sequence the migration so companies migrate first and become Salesforce Accounts, then contacts and leads split based on LionDesk lead_status value, then deals become opportunities with pipeline-to-record-type and stage-to-StageName mapping applied. This ordering respects Salesforce's foreign-key constraints and prevents orphaned records that would require manual repair after the migration completes.
Run a sample migration with field-level diff
A representative slice migrates first — typically 100–500 records spanning contacts, companies, deals, and activity history. We generate a field-level diff between LionDesk source values and Salesforce destination values so you can verify dollar amount precision, date formatting, owner resolution, and pipeline-to-record-type mapping before the full run commits. This sample pass surfaces discrepancies in a test environment, giving your team a chance to correct field configuration or mapping rules before production data moves. Discrepancies caught here do not require a rollback.
Cut over with delta-pickup for in-flight records
The full migration runs against Salesforce using the Bulk API for large record sets. A delta-pickup window (typically 24–48 hours) captures any LionDesk records created or modified during the cutover so Salesforce reflects the final source state at go-live. An audit log records every operation, and one-click rollback is available if reconciliation fails. After go-live, we deliver a reconciliation report comparing LionDesk record counts to Salesforce record counts by object.
Platform deep dives
LionDesk
Source
Strengths
Weaknesses
Salesforce Sales Cloud
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 Salesforce Sales Cloud.
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 Salesforce Sales Cloud migration scoping. Not seeing yours? Book a call.
Walk through your LionDesk to Salesforce Sales Cloud 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 Salesforce Sales Cloud
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.