Migrate from Wavity CRM to Salesforce Sales Cloud

Wavity Contact records map to Salesforce Contact with name, email, phone, and custom field values preserved. We use Wavity's contact export CSV, normalize field names and types to Salesforce's typed fields (FirstName, LastName, Email, Phone), and import into Contact with the AccountId lookup resolved against the Account records loaded in the prior phase. Custom field values from Wavity migrate to custom Contact fields (__c suffix) that we create during schema setup.

Wavity Company records map directly to Salesforce Account. Company name becomes Account Name; domain or website fields map to the Account Website field. We use Company as the parent record for Contact, resolving the Account-Contact relationship before Contact import so that no Contact record is orphaned. Bidirectional Contact-Account relationships are preserved by setting the primary account lookup on Contact.

Wavity Lead records map to Salesforce Lead. We preserve lead source attribution, status values, and any scoring data from Wavity's enrichment capabilities in custom Salesforce Lead fields. Owner assignment migrates by email lookup to the Salesforce User table after the User reconciliation phase completes. Leads that arrived via Wavity's chatbot or form integrations are flagged in a custom field for the admin to evaluate for marketing attribution requirements.

Wavity Opportunity records map to Salesforce Opportunity with deal value, stage, probability, and owner assignment. Pipeline stages vary by Wavity configuration, so we extract the full stage name and probability matrix from Wavity during schema discovery and recreate it as a Salesforce Sales Process mapped to the appropriate Record Type before Opportunity import begins.

Each Wavity pipeline configuration becomes a Salesforce Record Type on Opportunity with a corresponding Sales Process that whitelists the stage values. Stage names, order, and probability percentages migrate from Wavity's pipeline configuration. If Wavity uses probability overrides on individual Deals, those values are preserved in a custom Opportunity field and the standard probability is recalculated from the stage default post-migration.

Wavity Task records map to Salesforce Task with Subject, Status, Priority, ActivityDate, and Description preserved. Task assignments migrate by resolving the Wavity owner reference to the Salesforce OwnerId via the User mapping table. Linked objects (Contact, Opportunity) migrate as WhatId and WhoId references after the parent record IDs are confirmed in Salesforce.

Wavity Appointment records map to Salesforce Event with StartDateTime, EndDateTime, Subject, and Location preserved. Attendee relationships map to EventRelation records pointing at the resolved Leads, Contacts, and Users. Timezone handling is explicit: we store the original Wavity timezone in a custom field and convert to the customer's Salesforce org timezone during import to avoid scheduling misalignment.

Wavity Tickets map to Salesforce Case if the destination org includes Service Cloud licensing. Ticket status, priority, assignee, and customer link migrate to the corresponding Case fields. Conversation history migrates as EmailMessage records linked to the Case. Custom ticket fields require field-by-field mapping during the schema discovery phase; we document every custom ticket field, its type, and validation rules before the destination schema is built.

Wavity custom objects built with the Zero Code Application Designer require pre-migration schema discovery because there is no standard export format. We schedule a schema review call with the customer to document every custom object, field name, field type, picklist values, validation rules, and lookup relationships before writing a single record. The destination custom object schema is then built in Salesforce with matching __c API names, and data is migrated with all lookup references resolved to the parent records loaded in prior phases.

Wavity User records map to Salesforce User by email match. Inactive Wavity users are flagged and excluded from the Salesforce provisioning queue. The customer's Salesforce admin provisions any missing Users in the destination org before the migration resumes. OwnerId references on all standard objects (Contact, Account, Opportunity, Task, Event, Case) depend on this phase completing first.

File attachments stored in Wavity are exported from the platform's document storage and re-uploaded to Salesforce as ContentVersion records linked to ContentDocument via ContentDocumentLink. The attachment-to-record linkage (Contact, Opportunity, Account) is preserved by resolving the original Wavity record ID to the new Salesforce record ID during the link creation phase.

Wavity notes migrate to Salesforce Note records linked via ContentDocumentLink to the parent record (Lead, Contact, Account, or Opportunity). Rich text formatting is preserved where supported. Image attachments within notes migrate as separate ContentDocument records and are linked back to the parent Note record.

Wavity's pre-built sales dashboards and custom analytics are not exportable in structured form. We do not migrate Reports or Dashboards. We migrate the underlying data (Contacts, Accounts, Opportunities, Activities) so that equivalent reports can be rebuilt in Salesforce Reports and Lightning Dashboards post-migration. We deliver a written inventory of every Wavity report and dashboard with its data sources and filters for the customer's admin to reference during rebuild.