Migrate from Wice CRM to Mailchimp

Wice CRM contacts map directly to Mailchimp Audience members. The contact's email address serves as the unique identifier and dedupe key during import. Standard contact fields (first name, last name, phone, address) map to Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS). The link between a Wice contact and its parent Organization is preserved by setting the COMPANY merge field in Mailchimp to the organization name, and by creating a Mailchimp tag named after the organization for segmentation purposes.

Wice Organizations have no direct Mailchimp equivalent because Mailchimp has no separate account or company object. We create a Mailchimp tag for each unique Organization name (tag format: org:{name}) and apply it to every contact linked to that organization in Wice. The organization name also populates the COMPANY merge field on each contact. This dual approach lets the admin segment by organization using either the tag filter or the merge field in Mailchimp.

Wice CRM deals with pipeline stages, values, expected close dates, and owner assignments have no Mailchimp equivalent. Mailchimp does not store deal records, opportunity pipelines, or sales stage information. We export the deal data as a separate CSV during discovery and flag it as a manual handoff. The customer decides whether to move deal data into a spreadsheet, a dedicated CRM, or a Mailchimp-integrated CRM such as HubSpot or Salesforce that can sit alongside Mailchimp for marketing.

Wice CRM's category system for contact classification maps to Mailchimp tags. We extract all distinct category values assigned to contacts, normalize them into a tag-naming convention (replacing spaces with underscores, stripping special characters), and apply them during the Mailchimp import. If a contact has multiple Wice categories, all corresponding tags are applied. The mapping table between Wice category names and Mailchimp tag names is delivered as part of the migration documentation.

Wice CRM campaigns (basic and advanced) store campaign metadata and, for advanced campaigns, targeting and tracking properties. Campaign history data such as send dates, subject lines, and recipient counts can be preserved in a reference CSV for the admin to use when rebuilding campaigns in Mailchimp. Engagement history (opens, clicks) does not export cleanly from Wice and is noted as requiring Mailchimp analytics to rebuild from the date of Mailchimp go-live. We do not migrate campaign automation logic; this requires admin rebuild in Mailchimp Journeys.

Wice CRM support tickets linked to contacts have no Mailchimp equivalent. Mailchimp does not have a support ticket or case management object. We export ticket data (subject, status, priority, custom fields) as a separate CSV and flag it for the customer to migrate into a dedicated helpdesk platform (Zendesk, Freshdesk, HubSpot Service Hub) if needed. The contact-to-ticket relationship is preserved in the export for reference.

Wice CRM projects with tasks, assignees, and status fields have no Mailchimp equivalent. Mailchimp does not store project or task records. We export project and task data as a separate CSV and flag it for the customer to handle in a dedicated project management tool. Tasks linked to contacts are exported with the contact reference preserved for manual re-linkage in the destination project tool.

Wice CRM custom fields on contacts and organizations (available at Gold tier) map to Mailchimp merge fields. We extract the custom field definitions during discovery, map field types to appropriate Mailchimp merge field types (text, number, date, address, phone), and create the merge fields in the destination audience before import. Picklist-style custom fields in Wice are mapped to Mailchimp radio or dropdown merge field types with equivalent option values. Fields without a Mailchimp type equivalent are stored as text merge fields.

Wice CRM free-text notes attached to contacts are exported as plain text. Because Mailchimp has no native notes object, we add each contact's notes as a tag with the prefix 'note:' followed by a truncated note excerpt, and deliver the full note content in the migration reference CSV. The admin can review the notes CSV post-migration and decide whether to enter them manually into Mailchimp contact profiles or store them in a separate document system.