Migrate from Clientify to Mailchimp

Clientify Contacts map to Mailchimp Audience Members using email address as the primary dedupe key. Standard fields (first name, last name, email, phone) map directly to Mailchimp's NAME, LNAME, and EMAIL merge fields. Lifecycle stage from Clientify maps to a text merge field hs_lifecycle_stage__c for audit. If a Clientify contact has no email address, it is flagged in the export and held in a reconciliation queue.

Clientify custom fields on contacts translate to Mailchimp merge fields. We map text fields to Mailchimp text type, date fields to date type, and picklist fields to dropdown type. Mailchimp imposes a 30-character limit on merge field names; longer Clientify field names are truncated and flagged in the mapping document. Dropdown merge fields require pre-creation in Mailchimp before import or the insert fails for those records.

Clientify contact tags migrate directly to Mailchimp Tags as string arrays. Tags are preserved as-is because both platforms use a simple string-tag model. Tags used for segmentation in Clientify map to Mailchimp Segments, which are rebuilt post-migration based on the imported tag set.

Mailchimp has no Company or Account object. If the customer needs to preserve company data, we split each Clientify Company record into one contact record per associated contact, copying the company name, industry, and address into contact-level merge fields. If the customer does not need company-level data preserved, we skip the Company object and only migrate contacts with their direct custom properties. The split strategy is decided during scoping.

Clientify Deals have no equivalent in Mailchimp. We export Deals as a CSV file (deal name, value, stage, owner, expected close date) for the customer's admin to import into a separate CRM, spreadsheet, or database. We do not migrate deal data into Mailchimp because Mailchimp has no deal pipeline, stage, or value tracking. The CSV export is delivered alongside the contact migration.

Clientify pipeline configurations and stage labels are exported as a reference CSV. Mailchimp does not have a pipeline or stage concept. The export document is provided for the customer's admin to reference when rebuilding any deal-tracking process in a separate system.

WhatsApp message history attached to Clientify contact records has no equivalent in Mailchimp. We extract available metadata (last message timestamp, message count) as contact-level merge fields if exportable, but the full conversation thread, media attachments, and delivery metadata do not migrate. This gap is documented in the migration handoff.

Clientify engagement records for calls, meetings, tasks, and notes have no equivalent in Mailchimp. Email engagements tracked in Clientify's email campaigns (opens, clicks, sends) map to Mailchimp campaign history once contacts are imported and campaigns are sent from Mailchimp. All other activity types are excluded. This limitation is disclosed upfront during scoping.

Clientify Workflows stored in the proprietary automation builder have no portable export format and do not migrate to Mailchimp. Mailchimp Customer Journeys use a different trigger-action model. We provide a structured workflow audit worksheet during scoping for the customer to document every active rule, and the rebuild in Mailchimp Automations is handled by the customer's admin post-migration.