Migrate from Lead Docket to Mailchimp

Lead Docket contacts with valid email addresses become Mailchimp subscribers in the target audience. Email serves as the unique identifier for subscriber matching. During import, we match on email as the primary key; if duplicate emails exist, the most recently updated record is kept. Contacts without email are flagged, logged for manual review, and excluded from the main load.

Lead Docket leads that have not yet converted and carry a valid email address are imported as Mailchimp subscribers. Email is mandatory in Mailchimp, so leads missing an email are excluded from the bulk load and flagged for your team to either enrich with a correct address or retain in a separate reference export. During import, duplicate emails are resolved by keeping the latest Lead Docket timestamp.

Lead Docket's 11 default statuses (New Lead, Attempting Contact, Qualified, Proposal Sent, etc.) become Mailchimp tags. Custom statuses created in your Lead Docket account also become tags. Tags enable segmentation by intake stage, but Mailchimp's flat tag model differs from Lead Docket's hierarchical pipeline view.

Any case type assigned to a lead in Lead Docket — such as Personal Injury, Family Law, or Immigration — is translated into a corresponding Mailchimp tag. If a lead contains multiple case types, each is added as a separate tag to preserve full classification. Tag names preserve the original case type label, enabling you to segment campaigns by practice area or service line across the Mailchimp audience.

Both marketing sources and contact sources recorded in Lead Docket are transferred as Mailchimp tags, preserving every attribution pathway such as 'Source: Google Ads', 'Source: Referral Partner', or 'Source: Event'. If a record carries multiple source entries, each is added as a distinct tag. Tag names retain the original casing to keep attribution precise for segmentation and campaign performance analysis.

Lead Docket custom fields on leads (text, number, date, dropdown, checkbox, currency) become Mailchimp merge fields. Field names are truncated to Mailchimp's 10-character short name limit with numeric suffixes for uniqueness. Merge field types are set to match Lead Docket types where Mailchimp supports them.

Contact-level custom fields from Lead Docket also become Mailchimp merge fields. Currency fields become text merge fields (Mailchimp has no native currency type). Checkbox fields become yes/no text merge fields. We document the full mapping between Lead Docket field names and Mailchimp short names.

Every tag that has been applied to a Lead Docket contact or lead is transferred to the corresponding Mailchimp subscriber using the identical tag name. If a subscriber receives multiple tags from the source record, each is applied individually. This ensures that the complete tagging taxonomy — including status, case type, source, and any custom tags — is replicated in Mailchimp for accurate segmentation.

All notes attached to Lead Docket leads or contacts have no native equivalent in Mailchimp, which lacks a notes object. We export the complete set of notes into a CSV file keyed by the Lead Docket record ID, preserving the note text, author, and timestamp. Your team can archive this file for compliance audits or use it as a reference during manual follow‑up.

Call logs, email logs, and message history stored in Lead Docket have no counterpart in Mailchimp, which focuses on subscriber engagement metrics such as opens, clicks, and unsubscribes rather than internal communication records. We export all activity entries to a separate CSV file that includes the record ID, activity type, timestamp, and details, allowing your firm to retain the data for compliance or later review.

Automations built in Lead Docket — which trigger on status changes, lead form submissions, and integrations with Filevine and Vinesign — are platform-specific and cannot transfer. We export automation definitions as a reference document for manual rebuilding in Mailchimp's Customer Journey builder.

Lead forms and intake questionnaires built in Lead Docket have no direct counterpart in Mailchimp, which does not include a native intake form object. We document the complete structure of each form — including field names, types, required settings, and conditional logic — in a reference guide. Using that guide, your team can recreate the forms in Mailchimp's form builder or embed custom HTML forms on your website.

Lead Docket's built-in reporting suite does not replicate in Mailchimp. After migration, teams build reports using Mailchimp's audience growth, email performance, and e-commerce dashboards. Tags migrated from Lead Docket (status, case type, source) can be used to segment Mailchimp reports.

Native integrations that are active in Lead Docket — such as Filevine project sync, CallRail call tracking, and Google Analytics — do not have equivalents in Mailchimp and cannot be transferred. We export a detailed integration reference that outlines each connection’s triggers, data flows, and configuration settings. Your team can then rebuild the integrations using Mailchimp’s connected apps, Zapier workflows, or custom API connections based on that documentation.