Migrate from Wavity CRM to Zoho CRM

Wavity Contact records with name, email, phone, address, and custom field values map 1:1 to Zoho CRM Contact. The contact's associated Wavity Company (if any) resolves to a Zoho Account before Contact import so that the Account-Contact lookup linkage is satisfied at insert time. Any lifecycle or lead-type flags used in Wavity to distinguish prospect types from customer contacts are preserved as a custom field on the Zoho Contact for reporting continuity.

Wavity Company records map directly to Zoho CRM Account. The company domain or website URL becomes the Account's Website field and is used as the dedupe key during CSV import. Bidirectional Contact-Account relationships are preserved: each imported Contact receives the resolved AccountId reference from the imported Account record. We extract the full company field schema including any custom fields before writing to Zoho.

Wavity Lead records map directly to Zoho CRM Lead. Source attribution, status values, and any lead scoring properties migrate to corresponding Zoho standard fields or custom fields. Lead assignment rules are documented for the customer's admin to configure in Zoho Workflow Rules post-migration. Any Wavity lead enrichment data is preserved as a custom field on the Zoho Lead.

Wavity's customizable pipeline definitions — names, stage order, and stage probabilities — are extracted as a configuration artifact during discovery. We recreate equivalent pipelines in Zoho CRM by configuring the Deals module's Layouts with matching stage picklist values and stage probability percentages. If Wavity has multiple pipelines, each becomes a separate Zoho Deals Layout.

Each Wavity deal stage name and probability percentage maps to a Zoho Deals stage picklist value with corresponding probability. Closed-Lost and Closed-Won stages from Wavity map to the standard Zoho Won and Lost deal statuses. Stage mapping is validated against the customer's sales process and confirmed during sandbox migration before production import.

Wavity Opportunity records map to Zoho CRM Deals. Deal value, stage name, closing date, owner, and linked Contact and Account references all transfer. The linked Account is resolved from the Account import phase; the linked Contact is resolved from the Contact import phase. Any Wavity custom fields on Opportunities map to custom fields on the Zoho Deals module.

Wavity Task records — title, due date, status, assignee, priority, and linked Contact or Opportunity — migrate to Zoho CRM Task. The Task-Contact and Task-Opportunity (WhatId) linkage is resolved using the Contact and Deals import results. Completion status and timestamps are preserved. Assignee resolution relies on the User mapping from the Owner reconciliation phase.

Wavity calendar appointments with start time, end time, duration, attendees, and linked Contact or Opportunity transfer to Zoho CRM Event records. Timezone information is preserved during import to prevent scheduling misalignment in Zoho. Attendees resolve to Zoho Contacts or Users based on the email match during the User reconciliation phase.

Wavity Help Desk Tickets — status, priority, assignee, linked Contact, and conversation history — map to Zoho CRM Cases. The conversation thread migrates as Zoho Notes or Email Messages attached to the Case. Custom ticket fields require field-level mapping during schema design. Note that Zoho Cases requires Service Cloud or a support module enabled on the target account; we confirm this during scoping.

Wavity User records — name, email, role, and permissions — map to Zoho CRM User. We resolve Wavity Owners by email match against the Zoho destination User table. Any Wavity Owner with no matching Zoho User goes to a reconciliation queue for the customer's admin to provision. We flag inactive Wavity users that should not be provisioned as active Zoho users. Role and permission configurations are documented for manual rebuild in Zoho Roles and Profiles.

Custom objects built with Wavity's Zero Code Application Designer require schema discovery and field-by-field mapping because they have no standard export format and do not map to any standard CRM object model. We run a schema review call with the customer to document every custom object, field type, validation rule, and lookup relationship. We then pre-create the corresponding custom module in Zoho CRM — including all custom fields, field types, and lookup fields — before any data moves. The Zoho Data Migration Wizard's _C filename convention is used to auto-recognize custom modules during import.

File attachments stored in Wavity must be exported manually (Wavity's lack of a public API prevents automated attachment extraction) and re-uploaded to Zoho CRM with record linkage preserved. We document every attachment-to-record association during discovery, provide the customer with a file export checklist, and re-link attachments in Zoho using the same parent record references. This step adds manual coordination time proportional to the total attachment volume.