Migrate your Wishpond data

Leads is the primary data object in Wishpond, representing contacts captured via landing pages, forms, popups, and contests. Standard fields (name, email, phone if provided) export cleanly. We map these 1:1 to Contacts in the destination CRM and flag any records missing email addresses as invalid.

Landing pages are Wishpond's core content objects. We export page metadata, URL structure, and copy. The destination platform may require manual recreation of the visual layout if it lacks an equivalent drag-and-drop page builder. We preserve page title, slug, and all form field configurations.

Email campaigns with drip sequences and A/B variants are exported as campaign records and email content. Campaign-level metrics (open rates, click rates) are pulled as CSV attachments since the API does not expose aggregate analytics in a single endpoint. Automation triggers and conditional branching are mapped to equivalent workflow logic in the destination.

Lead capture forms, including field names, field types, and associated landing page associations, are exported. Custom fields created within Wishpond are mapped to custom contact properties in the destination CRM.

Automation workflows are represented as trigger-action sequences (e.g., 'if form submitted, add to drip sequence'). We export the workflow structure as a JSON schema and map it to the destination's workflow or automation engine, noting that complex conditional branching may require manual reconstruction.

Exit-intent and embedded popups with targeting rules export as campaign assets. We capture popup configuration including trigger conditions, display rules, and associated form. Destination rendering depends on whether the target platform supports popup widgets.

Referral marketing campaigns with reward mechanics export as campaign records. The referral tracking codes and participant lists are mapped to the destination as campaign members or contacts tagged with a referral source property.

Contest entries export as lead records tagged with contest metadata. Where Wishpond tracks contest participation separately from standard leads, we merge these into the unified contact export and preserve contest attribution as a custom property.

A/B test configurations for landing pages and email campaigns export with variant metadata and winner criteria. We map variant names and traffic allocation percentages to the destination platform's testing framework where supported.

User accounts including name, email, and role are exported as user records. We map Wishpond roles to equivalent permission levels in the destination platform. Active vs. inactive status is preserved.

Wishpond stores integration credentials (e.g., Salesforce sync, Mailchimp connection) as platform-level settings rather than customer data. These credentials cannot be exported or migrated—they must be reconfigured in the new platform by the customer directly.

Historical open rates, click rates, conversion rates, and lead attribution data export as time-series CSV. We chunk large analytics exports into monthly segments to respect API rate limits. The destination stores these as historical reporting data linked to campaign records.