Migrate from Wishpond to monday CRM

Discovery and plan verification

We audit the source Wishpond account across tier (Starter, Pro, Growth), active lead count, custom form fields, active campaigns, automation workflows, and contest configurations. We verify the customer's current plan tier because it determines whether API-based extraction is available or manual CSV export is required. We pair this with a Monday.com CRM workspace audit confirming the CRM board structure, existing custom columns, and user provisioning. The discovery output is a written migration scope with record counts, field coverage assessment, and a plan for handling incomplete lead data.

Field mapping and column design

We design the Monday.com CRM column schema to receive Wishpond data. This includes mapping standard fields (name, email, phone, company) to Monday.com CRM contact columns, creating custom columns for Wishpond-specific attributes (landing page source, form name, UTM parameters, contest tags), and configuring the Companies board with linked contacts. For Wishpond Starter-tier accounts using manual CSV export, we map only the fields available in the dashboard export and note any Wishpond API-only fields that will require manual entry post-migration.

Lead extraction under rate-limit constraints

For Pro and Growth tier accounts, we extract leads via the Wishpond API using 65-second delays between 100-record batches to avoid the 60-second blocking window. For Starter-tier accounts, we provide a CSV export template and guide the customer through the dashboard export process. We flag records missing phone numbers and export them to an enrichment queue. We extract form definitions, campaign membership lists, and workflow schemas as JSON metadata documents.

Data quality pass and enrichment sequencing

We run a data quality audit on the extracted leads: identifying duplicates (same email), incomplete records (missing name or email), and records lacking phone numbers. We apply a deduplication pass before import using email as the primary key. Records missing phone numbers are flagged with a 'phone missing' custom column and sequenced for batch enrichment via a third-party data provider. This step is scoped separately unless included in the engagement. We deliver a data quality report before production import begins.

Production import in dependency order

We run production import in record-dependency order: Companies first (as standalone items), then Contacts with the Company relationship resolved, then campaign membership tags applied to contacts, then user reconciliation (matching Wishpond users to Monday.com workspace members by email). Each phase emits a row-count reconciliation report before the next phase begins. Any Wishpond user without a matching Monday.com account is held in a reconciliation queue for the customer's admin to provision.

Cutover, validation, and automation handoff

We freeze Wishpond writes during cutover and run a final delta migration of any records modified during the migration window. We validate a random sample of imported records against the Wishpond source data, checking name, email, phone, company linkage, and tag accuracy. We deliver the automation inventory document (Wishpond workflows documented with Monday.com equivalents), the landing page reference document, and the campaign metrics CSV. We support a one-week hypercare window for reconciliation issues. Rebuilding Wishpond Workflows in Monday.com's automation builder is outside the migration scope and is documented as an admin task or separate engagement.