Migrate from Wishpond to HighLevel

Wishpond Lead records map directly to GoHighLevel Contact. Standard fields (first name, last name, email, phone if present) migrate as typed Contact fields. Wishpond custom lead properties migrate as GoHighLevel custom fields on Contact. We preserve the original Wishpond lead source (landing page URL, form name) in custom fields for attribution analysis. Wishpond lead records without email are flagged during reconciliation for the customer's admin to review before import completes.

Wishpond landing pages export as page metadata including URL structure, page title, copy content, and form associations. GoHighLevel's Snapshot feature captures landing page structure for migration, though the visual layout requires manual recreation in GoHighLevel's funnel builder. We deliver a written inventory of every Wishpond landing page with its URL, associated form, and lead volume for the customer's admin to prioritize during GoHighLevel funnel recreation.

Wishpond lead capture forms, including field names, field types, and associated landing page links, map to GoHighLevel Forms. Custom fields created within Wishpond map to GoHighLevel contact custom fields of equivalent type. Form submission source (popup, landing page, contest) is preserved as a tag on the Contact record for segmentation in GoHighLevel.

Wishpond email campaigns with drip sequences and A/B variants export as GoHighLevel Campaigns with email content preserved. Campaign-level metrics (open rates, click rates, conversion rates) export as time-series CSV and are delivered as attachments for the customer to reference in GoHighLevel reporting. GoHighLevel's LC Email infrastructure requires SPF/DKIM/DMARC authentication before campaigns send from migrated content, which we configure during the deliverability setup phase.

Wishpond automation workflows (trigger-action sequences such as 'if form submitted, add to drip sequence') export as JSON schema documenting every trigger, condition, delay, and action. GoHighLevel Workflows require manual rebuild using GoHighLevel's visual automation builder because Wishpond automation logic does not transfer as executable code. We deliver a written workflow inventory with trigger types, condition logic, and recommended GoHighLevel Workflow equivalents for the customer's admin to rebuild post-migration.

Wishpond exit-intent and embedded popups export with trigger conditions, display rules, and associated form configuration. Popup targeting rules map to GoHighLevel form submission conditions and contact tagging. The visual popup layout does not migrate; the customer recreates popup appearance in GoHighLevel's form builder or workflow triggers.

Wishpond referral campaigns with reward mechanics export as GoHighLevel Campaigns with referral-specific tags on participant contacts. Referral tracking codes and participant lists map to a GoHighLevel Custom Object (e.g., ReferralParticipant) with fields for referral_code, reward_status, and contact_id, linked to the Contact via lookup relationship. We create the custom object schema in GoHighLevel during migration setup.

Wishpond user accounts (name, email, role) map to GoHighLevel Users. Wishpond role permissions (Admin, Manager, Member) map to GoHighLevel permission levels. Active vs. inactive status migrates to User.isActive in GoHighLevel. We resolve users by email match against the GoHighLevel destination account, flagging any Wishpond users without a matching GoHighLevel account for the customer's admin to provision before import.