Migrate from Leadtrekker Lead Management to Mailchimp

Leadtrekker Lead records map directly to Mailchimp Subscribers inside a target Audience. The lead's email address becomes the Subscriber Hash used for deduplication; first name, last name, phone, and physical address map to standard Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS). The lead's status field (active, converted, stale) is stored as a Tag in Mailchimp rather than a native status, since Mailchimp does not enforce a lead lifecycle stage model. We apply a pre-migration audience deduplication scan to avoid duplicate Subscriber records when multiple Leads share an email address.

Leadtrekker's lead source attribution (website form, campaign, referral, import) maps to a Mailchimp Tag named after the source label (e.g., TAG: source_website_form, TAG: source_google_ads). Source attribution is critical for the customer's marketing ROI reporting, so we treat it as a required mapping and verify every Lead has a source value before migration. If the customer used a custom lead source taxonomy, we map each distinct value to a corresponding Mailchimp Tag and optionally store the raw value in a merge field for segment filtering.

Leadtrekker's owner assignment (the rep responsible for a lead) maps to a Mailchimp Tag using the owner's display name (e.g., TAG: owner_jane_doe). Mailchimp does not support user-account assignment to subscribers the way Leadtrekker does; Tags provide the closest analog for segmenting contacts by responsible rep. We extract the full Owner roster from Leadtrekker during discovery and build the tag prefix strategy with the customer before migration. If the customer wants rep-level accountability, we recommend Mailchimp's Customer Journey automations triggered by tag-based segments.

Leadtrekker Notes attached to a Lead migrate as Tag-based activity log entries in Mailchimp. Each note becomes a Tag in the format ACTIVITY: note_{timestamp}_{preview}, preserving the timestamp and a 50-character preview of the note body. The full note content is stored in a custom Merge Field (NOTE_BODY) as a text field, since Mailchimp does not support free-form note objects on subscribers. For large note volumes, we batch-tag via the Mailchimp Tags API endpoint with exponential backoff to respect Mailchimp's rate limits.

Leadtrekker call engagements (with duration and disposition) migrate as Mailchimp Tags in the format CALL: {disposition}_{duration_seconds} at the timestamp of the original call. Call disposition values are mapped to specific tag prefixes (CALL: connected, CALL: no_answer, CALL: voicemail) so the customer can filter segments by call outcome. Duration is stored in a custom merge field CALL_DURATION_SECONDS for reporting. We batch-call the Mailchimp API using the member-by-email endpoint with tag-add operations, pacing requests to stay within Mailchimp's 10 requests/second limit.

Leadtrekker follow-up reminders with a due date and owner migrate as Tags in the format REMINDER: {due_date}_{owner}. Mailchimp does not have a native reminder or task object for subscribers, so due-date reminders are represented as tags that can trigger a Customer Journey automation if the customer configures one. We recommend the customer's admin sets up a Mailchimp automation triggered by REMINDER tags as the post-migration replacement for Leadtrekker's native reminder system. The migration deliverables include a reminder-rebuild guide with specific automation steps.

Leadtrekker user groups define which reps can view and edit specific lead subsets — a permission model with no direct Mailchimp equivalent. Mailchimp uses Audience-level access (all subscribers visible to all workspace users by default) rather than record-level permissions. We extract the full group membership roster and map each group to a Mailchimp Tag (e.g., TAG: group_enterprise_team). The customer uses Tags for organizational segmentation rather than access control. If the customer requires access restrictions by team, we document this as a Mailchimp Workspace or sub-account configuration decision for their admin post-migration.

Leadtrekker custom fields on Leads require explicit field-level mapping because the field taxonomy is not publicly documented. During discovery we probe the Leadtrekker API for all field keys present in a sample of records, then map each to a corresponding Mailchimp merge field of the appropriate type (text, number, date, phone, address, or dropdown). Mailchimp allows up to 40 merge fields per Audience. We configure all merge fields in the Mailchimp Audience before any subscriber data is loaded to prevent type mismatches during import. Customer-specific enum values from Leadtrekker custom fields map to Mailchimp dropdown merge fields with predefined options.