Migrate from Wishpond to Freshsales

Wishpond Leads are the primary data object and map directly to Freshsales Contacts. Standard fields (name, email, phone) migrate cleanly. We map Wishpond's lead source field to Freshsales's Lead Source picklist. Any phone number gaps (a documented Wishpond weakness where records often lack phone) are flagged in the reconciliation report. Custom fields captured via Wishpond forms map to Freshsales custom Contact properties, with field types matched (text to text, number to number, date to date). Wishpond lead scoring values migrate to Freshsales custom fields if the customer has Freddy AI configured.

If the customer has a pre-sales qualification process in Wishpond where leads are manually scored or tagged before entering the sales pipeline, we map those unqualified records to Freshsales Lead for routing through a sales process before conversion to Contact on an Account. The split rule is defined during scoping based on the customer's lead status values.

Landing page metadata (page title, URL, creation date, traffic source) migrates as Note records attached to the associated Contact. We do not migrate landing page layouts or visual content as Freshsales has no native landing page builder. The customer's admin rebuilds landing pages in their preferred tool post-migration. We deliver a written inventory of all active landing pages with URLs and traffic data for reference.

Wishpond form field definitions (field name, field type, associated landing page) export as metadata. Form responses are already embedded in the Lead export as field-value pairs. We map Wishpond custom form fields to Freshsales custom Contact properties, creating the properties in Freshsales before import. Form-to-field mapping is preserved in the inventory document.

Wishpond email campaign participation (which contact received which campaign email, and campaign-level metrics like open and click status) maps to Freshsales Contacts with Tags for campaign membership. Campaign-level performance data (open rates, click rates) migrates as a separate CSV inventory for the customer's admin to use in Freshsales Reports. Drip sequence logic does not migrate as automation; we document the sequence steps for manual rebuild in Freshsales Workflows or Freshmarketer Journeys.

Wishpond automation workflows export as JSON schema documenting trigger conditions, delay actions, CRM updates, and email sends. We do not migrate workflows as code because Freshsales Workflows use a different trigger-action model. We deliver a written inventory of every active workflow with its structure mapped to Freshsales Workflow equivalents where applicable. The customer's admin rebuilds automations post-migration.

Wishpond User accounts (name, email, role) map to Freshsales User records. We resolve by email match. If a Wishpond user has no corresponding Freshsales user, we hold them in a reconciliation queue for the admin to provision before the main record import runs. Wishpond role permissions map to Freshsales role assignments at the admin's direction.

Wishpond A/B test configurations (test name, variants, traffic split, winner criteria) export as campaign metadata. The variant data and allocation percentages are preserved in an inventory document. Freshsales has no native A/B test object; the customer's admin recreates test logic as Freshsales Workflows or in Freshmarketer if marketing experimentation continues.