Migrate from Wavity CRM to Freshsales

Wavity Contact records map directly to Freshsales Contact. Standard fields (name, email, phone, address) migrate 1:1. Custom fields on Contact require type-mapping to Freshsales' supported field types (text, number, date, picklist, multi-select). We extract the full Contact schema during discovery and match each Wavity field to its Freshsales equivalent before import. The contact-to-organization linkage (bidirectional) is preserved by resolving the Wavity Account reference to Freshsales' Link to Organization field.

Wavity Company records map to Freshsales Organization. Company name becomes Organization Name, domain becomes Website, and industry, employee count, and annual revenue migrate to corresponding Organization fields. We create all Organizations first during migration so that Contact imports have a valid parent Organization reference at insert time. Deduplication uses Organization Name as the primary key with domain-name fallback.

Wavity Lead records (with source attribution, status, and scoring values) map to Freshsales Lead. Lead status values from Wavity map to Freshsales Lead Status using a status translation table defined during scoping. Any Wavity lead scoring values migrate to Freshsales' custom lead score field. Unqualified leads that the customer wants to stage before conversion are held as Freshsales Leads rather than converted immediately.

Wavity Opportunity records (deal value, stage, probability, owner) map to Freshsales Deal. Deal Amount, Stage, Probability, and Expected Close Date migrate directly. Owner assignment resolves via email match against Freshsales User records. Any Wavity custom properties on Opportunity (discount percentage, product line, territory) map to Freshsales custom Deal fields that we pre-create in the destination account before migration.

Wavity's customizable pipeline stages map to Freshsales Deal Pipes. We extract the full stage schema from Wavity (stage names, order, probability percentages) and recreate an equivalent Deal Pipe structure in Freshsales. Each Wavity stage becomes a Freshsales stage within the corresponding Deal Pipe. Probability percentages migrate to Freshsales stage probability values, rounded to the nearest supported integer.

Wavity Task records (due dates, assignees, status, linked objects) migrate to Freshsales Task. Task status (open, completed), priority, due date, and description migrate 1:1. Task assignment resolves by matching the Wavity owner email to a Freshsales User. Linked Contact and Opportunity references migrate as Freshsales Lookup fields by resolving the Wavity record ID to the migrated Freshsales record ID.

Wavity calendar appointments (time, duration, attendees, linked records) map to Freshsales Meeting. Start time, end time, location, and title migrate directly. We handle timezone preservation by storing the original Wavity timezone in a custom field and converting to UTC for Freshsales. Attendee emails resolve to Freshsales Contact or Lead records via the User mapping. Meeting linkage to the parent Contact or Deal migrates via ID resolution after the parent record is created in Freshsales.

Wavity Help Desk tickets (status, priority, assignee, customer link, conversation history) map to Freshsales Case if the customer activates Freshsales' built-in case management or bundles Freshdesk. Ticket pipeline becomes Case Record Type; ticket stages become Case Status values. Conversation threads migrate as Case Emails or Case Thread entries linked to the Case. Custom ticket fields require field-by-field mapping to Freshsales' case field model. We coordinate with the customer's Freshdesk license if the case management scope extends beyond Freshsales' native capabilities.

Custom objects built with Wavity's Zero Code Application Designer require manual schema discovery and field-by-field mapping because there is no standardized export format. We schedule a schema review call with the customer to document every custom object, field type, validation rule, and lookup relationship in Wavity before writing to Freshsales. We then pre-create the equivalent Freshsales Custom Module with matching field types and lookup fields, and import the data using Freshsales' REST API with batch chunking. This is the highest-effort object in the migration and often drives the project into the longer timeline range.