Migrate from Wavity CRM to Microsoft Dynamics 365 Sales

Wavity Contact records map directly to Dynamics 365 Contact. Standard fields (full name, email, phone, address) migrate 1:1. Custom contact fields built in Wavity's form designer require type-mapped equivalents in Dynamics 365 (text to Single Line of Text, date to Date Only, dropdown to Option Set). The Wavity Contact-Account relationship maps to the Dynamics Contact.parentcustomerid Account lookup, resolved by matching Account names during the Accounts-phase insert.

Wavity Account records map to Dynamics 365 Account. The Wavity company name becomes Account.name; industry and website fields map directly. Accounts are migrated first in the sequence so that Contact records can satisfy their parent Account lookup at insert time. Any Wavity custom fields on Accounts are mapped field-by-field after the standard schema is validated in the sandbox phase.

Wavity Lead records map to Dynamics 365 Lead. Lead status values (New, Contacted, Qualified, Disqualified) require an explicit mapping table because Wavity allows custom lead status names. We preserve Wavity's lead scoring values in a custom field wavity_lead_score__c on the Dynamics Lead. Source attribution (LeadSource) migrates from Wavity's lead source property.

Wavity Opportunity records map to Dynamics 365 Opportunity with estimatedvalue, closeprobability, and estimatedclosedate preserved. Each Wavity pipeline stage name requires an explicit mapping to a Microsoft Dynamics 365 Sales Process stage. We extract the full stage list from Wavity during discovery and configure matching stage values in Dynamics before the production migration begins.

Wavity pipelines are user-defined with custom stage names and probabilities. We extract the full stage schema during discovery, then configure equivalent Microsoft Dynamics 365 Sales Processes and Opportunity Record Types. Each Sales Process whitelists the stage values that correspond to one Wavity pipeline, preserving the stage ordering and probability percentages. Customers with multiple Wavity pipelines get multiple Record Types in Dynamics.

Wavity Tasks migrate to Dynamics 365 Task records with subject, description, scheduledend (due date), and statecode (open/completed) preserved. Task ownership migrates by matching Wavity owner email to Dynamics User.emailaddress1. Tasks linked to Contacts or Opportunities carry the Regarding (regardingobjectid) lookup resolved after the parent records are inserted.

Wavity Appointments migrate to Dynamics 365 Appointments with starttime, endtime, location, and description preserved. If the Wavity appointment is a call record (distinguished by type flag in the export), we map it to Task with TaskSubtype=Call and preserve duration in a custom field. Attendees map to EventRelation records linked to the Contact or Lead.

Wavity Tickets migrate to Dynamics 365 Case records when the destination org includes Service Cloud licensing or the customer selects Case as the help desk equivalent. Ticket status (Open, In Progress, Resolved, Closed) maps to Case Status values via an explicit mapping table. Ticket priority migrates to Case Priority. Conversation threads on tickets migrate as EmailMessage records linked to the Case, and any SLA data in Wavity is documented for manual reconfiguration in Dynamics 365 SLA settings.

Wavity custom objects built with the Zero Code Application Designer have no standard export format and no direct Dynamics equivalent. We schedule a schema discovery call to document every custom object, its field types, validation rules, and lookup relationships to standard objects. We then pre-create matching Dataverse custom tables in Dynamics, including all attributes and relationships, before any custom object data is written. Relationship integrity (lookups to Contact, Account, or Opportunity) is resolved at migration time using the identifiers established during standard object inserts.

Wavity User records map to Dynamics 365 User by email address. Inactive Wavity users are flagged during scoping and held in a reconciliation queue; the customer's Dynamics admin decides whether to provision inactive users as deactivated records or omit them entirely. Role and permission sets from Wavity are documented in the handoff inventory for manual reconfiguration in Dynamics 365 security roles post-migration.