Migrate from Wishpond to Mailchimp

Wishpond Leads map to Mailchimp Subscribers within a target Audience. We extract all standard fields (name, email, phone) and custom Lead properties, then create corresponding Mailchimp merge fields (max 40 per Audience on Standard and Essentials tiers) during schema configuration. The Wishpond lead source campaign or landing page maps to a Mailchimp Tag on the Subscriber record. We deduplicate by email address and flag records with missing emails for customer review before import.

Wishpond email campaign content (subject, body HTML, from name, from email) maps to Mailchimp Campaigns and stored Templates. We export campaign content via the Wishpond API and recreate as Mailchimp Regular Campaign or Automation types depending on the Wishpond campaign type. Drip sequences map to Mailchimp Customer Journeys; we document the sequence order and timing delays as a rebuild guide rather than migrate automation logic as code. Campaign-level metrics (open rate, click rate) export as CSV from Wishpond and are delivered as a separate reporting artifact for the customer to ingest into their BI tool.

Wishpond lead capture forms, including field names, field types, and associated landing page associations, export as form metadata. We map Wishpond custom form fields to Mailchimp Audience merge fields and deliver a form rebuild guide referencing Mailchimp's Embedded Form or Hosted Form builder. Wishpond's form logic (conditional fields, progressive profiling) does not migrate; we document the conditional rules for manual rebuild in Mailchimp.

Wishpond landing pages export as page metadata, URL structure, copy, and form configurations. Mailchimp Microsites provide a basic page builder but are not equivalent to Wishpond's drag-and-drop landing page builder. We deliver a page inventory with copy, structure, and form field mapping. The customer rebuilds visual layouts using Mailchimp Microsites, their existing CMS, or a landing page tool like Carrd, Leadpages, or Unbounce. Landing page URLs require redirect planning if the Wishpond domain is being retired.

Exit-intent and embedded popups from Wishpond export as popup configuration metadata including trigger conditions and display rules. Mailchimp does not have a native popup product; the popup configuration becomes a rebuild guide for Mailchimp-compatible popup tools (Privy, OptinMonster, or Sleeknote) or embedded Mailchimp forms on the customer's website. We capture popup targeting rules and associate them with the corresponding Wishpond landing page for cross-referencing during rebuild.

Wishpond automation workflows export as a JSON schema documenting trigger, conditions, actions, delays, and A/B test variants. Mailchimp Customer Journeys use a different automation model (entry triggers, conditions, time delays, and actions specific to Mailchimp's architecture). We do not migrate workflows as code. We deliver a written workflow inventory with each Wishpond workflow mapped to a recommended Mailchimp Customer Journey equivalent, including trigger mapping (e.g., Wishpond 'form submitted' maps to Mailchimp 'joins Audience' trigger) and a note on which Wishpond-specific actions have no Mailchimp equivalent. The customer's admin or a marketing implementation partner rebuilds the automations post-migration.

Referral marketing campaigns from Wishpond export as campaign records with participant lists and reward mechanics. Referral tracking codes map to Mailchimp Tags on Subscriber records, and referral participants are loaded as Subscribers tagged with the campaign name. Mailchimp does not have native referral reward mechanics; we document the referral program structure for rebuild using a dedicated referral tool (ReferralCandy, Ambassador, or Post affiliate) integrated with Mailchimp via Zapier.

Contest entries export as Lead records tagged with contest metadata. We load these as Mailchimp Subscribers with tags identifying the contest source and entry date. Campaign-level contest analytics (total entries, winner selection criteria) export as CSV and are delivered as a reporting artifact. Mailchimp has no native contest functionality; the visual contest experience rebuilds in Wishpond alternatives like Vyper, Gleam, or Sweepwidget integrated with Mailchimp audiences.

Historical open rates, click rates, conversion rates, and lead attribution export as time-series CSV from Wishpond. We chunk large analytics exports to respect Wishpond's 60-second API rate limit and deliver them as CSV files organized by campaign and month. Mailchimp's Standard and Essentials plans limit engagement history migration to 90 days for native sync; legacy Wishpond data before the 90-day window must be imported manually via CSV. We flag this boundary during scoping so the customer can request a full historical export before cutover begins.