Migrate from Wavity CRM to Mailchimp

Wavity Contact records migrate to Mailchimp Audience members as the primary record type. Email address serves as the dedupe key; contacts with duplicate emails merge rather than create duplicates. Standard fields (first name, last name, phone) map to Mailchimp merge fields FNAME, LNAME, and PHONE. Custom contact fields require type evaluation: text fields become Mailchimp text merge fields, date fields become date merge fields, and multi-select or checkbox fields map to Mailchimp groups or radio/dropdown merge fields depending on the customer's segmentation strategy.

Wavity Lead records migrate to Mailchimp Audience members with a 'Lead' tag applied. Lifecycle stage values from Wavity (New, Working, Nurturing, Qualified) become individual Mailchimp tags or a merge field (LEADSTAGE) based on segmentation needs. Any lead scoring value stored as a custom field migrates as a numeric merge field. Unqualified leads that should not receive marketing email are migrated with a suppression flag or excluded from the primary audience pending re-permissioning.

Wavity Account records carry company-level data (industry, size, address) that has no direct Mailchimp equivalent because Mailchimp lacks a separate Account or Company object. We create Mailchimp merge fields (COMPANY, INDUSTRY, COMPANY_SIZE) and tag contacts by Account name or industry segment. The account-contact relationship is preserved by tagging rather than as a foreign-key link, which is the natural denormalization required when migrating from a relational CRM to a flat contact list.

Wavity Opportunity records do not map to any Mailchimp object. Mailchimp has no deal, pipeline, or sales tracking capability. We export Opportunity records as a CSV inventory and flag them as records requiring a rebuild in a separate CRM if the customer continues to need sales pipeline tracking. This is a hard limitation disclosed during scoping.

Wavity Pipeline configurations (stage names, probabilities, custom fields) have no equivalent in Mailchimp. Pipeline schema is exported as a JSON document and delivered as part of the migration handoff package. The customer recreates any Mailchimp Customer Journey automations triggered by pipeline events from this documentation.

Wavity Help Desk Tickets and their conversation threads do not migrate to Mailchimp. Mailchimp has no case, ticket, or support conversation object. We export ticket records as a CSV inventory and conversation history as a structured JSON document. If the customer requires ongoing support ticket management, we recommend a dedicated help desk platform (Zendesk, Freshdesk) as a separate implementation.

Wavity Zero Code Application Designer custom objects require field-by-field evaluation. We create Mailchimp merge fields for each custom field that maps to a contact-level attribute and apply tags for categorical custom object data. Many-to-many relationship objects from Wavity become tag groups in Mailchimp. Objects with no contact-level attribute (standalone transactional records) are exported as CSV and noted as unmigrated.

Wavity User records map to Mailchimp User accounts only at the administrative level. Mailchimp's contact data model does not include owner-assignment (no record-level owner field). We deliver a user inventory CSV documenting each Wavity user's role and contact ownership for the customer's admin to use in Mailchimp permission and team setup.

Wavity Tasks linked to Contacts migrate as CSV inventory only. Mailchimp has no task or activity object for contact-level to-dos. Completed task history (notes embedded in task descriptions) migrates as Mailchimp Note fields or campaign content notes at the customer's discretion. Open tasks are delivered as a CSV for manual re-creation or integration with a project management tool.

File attachments stored in Wavity are exported and delivered as a ZIP archive. Mailchimp does not host attachments or provide a document management layer. We re-upload attachments only when they are directly relevant to email campaign content (e.g., PDF assets for a newsletter). Relationship links between attachments and contact records are severed in Mailchimp and delivered as a linkage map for reference.