Migrate from LionDesk to Mailchimp

LionDesk contacts map to Mailchimp audience members. Email address is the unique identifier — each LionDesk contact becomes one member record in your target Mailchimp audience. Duplicate email addresses are flagged during extraction and resolved before loading. The primary company association is stored in the COMPANY merge field for each audience member.

LionDesk custom fields (Text, Number, Date, Dollar Amt types) are created as matching Mailchimp merge fields in the target audience. Data type is preserved — number fields stay numeric, dates stay date-typed — so segmentation and filtering in Mailchimp work correctly after migration.

LionDesk tags applied to contacts migrate as Mailchimp tags on the same audience member. Tags are preserved as-is and can immediately drive segmentation, campaign targeting, and Customer Journey triggers without manual re-tagging. Tags are transferred exactly as they appear; case differences produce separate tags. If you use tag groups, we can apply a consistent prefix so segmentation remains clear in Mailchimp.

LionDesk notes migrate to a dedicated text merge field labeled LD_Notes for reference. Mailchimp has no native notes object for members, so the content is stored as a text field. Note truncation occurs for content exceeding 255 characters — flagged in the field-level diff.

LionDesk deal pipelines and stage values have no direct Mailchimp equivalent. Mailchimp is an email marketing platform, not a CRM — deal names, amounts, and pipeline stages cannot be stored as structured records. These are documented as rebuild items. If you need to preserve deal amounts or stage names, we can create custom number or text merge fields to store these values, then use them for segmentation or reporting in Mailchimp.

LionDesk task assignments and reminders cannot migrate to Mailchimp, which has no task management module. We recommend exporting the task list as a CSV before cutover so your team can recreate critical follow-ups manually in their preferred task tool. The exported CSV includes due dates, assignees, and task descriptions to facilitate straightforward recreation in tools such as Asana, Trello, or a spreadsheet.

LionDesk drip campaigns are built on a different automation model than Mailchimp Customer Journeys. There is no direct translation between the two. We export campaign definitions as a structured reference document so your Mailchimp admin can rebuild sequences in Journey Builder.

Mailchimp has no native company or account object — contacts are flat records within an audience. The primary company name maps to the COMPANY merge field. If you rely on LionDesk company associations for segmentation, those must be reconstructed using merge fields or tags in Mailchimp.

LionDesk SMS conversations and logs cannot be stored in Mailchimp, which is email-focused. We recommend exporting SMS history as a CSV using LionDesk's native export function before cutover for compliance and record-keeping purposes. The CSV export can be used for compliance audits, regulatory retention requirements, or imported into a dedicated SMS platform if you decide to continue texting through a third-party service.

LionDesk video email files do not transfer to Mailchimp. If video content is critical to your outreach, host videos externally and embed links in your Mailchimp campaigns. The video files themselves remain in LionDesk until account deprovisioning. If you need to keep video content accessible after deprovisioning, download the files from LionDesk before the account is closed, and store them in a cloud drive or media library.