Migrate your LionDesk data

Contacts are LionDesk's primary record type. Every contact has a flat profile with default fields (name, email, phone, address) plus any assigned custom fields. We map these 1:1 into the destination CRM's contact or person object, preserving all field values and assigning the owner from the source record.

LionDesk custom fields support four data types: Text, Number, Date, and Dollar Amt. We inspect the custom field definitions in the account's API response before migration, map each field's type to the closest matching destination field type, and flag any Dollar Amt fields that may require currency normalization.

Drip email sequences are stored as campaign objects with step definitions tied to contact enrollment triggers. We export the sequence structure and step content as a human-readable migration artifact, but automated enrollment logic must be rebuilt on the destination platform since trigger conditions are not exportable.

Text drip sequences follow the same campaign model as email drips. Phone number validity is critical — we flag any contacts with malformed or missing phone numbers before SMS campaigns are included in the migration scope.

Video emails are stored as attachments or linked media within the contact record. We preserve the video URL or embedded media reference during export, but the video hosting itself is LionDesk's infrastructure. We flag these as non-self-contained assets that require re-hosting on the destination platform.

Tasks are linked to contacts and include due dates, assignees, and completion status. We export task records as standalone objects, then associate them with their parent contact in the destination system. Open tasks are prioritized; completed tasks are exported with their historical timestamps.

Call logs record inbound and outbound call history against a contact, including duration and timestamp. We export these as activity or engagement records. Note that call recordings are stored in LionDesk's media infrastructure and may not be accessible via API for bulk export.

Contacts can have multiple tags applied. Tags are exported as a list per contact and mapped to equivalent tagging or labeling constructs in the destination CRM. If the destination uses a different tagging model (e.g., lists or segments), we translate tags to the closest available construct.

LionDesk tracks where a contact originated (e.g., Zillow, Referral, Facebook). This is typically a single-select or free-text field on the contact record. We preserve the source value as a custom or standard property on the destination contact record.

Free-text notes attached to a contact are exported as activity records or note objects. We preserve the note body, creation date, and author. Notes with embedded media or links to LionDesk-hosted files are flagged as potentially incomplete after migration.

Scheduled events tied to contacts — appointments, showings, follow-ups — are exported with date, time, duration, and associated contact. Calendar event logic (reminders, recurring events) must be verified post-migration as these behaviors may not transfer exactly.

LionDesk campaigns aggregate multiple touchpoints (emails, texts, calls) into a single initiative. We export campaign metadata and the associated contact enrollments, but automation triggers and enrollment rules are platform-specific and must be reconstructed on the destination.

Agent and staff user accounts in LionDesk are the owners of records. We export user identity (name, email) and map them to user or owner fields in the destination. If the destination uses a different user schema or requires manual user provisioning, we flag this during the scoping call.