Migrate from eTrigue to Mailchimp

eTrigue Prospects map 1:1 to Mailchimp Contacts within a single Audience. Standard fields (First Name, Last Name, Email, Company, Phone) map directly to their Mailchimp equivalents. Email address is the dedupe key — we use Mailchimp's upsert behavior to handle duplicate email addresses by updating existing records rather than creating duplicates. The Status field requires decoding from numeric codes (1 = Active, 2 = Opt-Out, etc.) before import to avoid silently marking all records as active.

eTrigue Campaigns map to Mailchimp Campaigns and Tag records on each Contact. Campaign names become Mailchimp Campaign titles; campaign response history (sent, opened, clicked) is captured as Tag values (e.g., CampaignName_Sent, CampaignName_Opened) on the associated Prospect records so the response timeline is visible per contact. We export the campaign list first, then apply tags to Prospects based on their activity history within each campaign.

eTrigue Activity History records (page views, email opens, form submissions, campaign responses with timestamps) are exported as a structured activity log and mapped to Mailchimp Tags with timestamp metadata embedded in the tag name (e.g., FormSubmission_2024-03-15). For key engagement events, we also populate a free-form text merge field capturing the most recent engagement date and type. Mailchimp does not have a native Activity History object, so this is a best-effort reconstruction using available tagging and merge field primitives.

eTrigue's composite Lead Score is stored as five separate numeric properties: Campaign Score, Activity Score, Source Score, Relationship Score, and Buy Time Score. Mailchimp has no native Lead Score object, so we create five merge fields (LEAD_CAMPAIGN, LEAD_ACTIVITY, LEAD_SOURCE, LEAD_RELATION, LEAD_BUYTIME) on the Mailchimp Audience to preserve each component. We also create a LEAD_TOTAL merge field containing the sum of all five for quick segmentation. The original composite score breakdown is preserved for the customer to reference when rebuilding scoring logic in any external scoring tool.

eTrigue Boolean, Text, and Numeric custom fields defined under Settings > Prospect Settings > Prospect Fields migrate to Mailchimp Merge Fields. Boolean fields map to Yes/No text or a checkbox merge field. Text fields map to text merge fields. Numeric fields map to number merge fields. The merge field type is determined during data profiling before import. Mailchimp has a limit of 20 merge fields per audience on Standard plans; we flag any accounts exceeding this for the customer to prioritize the most critical fields.

eTrigue's 3D Lead Scoring model enriches standard scoring with content-type engagement weighting. We export the 3D score as a single composite merge field (LEAD_3D) in Mailchimp. Mailchimp has no native equivalent for weighted content engagement scoring, so we preserve the calculated composite value and note the methodology for the customer to reference if they implement a similar model in an external scoring tool post-migration.

eTrigue landing pages with progressive forms are not migrated as functional pages — Mailchimp does not host external landing pages. We export the form field definitions (field names, labels, and types) and map them to Mailchimp's embedded signup form builder fields so the customer can recreate the form structure. Styling, layout, and progressive display logic do not transfer and must be rebuilt manually.

eTrigue Content Types used to classify prospect engagement with content categories export as Tag values in Mailchimp. We map each Content Type to a Tag name on the corresponding Prospect records. Mailchimp's 200 tag limit per contact is checked during scoping — for accounts exceeding this, we prioritize the most behaviorally relevant tags and note the overflow for manual cleanup post-migration.

Customers using eTrigue Lead Accelerator for channel partner programs store partner organization names and partner-specific campaign attribution in custom Prospect fields. These custom fields map to Mailchimp merge fields (PARTNER_ORG) and Tags (PartnerName format). Partner-specific scoring rules are documented in the handoff package for the customer's admin to evaluate for recreation in Mailchimp Automations or an external scoring tool.