Migrate from Clarify CRM to Mailchimp

Clarify Contact records map 1:1 to Mailchimp audience members. The primary key is email address. We validate email format before import and flag any malformed addresses in a reconciliation report. Name fields (first_name, last_name), phone, and address fields map to Mailchimp merge fields. The contact's associated company name from Clarify maps to the COMPANY merge field in Mailchimp. Any tags on the Clarify contact attach as Mailchimp tags on the subscriber record. Status (active/inactive in Clarify) maps to Mailchimp subscription status; unsubscribed contacts in Clarify are imported as unsubscribed in Mailchimp to preserve deliverability compliance.

Clarify Company records do not have a direct Mailchimp equivalent because Mailchimp has no Companies or Accounts object. Company data (domain, industry, employee count, location) merges into the subscriber record via Mailchimp merge fields. The primary contact's COMPANY merge field receives the company name. Industry and employee count become custom merge fields (text or number type) on the Mailchimp audience. If a Clarify contact has multiple associated companies, we attach a tag prefix (e.g., 'company:AcmeCorp') to the subscriber record and deliver a company reconciliation table for the customer to configure in Mailchimp segments post-migration.

Clarify Deal records have no equivalent object in Mailchimp. Mailchimp does not store opportunity value, stage, probability, or close date as structured records. We flag all active deals during scoping and ask the customer to decide: export them as a CSV report (delivered in the handoff package) for manual entry, or convert deal value and stage into subscriber tags (e.g., 'deal:hot', 'deal_value:5000') attached to the associated contact record. We do not create deal equivalents in Mailchimp because they do not exist in the platform's object model.

Clarify Pipeline Stages (e.g., Prospecting, Qualification, Demo Scheduled, Proposal Sent, Closed Won, Closed Lost) have no Mailchimp equivalent. We capture the full stage sequence during discovery and either deliver it as a CSV appendix or convert stage names into Mailchimp tags (e.g., 'pipeline:proposal_sent'). The customer uses these tags to build Mailchimp segments if needed, but Mailchimp does not support pipeline visualization or stage-based workflow routing for contacts.

Clarify activity records (calls, emails, meetings, tasks) cannot migrate to Mailchimp because Mailchimp has no activity timeline, Task, Event, or EmailMessage object. Call disposition, duration, meeting attendees, and task completion status have no landing spot in Mailchimp's audience-member model. We extract a structured activity log as a CSV export delivered in the handoff package. AI-generated meeting summaries from Clarify (stored as linked note content on activity records) can attach to the corresponding subscriber record as a member note, though Mailchimp displays notes as plain text without rich formatting and customers should review for completeness.

Clarify custom fields on Contact and Company objects map to Mailchimp merge fields on the destination audience. We map field types as follows: text fields to text merge fields, number fields to number merge fields, date fields to date merge fields, and dropdown fields to dropdown merge fields. Multi-select fields from Clarify map to text merge fields with comma-separated values. Currency and percentage fields require field type validation because Mailchimp supports a limited merge field type set. We pre-create merge fields in the Mailchimp audience before subscriber import and flag any Clarify field types with no Mailchimp equivalent.

Clarify Tags attached to Contacts and Companies map directly to Mailchimp Tags on the corresponding subscriber records. Tags from both Contact-level and Company-level tagging in Clarify accumulate on the subscriber. We preserve the full tag string including any taxonomy prefix (e.g., 'segment:enterprise', 'source:linkedin'). Tag deduplication happens post-import: if the same tag appears on multiple contacts, Mailchimp's tag index handles it natively. We deliver a tag inventory report listing all unique Clarify tags and their subscriber counts.

Clarify stores AI-generated meeting summaries as enriched note content attached to activity records. Because activities cannot migrate, the summaries themselves are extracted as structured text linked to the primary contact. In Mailchimp, we attach the summary as a member note on the corresponding subscriber with a 'Migrated from Clarify CRM' header and a timestamp of the original meeting date. Mailchimp displays notes as plain text without rich formatting; the customer should review migrated notes for completeness and reformat if needed. We flag any summaries exceeding Mailchimp's note character limit for manual truncation.