Migrate from Wishpond to Twenty CRM

Wishpond's primary Lead object maps to Twenty's Person object. The key schema difference is that Wishpond stores a single full-name field while Twenty uses separate firstName and lastName fields. We split the Wishpond name value on the first space and map remainder to lastName. Email maps to Twenty's email field. Phone is optional in Wishpond and may be absent; we set it where available and flag the gap for enrichment. Wishpond custom properties (hs_lead_status, lifecyclestage, utm_source) map to Twenty custom fields that we pre-create during schema setup.

When a Wishpond Lead includes company name data (from a form field or enrichment), we create a corresponding Company record in Twenty and link the Person to it via a foreign key. We use the Wishpond lead's company domain or name as the Company name field. Company-Person relationships are established before Person records are finalized to avoid orphaned lookups.

Wishpond landing pages have no native equivalent in Twenty's object model. We export page metadata (name, URL slug, creation date, associated form) as a Note attached to the Person record that captured leads from that page. The note body captures the page URL and copy structure. Visual layout and form builder configuration are not transferable and are documented in the landing-page inventory handed to the customer's admin for rebuild in Twenty's workspace or via the customer's web stack.

Wishpond form field definitions (field names, field types, required flags) map to custom field definitions on Twenty's Person object. We create the custom fields before lead import so that form-captured data lands in the correct properties. The mapping between Wishpond form field IDs and Twenty custom field API names is documented in the field mapping appendix. Form logic (conditional fields, skip logic) is not migratable and is noted for rebuild.

Wishpond email drip campaigns and A/B test configurations export as campaign records with variant metadata and traffic allocation. We create a Note record per email campaign, linked to the Person record, with campaign name, status, and A/B variant data in the note body. Campaign-level metrics (open rates, click rates) export as time-series CSV and are preserved as Note attachments. The email content itself (HTML body, subject lines) is exported and documented as a content reference for the customer's email platform rebuild.

Referral campaigns with reward mechanics export as campaign records with participant lists. Referral participants map to Person records tagged with a referral source identifier. Reward tier information maps to a custom field on Person. The referral tracking codes are preserved as activity metadata. Reward configuration (thresholds, discount types) is documented in the campaign inventory for rebuild by the admin.

Contest entries in Wishpond are lead records tagged with contest metadata. We export these as Person records in Twenty with a contest_name tag and a contest_entry_date custom field. Where Wishpond tracks contest participation separately from standard leads, we merge into the unified Person export. Winner and reward data map to custom fields.

Exit-intent and embedded popups with targeting rules export as campaign assets. We capture popup configuration (trigger conditions, display rules, associated form) as a Note attached to the Person record that triggered the popup. Visual design and targeting logic do not migrate; these are documented for rebuild by the admin.

Wishpond automation workflows (trigger-action sequences such as 'if form submitted, add to drip sequence') export as JSON schema describing the workflow structure. We do not migrate workflows as code into Twenty because Twenty's sequence and automation model is early-stage and does not have an equivalent visual workflow builder. The workflow inventory document includes every active automation with trigger conditions, action sequence, delays, and a recommended rebuild approach in Twenty Sequences.

Wishpond user accounts (name, email, role) export as user records. We map Wishpond roles to Twenty workspace roles and permissions. Active vs. inactive status is preserved. Twenty requires manual user provisioning through workspace settings; we deliver the user mapping list to the customer's admin for provisioning before record migration.

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 manage volume. The CSV is attached as a Note to the relevant campaign record or as a workspace file reference. The customer can import this into a BI tool or use Twenty's reporting capabilities to reconstruct dashboards.