Migrate from Wishpond to Pipedrive

Wishpond Lead records map to Pipedrive Person. Standard fields (name, email, phone if present, source campaign) migrate directly. We flag records missing email addresses since Pipedrive Person requires a name but email deduplication is the primary match key. For leads requiring follow-up before deal creation, Pipedrive's Lead object is used instead; for leads with clear purchase intent, they map directly to Person with an associated Deal created from the campaign score or a manual Deal creation step during migration scoping.

Wishpond tracks which landing page, form, popup, or contest captured each lead. We map the source campaign name to a Pipedrive Activity Note attached to the Person record. If the customer wants to track pipeline by campaign, we optionally create a Deal per high-intent campaign and attach the Person to it. The campaign attribution is preserved as a custom field (wishpond_source__c) on the Person record rather than lost in the transition.

Wishpond Email Campaigns with drip sequences and A/B variants are exported as campaign metadata records. Campaign names, send dates, and subject lines migrate as Activity Notes or custom fields on the associated Person records. Wishpond's open rate, click rate, and conversion metrics export as CSV and are loaded as custom numeric fields (wishpond_open_rate__c, wishpond_click_rate__c) on the Person record for reporting. We do not recreate email templates or drip sequences in Pipedrive; these are documented for rebuild.

Wishpond custom fields created within campaigns and forms (e.g., company_size, product_interest, event_attended) map to Pipedrive custom fields on the Person object. We pre-create the destination schema in Pipedrive before migration, matching field types: text to text, number to number, date to date, picklist to picklist. Multi-select fields from Wishpond require Pipedrive custom field pre-creation with the same options list. Field-level validation rules in Pipedrive are confirmed against the Wishpond data before import to avoid rejection.

Wishpond Contest entries export as Lead records tagged with contest metadata (contest name, entry date, prize tier). We merge these into the unified Person export and add a tag (e.g., 'Contest Participant') in Pipedrive. The contest-specific fields (entry_date__c, contest_name__c) migrate as custom Person fields if the customer wants to track contest-sourced leads separately in Pipedrive reporting.

Wishpond Referral Campaign participants export as Lead records with referral tracking codes. We map these to Pipedrive Person records with a referral_campaign__c custom field and a 'Referral' tag. The referral reward status (if tracked in Wishpond) migrates as a custom field for the customer's sales team to act on in Pipedrive.

Wishpond lead capture forms, including field names, field types, and associated landing page associations, export as form metadata. The form fields map to Person custom fields in Pipedrive where applicable. The form submission itself is not recreated; we document the form structure for the customer to rebuild using Pipedrive Web Forms or a third-party form tool if ongoing lead capture is needed.

Exit-intent and embedded popup configurations export as campaign asset metadata. Trigger conditions, display rules, and associated forms are documented in the migration inventory but do not map to a native Pipedrive object. We document popup configuration for the customer to implement in a replacement popup tool (e.g., OptinMonster, Sumo) integrated with Pipedrive via Zapier or native integration.

Wishpond User accounts (name, email, role) export as User records. We map Wishpond roles to Pipedrive permission sets: Admin to Pipedrive Admin, Standard User to Pipedrive regular User. Active versus inactive status is preserved. The customer's Pipedrive admin provisions User accounts before migration; we resolve the owner assignment by email match on Person and Deal records during import.

Wishpond Landing Pages export as page metadata (URL structure, title, copy). Landing pages are not migrated to Pipedrive since Pipedrive has no landing page hosting capability. We deliver a written inventory of all active landing pages with URL, copy summary, and conversion goal for the customer's web team to rebuild on a landing page platform (e.g., Unbounce, WordPress, or Webflow) integrated with Pipedrive.

Wishpond automation workflows export as JSON schema documenting trigger-action sequences (e.g., 'if form submitted, add to drip sequence'). These do not migrate to Pipedrive Workflows because Wishpond and Pipedrive use different trigger models and action types. We deliver a written workflow inventory with trigger, conditions, actions, and recommended Pipedrive Workflow equivalent for the customer's admin to rebuild in Pipedrive's automation builder.

Historical open rates, click rates, conversion rates, and lead attribution export as time-series CSV. We chunk large analytics exports into monthly segments to respect Wishpond's API rate limits. The aggregated metrics load as custom numeric fields on the associated Person records. A full analytics CSV archive is delivered alongside the migration for the customer to store or load into a BI tool.