Migrate from Wise Agent to Mailchimp

Mailchimp has no deal, transaction, or pipeline object — deal and transaction fields become read-only reference data

Wise Agent stores deals with stage, amount, and close date, plus transaction checklists tied to specific property addresses. Mailchimp has no equivalent to these objects — its contact model only supports subscriber fields, tags, and segments. When you migrate, deal fields and transaction fields land as custom merge fields on the subscriber record. They are preserved for segmentation and reference, but you cannot run a deal pipeline or transaction checklist inside Mailchimp. You will need a separate tool or a manual process to manage active deal progress after the migration.

Wise Agent drip campaigns do not migrate as Mailchimp automations — sequences must be rebuilt from drip-enrollment tags

Wise Agent's drip campaigns store a contact's enrollment date, which drip step they reached, and when they last received an email. Mailchimp's Customer Journeys automation builder cannot import drip sequences — it requires you to rebuild each sequence manually. FlitStack preserves the drip enrollment state as tags and custom fields (DRIPENRLD__c, DRIPSTEP__c) so your team can use those values as starting conditions when rebuilding in Mailchimp's automation builder, but the automation logic itself does not transfer.

Wise Agent's single-label-per-contact model requires label-group decomposition before tagging into Mailchimp

Wise Agent supports label groups (e.g., a contact can be tagged with a 'Source' group and a 'Status' group, each containing one active label). Mailchimp's tag model is many-to-many and does not enforce mutual exclusivity by group. When migrating, FlitStack decomposes each label group into individual tags with a group prefix (e.g., 'Source-Web Form', 'Status-Hot Lead') to preserve the semantic meaning of the original group structure within Mailchimp's flat tag namespace.

Mailchimp's subscriber status is permanent for unsubscribes — mismatches with Wise Agent's opt-out flag require manual review

Wise Agent tracks contact-level opt-out separately from its contact database. Mailchimp enforces audience-level unsubscribe as a permanent status that cannot be overwritten by API. If a contact in Wise Agent is marked as opted out, FlitStack checks their Mailchimp subscriber status before attempting to import — contacts already unsubscribed in Mailchimp are skipped and logged; contacts with no Mailchimp record are imported as subscribed. Any contacts where Wise Agent says active but Mailchimp already has an unsubscribe record require manual resolution.

Mailchimp's contact-based pricing means the migrated audience size directly affects your monthly plan cost

Wise Agent uses a flat-rate model that bundles contacts into the monthly subscription regardless of list size. Mailchimp prices by total audience contacts, and plan tiers enforce contact caps that trigger overage charges if exceeded. Before migration, FlitStack audits your Wise Agent contact count and flags any contacts that should be excluded (test records, duplicates, permanently bounced addresses) so your Mailchimp audience lands within your target plan tier and avoids surprise billing after migration.