Migrate from Wishpond to Nutshell

Wishpond Leads map to Nutshell People records as the primary object. We derive a Company record for each Lead by parsing the email domain (e.g., acme.com from [email protected]) and creating a Nutshell Company with that domain as the name and website. Each Person record is linked to its parent Company via the Company field in Nutshell. Source attribution fields (landing page name, form name, campaign tag) from Wishpond are stored as Nutshell custom fields on the Person record for attribution continuity. Wishpond Lead notes and tags migrate as Person notes and tag assignments respectively.

Wishpond Users with name, email, and role export and map to Nutshell User accounts. We match by email address. Inactive Wishpond users are provisioned as inactive Nutshell users to preserve historical assignment data. Role mapping (Admin, Member, Sales) maps to Nutshell's permission model on a field-by-field basis.

Wishpond Landing Pages are visual content objects without a direct Nutshell equivalent. Nutshell does not have a landing page builder. We export page metadata (page name, URL slug, creation date) and a written inventory of all landing pages with their URL, associated form, and traffic volume from Wishpond's analytics export. The customer uses this inventory to recreate pages in their chosen landing page tool (Carrd, Leadpages, WordPress) and maps the new URLs as custom fields on the migrated Person records.

Wishpond lead capture Forms, including field names, field types, and associated landing page associations, export as a field inventory. We map Wishpond custom form fields to Nutshell custom Person fields, creating them in Nutshell before Lead migration begins. Form logic, conditional field visibility, and multi-step form configurations do not migrate; these are documented in the written handoff for the customer's admin to rebuild in Nutshell or a standalone form tool.

Wishpond Email Campaigns with drip sequences export as campaign records including campaign name, start date, and member list. Campaign membership (which Leads were in which campaigns) migrates as a tag on the corresponding Nutshell Person record (e.g., tag: 'Campaign: Q1 Newsletter'). Campaign-level metrics (open rate, click rate, unsubscribe rate) are exported as a time-series CSV and delivered alongside the migration as a reference document for the customer to import into a reporting tool if needed. Email content itself does not migrate as templated emails in Nutshell.

Wishpond Workflows are trigger-action sequences (e.g., form-submitted triggers a drip email sequence). We export the workflow structure as a JSON schema including triggers, conditions, delays, and actions. This is delivered as a written automation inventory document. Nutshell's sales automation features (task triggers, stage-change actions) are documented as the equivalent replacement. The customer's admin rebuilds the logic in Nutshell or a dedicated automation tool. We do not migrate workflows as executable code.

Wishpond Referral Campaigns export as campaign records with participant lists. Referral participants (the Leads who participated) are tagged in Nutshell with the campaign name and added to a 'Referral' segment documented in the migration handoff. Referral reward status and reward type are stored as custom Person fields if applicable. Nutshell has no native referral tracking object; this data lives as tags and custom fields on Person records.

Wishpond Contest entries export as Leads tagged with contest metadata. We merge contest participants into the standard Person export and assign a tag (e.g., 'Contest: Summer Giveaway') and a custom field capturing contest entry date. Nutshell's native objects do not have a contest equivalent; the contest data is preserved as attribution context on the Person record.