Migrate from ZeyOS to Mailchimp

ZeyOS Contacts map directly to Mailchimp Members. We extract the contact's name, email address, phone, and all extdata custom fields from the REST API response, then map them to Mailchimp merge fields (FNAME, LNAME, PHONE plus any custom merge field tags we pre-create). The Contact's parent Account FK resolves to a Mailchimp Audience assignment. If the ZeyOS contact has an opt-out or unsubscribe status in its custom fields, we set the Member status accordingly (subscribed, unsubscribed, cleaned). We handle Mailchimp's 255-character merge field limit by flagging any ZeyOS extdata value exceeding that length for truncation or split-field strategy during scoping.

ZeyOS Accounts map to Mailchimp Audiences, but the mapping direction is inverted compared to a CRM-to-CRM migration. Mailchimp Audiences are flat lists of Members; there is no nested Account-Contact hierarchy. We typically consolidate multiple ZeyOS Accounts into a single Mailchimp Audience unless the customer has a business reason for separate Audiences (for example, separate brands or legal entities requiring isolated email compliance). We pre-create Audience names and tags during scoping, then assign Members to the correct Audience based on their parent Account at migration time.

ZeyOS Leads are a distinct CRM object separate from Contacts. Since Mailchimp has no separate Lead concept, we merge Lead records into Members within the target Audience and preserve lead-specific status fields (lead status, lead score, source) as Mailchimp Tags (for example, tag Lead, tag Source:Web, tag Score:75). The customer's admin decides during scoping whether Leads merge into the same Audience as Contacts or map to a separate Audience.

ZeyOS stores custom Contact and Lead properties in the extdata JSON column and in the fields table. We read the field definitions during discovery, create matching Mailchimp merge fields (text, number, date, or dropdown per the field type), and map values during import. Mailchimp enforces a 255-character limit on text merge fields. We flag any ZeyOS custom text fields exceeding 255 characters and propose a truncation strategy, a split-field approach, or a transition to Mailchimp's Notes field for longer content.

ZeyOS Users (team members who own records) have no direct Mailchimp equivalent. Mailchimp Members do not track an owner or assigned sales rep. If the customer wants to preserve owner assignment for internal workflow purposes, we create Tags based on the ZeyOS User name and apply them to Members they originally owned in ZeyOS. This is optional and configured during scoping.

If ZeyOS stores Tags on Contacts (via a tag property or multi-select field), we map those directly to Mailchimp Tags. Tags migrate as string labels on the Member record. Mailchimp Tags can be applied in bulk during import via the Members POST endpoint or the bulk import endpoint.

ZeyOS Activities (engagements linked to Contacts or Accounts) cannot migrate to Mailchimp as native objects because Mailchimp's Member record has no activity timeline equivalent. We extract the most recent engagement date per Contact and store it as a merge field (LASTENGAGED) or as a Tag with a date label, preserving the recency signal without importing the full history. Full engagement history requires a CRM platform as the destination.

ZeyOS stores file attachments as binary blobs in the binfile column. Mailchimp does not host arbitrary file attachments for CRM records. We extract the binary blob from ZeyOS, upload it to a customer-provided storage location (S3, Google Drive, or SharePoint), and store the resulting URL as a custom merge field (DOCUMENT_URL) on the corresponding Member. Files exceeding 25MB are flagged for customer review before upload.