Migrate from ContactWise CRM to Mailchimp

ContactWise Contacts map to Mailchimp Members within one or more Audiences. Email address serves as the dedupe key; duplicate email addresses are flagged for resolution before import. Standard fields (first name, last name, phone, address) map to Mailchimp merge fields FNAME, LNAME, PHONE, and ADDRESS respectively. Any ContactWise custom properties are mapped to Audience-specific merge fields that we create before import. Contact status (active/inactive) does not have a native Mailchimp equivalent; we preserve it in a custom merge field contact_status__c and recommend using Mailchimp's unsubscribed or cleaned status as the equivalent for inactive records.

ContactWise Account records map to Mailchimp as merge field values on the related Audience Member rather than as a separate object. We extract the Account name and map it to a COMPANY merge field, and Account type (customer, prospect, partner) maps to a tag on each Member. If the customer maintains multiple ContactWise Accounts for the same email contact, we flag these for manual resolution as Mailchimp does not support multi-parent record relationships.

ContactWise Leads are distinct from Contacts and carry a lead status and source attribution. We import them as Mailchimp Members tagged with a Lead tag and include status as a merge field value. The decision to import Leads into the same Audience as Contacts or a separate prospect Audience is made during scoping; a separate Audience requires a distinct import job with its own merge field configuration. Lead score or rating does not map to a native Mailchimp field and is preserved in a custom merge field lead_score__c.

ContactWise Opportunities store deal records with stage, amount, expected close date, and owner assignment. Mailchimp has no opportunity or deal-tracking object. We do not migrate Opportunities as records. We export the opportunity data to a CSV file and deliver it as a supplementary export for the customer to manage in a separate tool, a spreadsheet, or a supplemental CRM if they choose to maintain one alongside Mailchimp. This is documented in the scope as an out-of-scope object.

ContactWise service desk tickets track support interactions with state, priority, and contact associations. Mailchimp does not support a ticket or case object. We do not migrate Tickets as records. We export ticket metadata (ticket ID, contact email, creation date, status, resolution notes) to a CSV delivered alongside the primary contact migration. The customer uses this as a reference for re-entering open tickets in their chosen support tool.

ContactWise Documents and attachments associated with Contacts, Accounts, or Tickets do not migrate directly to Mailchimp because Mailchimp does not have a document management layer. We export files to cloud storage (S3 or equivalent) and deliver a manifest mapping each file to the related contact email for reference. The customer manually attaches files in Mailchimp if needed, or uses a separate document management system.

ContactWise Workflow definitions store automation logic as platform configuration rather than data records. They cannot be exported and replayed in Mailchimp because Mailchimp Automations use a different trigger model (email-based triggers, date-based triggers, and API-triggered campaigns versus ContactWise's field-change and time-based triggers). We document every active ContactWise Workflow during discovery, listing the trigger, conditions, and actions, and we deliver a rebuild guide mapping each to an equivalent Mailchimp Automation or Customer Journey. The customer's admin rebuilds them in Mailchimp post-migration.

ContactWise Time Entries track billing or project work linked to Contacts, Tickets, or Projects. Mailchimp has no time-tracking or billing object. We do not migrate Time Entries. We export them to a CSV with contact reference, date, duration, and billing amount for the customer's accounting or project management tool. This is documented in the scope as out-of-scope data.