Migrate from Constructor to Mailchimp

Constructor contacts migrate to Mailchimp subscribers. The contact's email address is the subscriber key — if a subscriber already exists in the target Mailchimp audience, records are matched by email and updated rather than duplicated. Constructor contact owners are not assigned in Mailchimp — team access is managed through Mailchimp user permissions instead.

Constructor companies don't have a direct Mailchimp equivalent. Company name maps to the COMPANY merge field (FALLBACK). Company domain, industry, and employee count become custom merge fields in the Mailchimp audience. Multiple Constructor contacts associated with the same company receive the same company merge field values.

Constructor deals (stages, amounts, close dates, owners) have no native Mailchimp object. We preserve deal data as Mailchimp tags (e.g., DealStage:Negotiation, DealAmount:5000) and include a Deal_Details__note in the subscriber profile referencing the original Constructor deal name and stage. Salesforce-style pipeline stages don't exist in Mailchimp.

Constructor task records (subject, due date, status, owner) have no Mailchimp equivalent. Mailchimp tracks email engagement activity only. Tasks requiring internal follow-up should be managed in Constructor or a project management tool after migration — they cannot be represented in Mailchimp's subscriber model.

Constructor notes attached to contacts migrate to Mailchimp subscriber notes. Notes attached to deals or companies are appended to the associated contact's note field. Mailchimp's note field accepts plain text up to the character limit per subscriber. When notes exceed Mailchimp's character threshold, we truncate with an ellipsis marker and flag those records for review so no critical context is permanently lost during migration.

Constructor call and meeting records (with timestamps, duration, owner, outcome) have no Mailchimp representation. Mailchimp tracks email engagement per subscriber but has no call or meeting history model. If this activity context is critical, it must remain in Constructor or be documented outside Mailchimp.

Emails sent from Constructor are not tracked in Mailchimp's campaign history since they originate outside Mailchimp. Mailchimp will begin tracking opens, clicks, and unsubscribes only for emails sent through Mailchimp campaigns post-migration. Historical Constructor email sends are not represented in Mailchimp.

Constructor contact tags and labels migrate 1:1 to Mailchimp subscriber tags. Tags are preserved with their original names. If a tag contains a Constructor-specific value (e.g., DealStage:ClosedWon), it migrates as-is — we recommend reviewing tag naming conventions post-migration to align with Mailchimp segmentation practices.

Constructor custom fields on contacts create corresponding Mailchimp merge fields. Field types are mapped: text → text merge field, number → number merge field, date → date merge field (formatted per Mailchimp requirements), picklist → dropdown merge field with options mapped value-by-value. Mailchimp requires merge field names in uppercase (e.g., LIFECYCLESTAGE).

Constructor custom fields on companies become merge fields on the associated subscriber record. Since Mailchimp contacts don't have a separate company object, company-level custom data is flattened onto the subscriber. This requires a company-first pass to establish the field-to-subscriber mapping before import.

Constructor owner assignment (sales rep linked to a contact or deal) has no Mailchimp equivalent. Mailchimp manages access at the account and audience level, not per-subscriber. If owner attribution is critical for campaign targeting, owner names can be stored as a merge field on subscribers for segmentation purposes.

Constructor workflows, automation sequences, and triggered actions do not migrate. We export Constructor workflow definitions (triggers, conditions, actions) as a documented reference. Mailchimp Customer Journey Builder must be rebuilt — we provide the exported workflow map so your team can recreate the logic in Mailchimp's automation builder.