Migrate from Wishpond to Microsoft Dynamics 365 Sales

Wishpond Leads map to Microsoft Dynamics 365 Sales Contact for qualified records or Lead for unqualified prospects. We apply a lifecycle-stage split rule during scoping: leads with a confirmed email and at least one engagement (form submission, email click, or campaign interaction) map to Contact linked to an Account; raw leads with no engagement history map to Dynamics Lead. Any phone number present in Wishpond maps to Contact's Telephone field; records without phone numbers are flagged as enrichment candidates because Microsoft Dynamics 365 Sales ' built-in calling and SMS features require a populated phone field. The original Wishpond lead source (landing page, popup, contest, referral) migrates as a custom field on both Lead and Contact for attribution reporting.

Wishpond landing pages have no direct Microsoft Dynamics 365 Sales equivalent since Dynamics lacks a native page-builder module. We extract page metadata (URL slug, page title, associated form, traffic-source tags, and publish status) and load it as a Dynamics Campaign record with the page URL in the Campaign Website field. The visual layout and copy must be rebuilt manually post-migration in SharePoint Online, a Power Apps portal, or a third-party landing page tool. We deliver a written landing-page inventory with page-by-page mapping notes so the customer's marketing team can recreate layouts efficiently.

Wishpond email campaigns with drip sequences and A/B variants map to Dynamics 365 Campaign records. Campaign name, start and end dates, and target audience segments migrate as Campaign Member query strings. The email body content migrates as a Campaign Note attachment so the customer's team can reference it when rebuilding in Dynamics-compatible email tools (Dynamics 365 Email Templates, Outlook, or a third-party email platform). A/B variant metadata and traffic-allocation percentages migrate as a Campaign Note JSON attachment.

Wishpond lead-capture forms with standard fields (name, email, phone, company) map to equivalent Contact fields in Microsoft Dynamics 365 Sales . Custom Wishpond form fields (e.g., Number of Employees, Industry, Product Interest) map to custom Contact fields created in Dynamics before migration. Form-to-landing-page associations are preserved as a Note on the related Campaign record so the customer's team can reconnect forms if they use a third-party form tool post-migration.

Wishpond automation workflows do not migrate as functional objects into Microsoft Dynamics 365 Sales because the two platforms use incompatible automation models. We export the workflow structure as a JSON schema documenting every trigger (form submitted, email opened, date-based), condition (field equals, contact tagged), and action (add to sequence, update property, notify). This JSON schema serves as the specification for rebuilding in Power Automate or Dynamics workflow designer post-migration. The customer's admin or a Microsoft partner rebuilds the automations; FlitStack AI does not include workflow rebuild in the standard migration scope.

Wishpond popup campaigns, referral marketing campaigns, and contests generate leads tagged with campaign attribution metadata. These migrate as Dynamics 365 Campaign Member records linked to the corresponding Campaign, with the original Wishpond campaign type (popup, referral, contest) stored in a custom Campaign Member field. Participant lists and reward mechanics from referral and contest campaigns migrate as Campaign Notes for manual reconstruction in Dynamics if the customer wants to recreate the programs.

Historical campaign open rates, click rates, conversion rates, and lead attribution data export from Wishpond as time-series CSV. We attach these CSVs to the corresponding Dynamics 365 Campaign record as Notes with the date range and metric type in the Note title. Microsoft Dynamics 365 Sales does not have native campaign analytics of this depth; the customer's team uses the attached CSVs for historical reporting or connects Dynamics to Power BI for visualization. For large analytics exports (over 5,000 data points), we chunk the CSV by month to respect the Wishpond API rate-limit window.

Wishpond user accounts including name, email, and role export as a provisioning list for the customer's Dynamics 365 admin. We match Wishpond Owner references on Lead, Campaign, and Engagement records by email to existing Dynamics 365 Users. Any Wishpond Owner without a matching Dynamics User is flagged in a reconciliation report for the admin to provision before record import resumes. Inactive Wishpond users are mapped to inactive Dynamics Users so historical assignment records remain intact.