Migrate from Wishpond to Salesforce Sales Cloud

Wishpond's primary data object is the Lead record, representing contacts captured via landing pages, forms, popups, and contests. Standard fields (name, email, phone if provided) map to Salesforce Contact. If the customer wants to preserve unqualified prospect data separately, we also create Salesforce Lead records and run a split based on lead source and capture context. We flag Wishpond's common data quality issue: lead records frequently lack phone numbers, so we create a custom field wishpond_phone_missing__c as a boolean flag so the sales team knows which records need enrichment on follow-up. The original Wishpond lead ID is stored in a custom field wishpond_lead_id__c on the Salesforce record for reconciliation.

Wishpond Landing Pages cannot migrate as visual assets because they are hosted on Wishpond's platform with platform-specific URL structure, embedded forms, and drag-and-drop layout metadata that has no Salesforce equivalent. We export page metadata (title, URL slug, headline, body copy, form associations) as a JSON schema document. The customer's admin rebuilds pages in Salesforce Experience Cloud, a CMS, or a third-party landing page tool (Unbounce, WordPress + form plugin). We deliver the full page content as structured copy so that no text is lost.

Wishpond Email Campaigns (including drip sequences and A/B variants) map to Salesforce Campaign. Campaign metadata (name, start date, status, type) migrates directly. Email subject lines, body content, and template variables are exported as a CSV attachment in the Campaign Description field or as a ContentDocument attached to the Campaign. We do not migrate email assets as Salesforce Email Templates because the template structure and merge field syntax differ between platforms. Campaign member status (Subscribed, Unsubscribed, Bounced) migrates to CampaignMember Status on each Contact.

Wishpond campaign analytics (open rates, click rates, conversion rates, bounce counts) are exported as time-series CSV because the API does not expose them as structured objects. We chunk large analytics exports into monthly segments to respect the 60-second API rate limit, then load the data into Salesforce custom fields on the Campaign record (e.g., wishpond_open_rate__c, wishpond_click_rate__c, wishpond_conversion_rate__c) and as notes on the Campaign for historical reporting.

Wishpond Forms (including custom field names, field types, and associated landing page associations) are exported with field-level detail. We map each Wishpond form field to either a Salesforce standard field or a custom Contact/Lead field with matching data type. If the customer uses Salesforce Web-to-Lead as the replacement form tool, we deliver a field mapping guide that shows which Wishpond form fields map to which Salesforce form fields. Forms that used conditional logic or progressive profiling require manual rebuild in the Salesforce form tool.

Wishpond automation workflows (trigger-action sequences such as 'if form submitted, add to drip sequence, then wait 3 days, then send email') are exported as a JSON schema representation showing the trigger, conditions, actions, and delays. Salesforce Flow uses a different execution model (record-triggered, scheduled, screen, platform event variants) with different action types and governor limits. We do not migrate Workflows as code. We deliver a written inventory of every active Wishpond Workflow with its trigger type, conditions, action sequence, and a recommended Salesforce Flow equivalent so the customer's admin or a Salesforce partner can rebuild them.

Exit-intent and embedded popups with targeting rules export as configuration metadata (trigger conditions, display rules, associated form, copy content) in JSON format. Salesforce has no native popup feature; the replacement is typically a third-party tool (OptinMonster, Sumo, or a marketing site CMS plugin). We deliver the popup configuration as structured copy and targeting rules so the marketing team can reproduce the logic in their chosen replacement tool.

Referral marketing campaigns with reward mechanics export as Campaign records with referral-specific metadata (reward type, participation tracking, referral codes). Referral participant lists export as Salesforce Contacts tagged with a custom field wishpond_referral_program__c set to the referral campaign name, and referral codes stored in wishpond_referral_code__c. The customer's Salesforce admin rebuilds the referral tracking logic in Salesforce using Flow or a third-party referral tool.

Contest entries in Wishpond are tracked 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 the contest affiliation in a custom field wishpond_contest_name__c. Winner status and prize awarded (if tracked in Wishpond) migrate to custom fields wishpond_contest_winner__c and wishpond_contest_prize__c on the Contact.

A/B test configurations for landing pages and email campaigns export with variant metadata (variant names, traffic allocation percentages, winner criteria, test duration). We map this data to Salesforce Campaign custom fields (e.g., wishpond_ab_test_variant_a__c, wishpond_ab_test_variant_b__c, wishpond_ab_traffic_split_pct__c) so that the customer's analytics team can recreate the test reporting in Salesforce or a BI tool. The visual A/B test builder does not migrate.

Wishpond user accounts including name, email, and role export as user records. We resolve Wishpond users by email against the Salesforce destination org's User table. If the customer wants Salesforce to reflect the same team structure, the admin provisions matching User accounts (active or inactive depending on whether the original Wishpond user is still employed). Role hierarchy migrates to Salesforce Role Hierarchy if the customer wants the same reporting structure.

Wishpond stores integration credentials (Salesforce sync, Mailchimp connection, Shopify connection) as platform-level settings rather than customer data. These credentials cannot be exported or migrated—they must be reconfigured in the destination platform by the customer's admin. We flag which integrations were active in Wishpond and note them in the migration handoff document so the admin can set them up in Salesforce or replace them with equivalent AppExchange apps. This includes any existing Wishpond-to-Salesforce sync configuration which will be replaced by Salesforce's own native sync settings or a new AppExchange connector.