Migrate from MOGO to Mailchimp

Each MOGO contact record maps 1:1 to a Mailchimp subscriber within the target audience. The subscriber's email address serves as the primary key for matching; any duplicate emails detected in MOGO are flagged during pre-import validation to prevent Mailchimp's conflict handling from silently merging records and causing data loss.

MOGO custom properties of various types (text, number, date, boolean) become Mailchimp merge fields of the corresponding type. Text fields that exceed Mailchimp's 255-character limit are truncated with a truncation note included in the migration report for review. Date fields use Mailchimp's standard DATE merge tag format (YYYY-MM-DD) for consistency.

MOGO contact tags migrate directly as Mailchimp tags applied to each subscriber record. Tag names are normalized to lowercase with spaces converted to hyphens to comply with Mailchimp's tag syntax requirements. Any tags containing special characters are cleaned and sanitized before the import process begins.

MOGO active contacts are mapped to Mailchimp 'subscribed' status. Inactive or previously unsubscribed MOGO contacts are mapped to 'unsubscribed' to honor existing consent records and GDPR compliance requirements. MOGO contacts without valid email addresses are exported with 'pending' status, requiring re-consent handling within Mailchimp's workflow.

MOGO saved segments are recreated as Mailchimp segments using the migrated merge fields as segment criteria and filter conditions. The complete segment rules are documented in a Mailchimp setup guide delivered alongside the migration package so your team can recreate and adjust them directly in the Mailchimp UI after migration.

MOGO company names are mapped to Mailchimp's built-in COMPANY merge field for consistent branding attribution. When MOGO stores company address components separately (street address, city, state, zip code), these are consolidated and mapped to Mailchimp's ADDRESS merge field type, which stores them as a formatted address block on the subscriber record.

Mailchimp's native subscriber 'timestamp' field reflects the import date rather than the original source record creation date. To preserve historical accuracy for reporting continuity, FlitStack AI stores the original MOGO create date in a custom date-typed merge field (ORIGINAL_CREATEDATE__c) that can be referenced in segmentation and reporting.

MOGO appointment or transaction history has no native Mailchimp equivalent since Mailchimp tracks campaign engagement rather than operational events. FlitStack AI exports this data as a JSON-encoded custom merge field (ACTIVITY_HISTORY__c) with a 2,000-character limit. Teams requiring this data in Mailchimp reports should configure a linked Zapier or Make integration post-migration.

Mailchimp is an email marketing platform and does not function as a document storage system. File attachments associated with MOGO contact records are not migrated to Mailchimp. Instead, we export a comprehensive file manifest containing all attachment URLs so your team can host them externally (Google Drive, Dropbox) and reference them in Mailchimp campaigns.

Mailchimp does not have a native owner or assigned-user concept for individual subscribers within an audience. MOGO owner IDs are preserved as a text merge field (MOGO_OWNER__c) for internal reference and traceability. If Mailchimp's Teams feature is active on your account, owner-to-subscriber mapping can be configured as a post-migration customization step.