Migrate from LionDesk to Zoho CRM

LionDesk contacts map directly to Zoho CRM Contacts. The primary link is the contact's primary company — LionDesk stores this as a contact property while Zoho CRM requires an AccountId lookup. If a LionDesk contact has no associated company, FlitStack creates a default 'Unassigned Account' record and links the contact to it to satisfy Zoho's required AccountId relationship for most layouts.

LionDesk contacts who have not been converted to a deal or assigned a status can route to Zoho CRM Leads instead of Contacts. FlitStack applies a configurable rule — typically based on the presence of a last_activity_date or a blank deal association — to determine whether to create a Lead or a Contact record, ensuring no records are orphaned during migration.

LionDesk companies map to Zoho CRM Accounts using a direct name-to-name mapping. If the LionDesk company record contains parent-child hierarchy information, FlitStack maps the parent link to the Account.ParentId field in Zoho CRM, provided the parent account record is migrated first. Circular references are flagged and resolved before the migration run.

LionDesk deals map to Zoho CRM Deals using the deal name as the Zoho Deal_Name field. Pipeline stages are mapped via value mapping to Zoho's Stage pick-list. Owner resolution is handled by email match against Zoho CRM users — unmatched owners are flagged for admin assignment before records commit to the destination.

LionDesk pipeline definitions (pipeline name and associated stages) are translated into Zoho CRM Pipelines using Zoho's pipeline configuration API. Each LionDesk pipeline becomes one Zoho CRM pipeline. If Zoho CRM multi-pipeline view is available on the target plan, FlitStack preserves pipeline separation; otherwise, pipeline names are appended to stage values to maintain visibility into deal origin.

LionDesk stage names (e.g., 'Appointment Scheduled', 'Listing Presented', 'Under Contract') are mapped one-to-one to Zoho CRM Deal Stage pick-list values. Probability and forecast category are assigned per stage based on Zoho CRM defaults, then adjusted if the source data includes close_probability fields. Stage transition timestamps are stored in custom datetime fields since Zoho's native stage-history tracking requires additional configuration.

LionDesk custom fields defined on contacts — including types Text, Number, Date, and Dollar Amt — require Zoho CRM custom field creation before data loads. FlitStack creates the Zoho custom field using the field name, data type, and pick-list options from LionDesk, then maps values during the bulk write operation. Fields exceeding Zoho's 300-field-per-module limit are flagged for admin review before migration runs.

LionDesk notes attached to contacts or deals migrate as Zoho CRM Notes with a link to the parent Contact or Deal record. File attachments are downloaded from LionDesk's storage and re-uploaded to Zoho CRM's file attachment API. Note body content is preserved as plain text, and rich-text formatting is converted where feasible without breaking character encoding.

LionDesk call logs and completed tasks associated with contacts or deals migrate into Zoho CRM's Activities module. FlitStack creates a Task record with the activity type, subject, description, and original timestamp, linked via the WhatId field to the corresponding Zoho Deal or Contact. Email activity threads are stored as Notes if the message body is available, since Zoho's native email sync requires Zoho Mail configuration post-migration.

LionDesk owner IDs are resolved by email address against Zoho CRM's user list. FlitStack performs a pre-migration user audit to identify LionDesk owners who have no corresponding Zoho CRM user account. Unmatched owners receive a fallback owner assignment (configurable by the client) and the original owner ID is preserved in a Source_Owner_ID__c custom field for post-migration reconciliation.