Migrate from GP Flow to Mailchimp

GP Flow contacts migrate as Mailchimp members within the target audience. The email address is the unique identifier — FlitStack matches by email on delta runs to avoid duplicate members. Unsubscribed and bounced contacts from GP Flow are imported as suppressed members in Mailchimp to preserve deliverability.

GP Flow companies map to merge fields on each member record — COMPANY_NAME, COMPANY_DOMAIN, and COMPANY_INDUSTRY are created as text merge fields. Since Mailchimp has no standalone Account object, the primary company per contact is stored on the member. Multi-company associations in GP Flow are preserved in a companion reference file.

GP Flow deals have no direct Mailchimp equivalent — deal name becomes a text merge field (DEAL_NAME), amount maps to a number merge field (DEAL_AMOUNT), and close date maps to a date merge field (DEAL_CLOSE_DATE). Pipeline and stage information is stored as Mailchimp tags for segmentation.

GP Flow pipeline names are stored as Mailchimp tags — each member is tagged with their associated pipeline name (e.g., tag: Pipeline: Sales, tag: Pipeline: Enterprise). This enables segmentation by pipeline within Mailchimp's tag-filtering interface, though it does not replicate GP Flow's visual pipeline view.

GP Flow pipeline stage values are mapped to Mailchimp tags — each stage becomes a tag (e.g., tag: Stage: Discovery, tag: Stage: Proposal, tag: Stage: Closed Won). Value-by-value mapping preserves the original stage names exactly. Stage-entered timestamps are stored as a custom datetime merge field.

GP Flow custom objects map to merge fields in Mailchimp — each custom object field is translated to a text, number, or date merge field. If a GP Flow custom object has relationships to other objects, those are preserved as tagged identifiers. Objects with more than 40 fields across all types trigger Mailchimp's merge-field cap and require a companion file.

Mailchimp has no native lifecycle stage field. FlitStack AI creates a pick-list merge field (LIFECYCLE_STAGE) on the audience and maps every GP Flow lifecycle stage value exactly. Stage-transition timestamps are stored as a separate datetime merge field. Values like 'Lead', 'MQL', 'SQL', and 'Customer' are preserved for segmentation.

GP Flow engagement history — call logs, logged emails, meeting records, and notes — is consolidated into a Mailchimp member note field per contact. Original timestamps and owner names are included in the note text. Note: Mailchimp's note field is plain text with no rich formatting; timestamps and owner attribution are embedded as text strings.

GP Flow file attachments on contacts or deals are re-uploaded to Mailchimp's file hosting if they are email-relevant assets (images, logos). Large files or non-image attachments that exceed Mailchimp's file storage limits are linked via a companion reference document pointing to the original URL in GP Flow.

GP Flow workflows, sequences, and automation rules are not compatible with Mailchimp's automation engine and cannot be migrated automatically. FlitStack AI exports a machine-readable definition of every GP Flow workflow (trigger, conditions, actions) as a PDF reference document your Mailchimp admin uses to rebuild automations in Mailchimp's automation builder.

GP Flow owner assignments on contacts and deals are stored as Mailchimp tags — for example, tag: Owner: [email protected]. This preserves the assignment relationship for reference and reporting. Mailchimp has no native owner concept, so owner tags are informational rather than functional.

GP Flow subscriber status maps directly to Mailchimp member status. Active contacts become subscribed members; unsubscribed contacts are imported as unsubscribed in Mailchimp (suppression list); bounced contacts are imported as cleaned members to protect deliverability. This is critical for maintaining email reputation during and after migration.