Migrate from Cloze to Mailchimp

Cloze People records map directly to Mailchimp Members within a target Audience. Standard properties — first_name, last_name, email_address, phone_number, headline, and social links — map to Mailchimp merge fields (FNAME, LNAME, EMAIL, PHONE, COMPANY, SOCIALS). Cloze Stages (Lead, Potential, Active, Inactive, Past, Lost) and Segments migrate as tags on each member so that the original stage context is preserved for future segmentation in Mailchimp. Custom fields on People map to additional merge fields in Mailchimp. The member status (subscribed, unsubscribed, pending) is determined by the Cloze contact's current email marketing consent flag.

Mailchimp has no native company or account object. Company records from Cloze must be stored on the member record. We map the company name to the COMPANY merge field and store additional company fields (industry, address, social URLs) as structured notes attached to the member. For teams with multiple People linked to the same Company, each member carries the company name independently. If the customer uses Mailchimp's Enterprise tier, we can use the Company Name field (when available) and document the limitation that cross-contact company reporting is not native to Mailchimp.

Cloze's Projects/Deals/Properties object has no equivalent in Mailchimp. Mailchimp is an email marketing platform with no pipeline, opportunity, or deal-tracking capabilities. We do not migrate Projects or Deals. We flag every unique deal name, stage, value, and close date in a written inventory so the customer can decide whether to track these in a separate spreadsheet, a different CRM, or a Mailchimp-compatible integration (e.g., HubSpot CRM for pipeline alongside Mailchimp for email).

Cloze Segments and Audiences group contacts by Stage or custom criteria. We reconstruct each segment membership as individual Mailchimp tags on the relevant member records. For example, a Cloze segment 'Active Clients — Real Estate' becomes two tags: 'Stage: Active' and 'Segment: Real Estate'. Mailchimp's tag-based segmentation supports equivalent filtering. If the customer used multiple Cloze Audiences, we consolidate into Mailchimp's recommended single audience with tag-based sub-segments, since Mailchimp bills across all audiences cumulatively and managing separate audiences can inflate costs.

Cloze Tags are flat labels applied to People and Companies. We map each tag directly to a Mailchimp tag on the corresponding member. Cloze tags used for contact classification (e.g., 'vip', 'referral', 'newsletter-optin') become Mailchimp tags with the same labels. No transformation is required; the tag vocabulary transfers directly. We deduplicate any tags that differ only by casing or punctuation.

Cloze custom fields on People (text, number, date, choice/picklist) map to Mailchimp merge fields. We create the merge field in Mailchimp (via Audience > Settings > Audience fields and *|MERGE|* tags) before import and map each contact's custom field value. Choice/picklist fields from Cloze map to Mailchimp text merge fields — the dropdown constraint is not enforced in Mailchimp but we document the original picklist values for the customer's reference. Deprecated or deleted Cloze custom fields are flagged and skipped.

Cloze Timeline records capture individual call logs, email threads, meeting records, and notes tied to People or Companies. Mailchimp tracks campaign-level email engagement (opens, clicks, bounces) but not individual email threads or call logs. We do not migrate Timeline entries. The customer's admin should understand that Cloze's full communication history — the feature Cloze users cite most as valuable — will not appear in Mailchimp. If call logging or meeting notes are business-critical, the customer should consider keeping Cloze as a supplemental tool or migrating to a CRM that supports these alongside Mailchimp.

Cloze Teams control contact access and assignment. Mailchimp's user roles (Admin, Manager, Author, Viewer) govern platform access and audience permissions but do not map to Cloze's team-based contact assignment. We preserve the team structure as a written mapping document and recommend that the customer assign Mailchimp roles based on the marketing workflow rather than the Cloze team structure, since Mailchimp permissions are platform-level rather than contact-level.