Migrate from GENIEE to Mailchimp

GENIEE SFA/CRM Contacts migrate to Mailchimp Subscribers within a primary Audience. We map standard fields (email, first name, last name, phone) directly. Japanese field labels on custom properties are translated during scoping and mapped to Mailchimp Merge Fields. All contacts are imported as subscribed; the customer provides a suppression list of unsubscribed contacts from GENIEE which we import before the main contact migration to prevent re-subscribing.

GENIEE Company records do not have a direct Mailchimp equivalent since Mailchimp operates a flat subscriber model without native Account hierarchy. We map Company name and industry to Mailchimp Merge Fields and attach Company affiliation as a Tag on each Subscriber. For organizations requiring account-level reporting in Mailchimp, we configure a custom profile field for Company and advise rebuilding account grouping logic in Mailchimp Segments.

GENIEE Tags and Labels on Contacts migrate directly to Mailchimp Tags. Tag vocabulary is tenant-defined and preserved as-is. Mailchimp's tag model supports multiple tags per subscriber, matching GENIEE's multi-label structure. We export tags as label arrays and map them to Mailchimp tags at import time. Tags used for lead scoring or segmentation in GENIEE MA are preserved as tags but require manual segment rebuild in Mailchimp.

GENIEE SFA/CRM custom fields on Contacts migrate to Mailchimp Merge Fields within the target Audience. Field types are mapped: text fields to text merge fields, date fields to date merge fields, numeric fields to number merge fields, and checkbox or multi-select fields to either text merge fields or drop-down merge fields depending on the destination Mailchimp plan. We generate a field map during scoping and handle type conversion for any field that cannot map directly.

GENIEE MA Campaign records (campaign names, UTM parameters, source attribution) do not migrate as records to Mailchimp because Mailchimp has no campaign history import. Instead, we extract campaign metadata and use it to configure Mailchimp Audiences: default from-name, from-email, and UTM parameters are set during Mailchimp audience setup. The customer rebuilds campaign logic in Mailchimp's automation builder using this metadata as reference.

GENIEE SFA/CRM Users assigned as record owners are extracted and mapped to Mailchimp tags or a custom Merge Field (Owner) on each Subscriber. This preserves sales team attribution for migrated records. Mailchimp has no native user management equivalent to CRM ownership, so the tag-based approach provides the closest functional analog for routing and accountability.

Attachments on GENIEE SFA/CRM Contacts and Companies cannot migrate to Mailchimp because Mailchimp does not support file attachments on subscriber profiles. We flag attachments during scoping and deliver a written inventory of files with record reference so the customer's admin can re-upload to a linked storage system (Google Drive, SharePoint, or a CRM integration) post-migration.

GENIEE DSP campaigns (budget, targeting parameters, ad formats, flight dates) have no Mailchimp equivalent. Mailchimp is an email service platform, not an advertising demand-side platform. We exclude DSP campaign metadata from migration scope and deliver a written inventory of DSP campaign records with performance summaries for the customer to archive or import into a dedicated analytics tool if needed.