Migrate from Wavity CRM to Pipedrive

Wavity Lead records with name, email, phone, source attribution, status, and scoring values map directly to Pipedrive People records of type Person. We preserve lead source as a custom field on the Pipedrive Person. The Wavity lead status property maps to the first pipeline stage in Pipedrive so that imported Leads enter the correct pipeline position.

Wavity Contact records map 1:1 to Pipedrive People. Standard fields (name, email, phone) map directly; custom field values on Wavity Contacts migrate to matching custom fields we pre-create in Pipedrive before the import phase. The bidirectional Contact-Account relationship resolves to Pipedrive's Person-Organization link, which we establish after Organizations are imported.

Wavity Account records map directly to Pipedrive Organization. Organization is imported before People so that the Organization-Person link is satisfied at the moment of Person insert. The Wavity Account domain becomes the Organization's Website field and serves as the dedupe key to prevent duplicate Organizations during import.

Wavity Opportunity records with deal value, stage, probability, and owner assignment map to Pipedrive Deal. The pipeline stage name and probability migrate from Wavity's pipeline configuration to Pipedrive's stage definition within the chosen pipeline. Closed-Won and Closed-Lost reasons from Wavity custom fields become Pipedrive custom fields for reporting consistency.

Each Wavity pipeline with its user-defined stages, stage order, and probability percentages is extracted as a configuration record and recreated as a Pipedrive Pipeline. We match Wavity stage names to Pipedrive stage names and map probabilities to Pipedrive's stage probability values. Pipedrive's visual pipeline builder receives the stage schema before any Deal import begins.

Wavity Task records with due date, assignee, status, and linked objects (Contact, Opportunity) map to Pipedrive Activities. Task status (open, completed) maps to Pipedrive Activity done status. Assignment in Wavity (linked to a user record by owner ID) resolves to the Pipedrive user by email match before Activity import.

Wavity Appointment records with start time, duration, attendees, and linked Contact or Opportunity map to Pipedrive Activity records of type Meeting. We preserve timezone awareness by migrating the original appointment timestamp and setting the Activity due field accordingly. Linked attendees resolve to Pipedrive Person or Organization records that have already been imported.

Wavity Tickets with status, priority, assignee, customer link, and conversation history require a migration strategy decision during scoping. Pipedrive's core CRM does not include a native ticket object; if the customer licenses Pipedrive's Help Desk add-on ($19/seat/mo), tickets map to Pipedrive Tickets. Without the add-on, tickets can migrate to Deals in a separate pipeline (with ticket-type pipeline configured) or to Activity records with a ticket reference field. We document both options and the customer chooses before migration.

Wavity's Zero Code Application Designer custom objects lack a standard export format and require pre-migration schema discovery. We schedule a schema review call with the customer to document every custom object, field type, validation rule, and relationship to standard Wavity objects. We then pre-create equivalent Pipedrive custom fields on the relevant standard objects (Person, Organization, Deal) before migration. Custom object schemas that cannot map to standard Pipedrive objects are flagged for the customer's admin to handle post-migration in Pipedrive's custom fields UI.

File attachments stored in Wavity are exported as a file bundle and re-uploaded to Pipedrive, preserving the attachment-to-record linkage via ContentDocumentLink equivalents in Pipedrive's file association model. We map each attachment to the correct Person, Organization, or Deal using the Wavity record ID preserved during the Person and Organization import phase.

Wavity User records with name, email, role, and active/inactive status map to Pipedrive Users. We match by email address. Any Wavity user marked inactive is flagged for the customer to review before provisioning in Pipedrive, ensuring that only active users consume a Pipedrive seat. Role and permission structure is documented as a written handoff since Pipedrive's permission model differs from Wavity's custom roles.