Migrate from Zavvie Power Buyer to Mailchimp

Offer and deal data has no native Mailchimp home — it becomes tags and merge fields

Zavvie Power Buyer's core data model centers on offers and deal stages tied to specific contacts. Mailchimp has no Opportunity or Deal object — all transaction context must be encoded as merge field values and subscriber tags. Offer amounts become NUMBER merge fields, offer status becomes tags like 'offer-submitted' or 'offer-accepted', and deal stage becomes pipeline-stage tags. Mailchimp's tag limit per subscriber is 60, so contacts with frequent stage transitions may hit that ceiling. We flag contacts approaching the tag limit before migration and collapse low-value tags if needed.

Agent-to-contact relationships require a custom tagging strategy

Zavvie links every contact to an assigned agent via a foreign key relationship. Mailchimp has no native agent-assignment model — contacts are flat records within an audience. We preserve agent attribution by applying a subscriber tag in the format 'agent:[email protected]' to each contact. Mailchimp's audience-based permissions mean a single audience cannot restrict which agent sees which contacts; visibility is all-or-nothing at the audience level. Teams requiring agent-specific contact visibility should consider splitting contacts into per-agent audiences post-migration.

Activity history and offer communications do not migrate

Zavvie logs every offer communication, status change, and agent note with timestamps and user attribution. Mailchimp tracks campaign activity (opens, clicks, unsubscribes) but has no native activity feed for pre-migration events. Offer emails sent in Zavvie, meeting notes, and call logs are not importable into Mailchimp. We export a full activity log JSON from Zavvie as a reference archive; the Mailchimp subscriber record begins with no historical engagement data. Campaign tracking in Mailchimp starts fresh from the go-live date.

Custom contact properties require pre-migration merge field creation

Zavvie supports custom properties on contacts, companies, and offers with varied data types. Mailchimp merge fields must be created before importing data, and field types (TEXT, NUMBER, DATE, PHONE, ADDRESS) must be declared upfront. Changing a merge field type after creation requires deleting and recreating it, which disrupts existing subscriber data. We deliver a merge field creation checklist based on the Zavvie schema export before migration runs, giving your Mailchimp admin time to configure fields correctly in the target audience.

Subscriber status and email consent must be explicitly mapped

Zavvie tracks email consent at the contact level with opt-in and opt-out flags. Mailchimp enforces list-based subscription status: subscribed, unsubscribed, pending, or cleaned. Contacts with no email address in Zavvie cannot be imported (Mailchimp requires a valid email per subscriber). Contacts marked as unsubscribed or bounced in Zavvie must be mapped to the corresponding Mailchimp status to avoid re-subscribe violations. Double opt-in settings in Mailchimp affect how pending subscribers flow into the audience — we align the migration import status with your Mailchimp audience's confirmation opt-in configuration.