Migrate from Wavity CRM to Twenty CRM

Wavity Contact records map directly to Twenty People. Standard fields (name, email, phone, address, job title) migrate 1:1. Custom fields on Wavity Contacts require schema discovery before migration; we document each custom field type and create the corresponding Twenty People field via Settings > Data Model before import. The email address on People serves as the dedupe key. All Contact-Account relationship links migrate as People-Company relations in Twenty.

Wavity Account records map to Twenty Company. Company must be imported before People so that the relation field resolves at insert time. We extract the Wavity Account name, domain (website), industry, employee count, address fields, and any custom Account fields, then map them to the equivalent Twenty Company fields. Wavity's Account-Contact bidirectional relationship migrates as Twenty's People-Company link.

Wavity Lead records, which include source attribution, enrichment data, and scoring values, map to Twenty People in the lead context. We preserve Wavity's lead source, status, and any scoring or enrichment fields as custom fields on the Twenty People record. If the customer prefers a separate lead pipeline in Twenty, we create a custom view and a Stage picklist on People to distinguish leads from converted contacts.

Wavity Opportunity records map to Twenty Opportunity with deal name, amount, stage, probability, expected close date, and owner. The Opportunity-Company relation and Opportunity-People (primary contact) relation migrate via lookup resolution at import time. Custom Opportunity fields require pre-creation in Twenty's data model. Closed-Lost and Closed-Won reasons from Wavity become custom Opportunity fields in Twenty.

Wavity's customizable pipeline stages (stage names, order, probability percentages) require extraction from Wavity's UI and recreation in Twenty's Pipeline designer. We export the full stage schema including probability and sort order during discovery, then configure the equivalent Pipeline and Stage values in Twenty before any Opportunity records are imported. Pipeline stage names map directly; probability percentages migrate to Twenty's stage probability field.

Wavity Tasks migrate to Twenty Task records with title, body, due date, assignee (via owner email lookup), status, and priority preserved. Tasks linked to a specific Contact, Account, or Opportunity carry the corresponding Twenty relation at migration time. Completed status and historical completion dates migrate accurately. Wavity's task types (call, email, meeting, general) map to Twenty Task types or Notes depending on the activity subtype.

Wavity calendar appointments, including start time, duration, attendees, location, and linked Contact or Opportunity, migrate to Twenty's calendar event representation. Timezone information is preserved to ensure scheduling accuracy. Attendee relationships migrate as Task relation records linked to the corresponding People in Twenty. Recurring appointment patterns do not have a standard equivalent in Twenty and are converted to individual event records.

Wavity Help Desk Tickets do not have a direct standard equivalent in Twenty, which currently lacks a native service desk module. We create a Case custom object in Twenty's data model during migration, mapping ticket fields (status, priority, assignee, customer link, conversation thread) to the equivalent custom fields. Conversation history migrates as a rich-text field or series of linked Note records. SLA configuration from Wavity is documented for manual rebuild in Twenty.

Wavity Zero Code Designer custom objects require schema discovery before any data can migrate. We schedule a dedicated schema review session with the customer to document every custom object definition: field names, field types (text, number, date, picklist, relation), validation rules, and lookup relationships. We then create the equivalent custom object and fields in Twenty's Settings > Data Model before importing any custom object records. This is the highest-risk object in the migration and adds 3-5 days to the discovery phase.

Wavity User records (name, email, role, permissions) map to Twenty Workspace Users. We match by email as the reconciliation key. Inactive Wavity users are flagged and held in a reconciliation queue; the customer decides whether to provision inactive users in Twenty or exclude them from migration. Role and permission structures differ between platforms and are documented for manual reconfiguration in Twenty's Settings > Workspace.

File attachments stored in Wavity are exported to local storage and re-uploaded to Twenty as linked attachments. We preserve the attachment-to-record linkage (Contact, Account, Opportunity, or Task) during migration so that documents remain associated with the correct record in Twenty. Large file attachments (>25 MB) require chunked upload handling. We document the full attachment inventory during discovery to scope the re-upload effort accurately.