Migrate from LionDesk to Freshsales

LionDesk Contact maps directly to Freshsales Contact. Freshsales requires an AccountId lookup for most contact records — LionDesk contacts without a primary company get attached to a default 'Unassigned Account' record during migration. All standard contact properties (name, email, phone, address) carry over as direct field mappings.

LionDesk Company maps to Freshsales Account. Field names differ slightly (LionDesk uses 'company_name' vs Freshsales 'name') but the semantic intent is identical. Parent-child company relationships in LionDesk map to Freshsales's Parent Account field. Multi-company contact associations in LionDesk (N:N) collapse to one primary AccountId in Freshsales with secondary relationships preserved as Account Contact Relationships.

LionDesk Deal maps to Freshsales Deal with one exception: LionDesk supports a single pipeline while Freshsales supports multiple. If your LionDesk account uses more than one named pipeline, each pipeline maps to a separate Freshsales Pipeline object. Deal name, amount, stage, and close date map directly; stage values require value-by-value mapping because LionDesk stage names are free-text.

LionDesk's single-pipeline-per-account model maps directly to one Freshsales Pipeline. If your LionDesk account has multiple named pipelines (e.g., Listings, Buyers, Rentals), each becomes a separate Freshsales Pipeline with its own stage set. Pipeline-level settings like probability weights and forecast categories must be reconfigured in Freshsales admin settings post-migration.

LionDesk deal stage names are free-text and vary by account. Each unique stage name is mapped to a corresponding Freshsales stage value within its pipeline. Probability and forecast category are assigned per Freshsales stage based on your historical close rates. Stage-entered timestamps are preserved as custom datetime fields on the Deal record for reporting continuity.

LionDesk custom fields of types Text, Number, Date, and Dollar Amt each require a corresponding Freshsales custom field created before migration. Text fields map to Freshsales Text type; Number to Number; Date to Date; Dollar Amt to Currency. Custom field definitions and their rank/order are preserved in the migration plan so your Freshsales admin can pre-create the target fields before data lands.

LionDesk drip campaigns do not have a direct Freshsales equivalent. Freshsales separates automated outreach into Sales Sequences (outbound email drip) and Workflows (event-triggered automation). FlitStack exports your drip campaign definitions — contact triggers, step delays, message content — as a structured reference document for your Freshsales admin to rebuild using the platform's native Sequence and Workflow builders.

LionDesk tasks and reminder records map directly to Freshsales Tasks. Original due dates, assigned owners (resolved by email match), task status, and priority are preserved. Task descriptions and notes carry over as-is. Tasks associated with specific contacts or deals retain their parent record links in Freshsales.

LionDesk notes attached to contacts, companies, or deals migrate as Freshsales Notes. The note body content and original create timestamps are preserved. If notes contain rich-text formatting, the plain-text content is preserved and any embedded image links are re-evaluated for Freshsales file storage compatibility.

LionDesk owner IDs are resolved against Freshsales users by email match. Unmatched owners are flagged before migration — your team either creates their Freshsales user account first or assigns their records to a fallback owner. This prevents records from landing without an owner assignment, which would break Freshsales's assignment-rule and notification logic.

LionDesk's native SMS functionality is a platform-specific feature with no structural equivalent in Freshsales (which requires Freshcaller or a third-party SMS integration). FlitStack exports SMS message content and timestamps as Activity records for reference, but the SMS cannot be replayed or continued as a native Freshsales feature. This limitation should be addressed during your Freshsales integration planning.

LionDesk's video email feature stores a video link or embedded recording associated with a contact or deal. Freshsales does not have a native video email module. We export the video URL or embed reference and attach it as a note on the contact record so your team can access the original video link in Freshsales even if the video itself cannot be replayed as a native Freshsales engagement feature.

LionDesk contact and deal tags migrate to Freshsales Tags, which are available across all modules including Contacts, Accounts, Deals, and Leads. Tags are preserved as-is during migration and can be used immediately for segmentation, filtering, and workflow triggers in Freshsales after the cutover completes. This allows your team to maintain existing categorization logic without rebuilding tag structures manually.

LionDesk lead status values (New, Contacted, Qualified, or any custom values your account uses) map to Freshsales Lead Status pick-list values during migration. Custom status values in LionDesk require a pre-migration value-mapping configuration step so Freshsales can accept the incoming data without pick-list validation errors. FlitStack audits all unique LionDesk status values during discovery and provides the mapping configuration checklist before the migration run.