Migrate from Wavity CRM to Nutshell

Wavity Contact records map directly to Nutshell People. Standard fields (name, email, phone, address) transfer via CSV or REST API import. Custom fields on the Wavity Contact object require field-by-field type mapping since Wavity's Zero Code Designer stores field metadata differently from Nutshell's custom field model. We validate email format and uniqueness during import to avoid duplicate People records.

Wavity Account/Company records map to Nutshell Company. The Company-to-Person relationship is preserved by resolving the Account link on each Contact before import. Nutshell's Company object supports industry, website, and address fields. Any Wavity custom fields on Company require a pre-import schema mapping call to ensure type compatibility.

Wavity Lead records map to Nutshell Lead (or directly to Person if the lead is already qualified). Source attribution, lead status, and scoring values from Wavity transfer as custom fields on the Nutshell Lead or Person record. We flag any Wavity leads with a 'closed lost' status for exclusion unless the customer requests otherwise.

Wavity Opportunity records map to Nutshell Deal. Deal name, value, stage, probability, owner, and expected close date transfer directly. The Wavity pipeline stage name maps to the Nutshell pipeline stage via the stage mapping table built during scoping. Closed-Lost and Closed-Won status from Wavity map to Nutshell's Won/Lost deal state.

Wavity's customizable pipeline stages are extracted from the pipeline schema during scoping. We recreate the equivalent Nutshell pipeline with matching stage names, stage order, and probability percentages. If Wavity uses multiple pipelines, we configure multiple Nutshell pipelines and map each Opportunity to its corresponding pipeline during import.

Wavity Task records transfer to Nutshell Task with due date, assignee, status, and linked object preserved. Task assignment resolves by matching the Wavity owner email to the Nutshell user. Linked Contact and Opportunity references are preserved using Nutshell's task linking model. Completed vs open task status transfers directly.

Wavity calendar appointments with time, duration, attendees, and linked records migrate to Nutshell Meeting records. We preserve timezone information from the Wavity appointment to ensure scheduling accuracy. Attendee linking uses email-based resolution to match Nutshell People records.

Wavity Help Desk tickets migrate to Nutshell Cases if the destination account includes Nutshell's Service bundle. Ticket status, priority, assignee, and conversation history transfer. Custom ticket fields require manual mapping during the schema discovery phase. We preserve the full conversation thread as case comments and flag any ticket attachments for re-upload. Teams without the Service bundle receive a written mapping of the Wavity ticket schema for manual setup.

Custom objects built in Wavity's Zero Code Application Designer have no standard export format and no API access. We schedule a schema discovery session with the customer to document every custom object, its fields, field types, validation rules, and any lookup relationships to standard Wavity objects. Each custom object is then mapped to Nutshell custom fields on the closest standard object (Person, Company, or Deal) or to a standalone custom record type if the customer's data model requires it. This is the highest-risk part of the migration and requires customer involvement.

Wavity user records map to Nutshell users by email address. Active Wavity users receive Nutshell user provisioning instructions; inactive Wavity users are flagged and excluded from the import unless the customer requests they be provisioned. Role and permission structures do not transfer since permission models differ significantly between Wavity and Nutshell; the customer's admin configures Nutshell roles post-migration.