Migrate from LionDesk to Twenty CRM

LionDesk Contact maps directly to Twenty People. Email, phone, first name, last name, job title, and address fields transfer as-is. The LionDesk contact's primary company assignment becomes the People record's companyId relation — the Company record must exist in Twenty before the People record loads so the foreign key resolves correctly.

LionDesk Company maps to Twenty Companies. Company name, domain/website, address, and industry fields transfer as-is. If the LionDesk account has a parent company relationship, that maps to the Companies record's parentId relation — parent records must migrate first to avoid circular reference errors.

LionDesk Deal maps to Twenty Opportunities. Deal name, amount, stage status, close date, and owner assignment transfer. Stage values that exist as pick-list options in LionDesk become Twenty's stage pick-list on the Opportunities object. Owner email match resolves to the Twenty workspace member.

LionDesk tasks map to Twenty Tasks with type, subject, due date, and assignee preserved. Tasks linked to a contact in LionDesk carry the People record's id as the task's assignee and a relation back to the People record. Completed status and completion timestamps are preserved as custom fields if not natively supported.

LionDesk notes attached to contacts or companies migrate as Twenty Notes linked to the corresponding People or Companies record. Rich text formatting is converted to plain text for compatibility; FlitStack flags any note exceeding Twenty's character limits before the full run.

LionDesk custom fields of type Text are replicated as custom fields in Twenty via Settings → Data Model before migration. The field name and data type are preserved. Long-text fields that exceed Twenty's default display settings are surfaced in a note to your admin for layout adjustment.

LionDesk Number custom fields migrate to Twenty custom number fields. Numeric validation is applied during migration — any non-numeric values in the source are flagged in the pre-flight report and optionally loaded as text fields for manual review in Twenty.

LionDesk Dollar Amt custom fields become Twenty currency fields or custom number fields with decimal precision. FlitStack strips any currency symbols and validates decimal formatting during the transformation step. The original LionDesk field name is stored in a mapping log for audit purposes.

LionDesk Date custom fields map to Twenty date fields. Date formats from LionDesk (which may vary by account settings) are normalized to ISO 8601 (YYYY-MM-DD) during transformation. Any ambiguous date formats are flagged in the pre-flight report with the specific record id and field name.

LionDesk owner ID is resolved to the Twenty workspace member by email match. Unmatched owners — records assigned to a LionDesk user who has not accepted their Twenty invitation — are flagged before migration. Your admin either invites those users first or assigns records to a fallback workspace member.

LionDesk drip campaigns and automated sequences cannot be migrated to Twenty workflows — the trigger-and-action models are fundamentally different. FlitStack exports your sequence definitions (step order, delay days, action type, and recipient criteria) as a structured JSON file that your admin can use as a rebuild guide in Twenty's workflow builder.

LionDesk's video email and video text features store video content on LionDesk's infrastructure. FlitStack migrates the video URL as a text custom field on the People record. If the video content has been moved to a separate hosting platform, update the URL after migration; the historical reference to the video is preserved as long as the link remains active.