Migrate from Kizen to Mailchimp

Kizen Contacts map directly to Mailchimp audience members. We map standard fields: email (EMAIL), first name (FNAME), last name (LNAME), phone (PHONE), address fields (ADDRESS fields), and lifecycle stage as a tag or custom merge field. Any Kizen Contact property that has no direct Mailchimp merge field equivalent is preserved as an additional merge field. We set the audience member status based on the contact's Kizen lifecycle stage: customers become subscribers, leads become pending if double opt-in is required, and unsubscribed contacts are imported to the suppression list to protect deliverability.

Kizen Companies have no direct Mailchimp equivalent. We denormalize company data into merge fields on the contact record: company name becomes a COMPANY merge field, industry becomes an INDUSTRY merge field or tag, size (employee count) becomes an EMPLOYEES merge field, and annual revenue becomes a REVENUE merge field if the customer wants to preserve that data. If the Kizen account has multiple contacts per company, the company data is repeated on each contact record rather than stored as a separate entity.

Kizen Deals have no Mailchimp equivalent. Mailchimp does not support opportunity tracking, deal amounts, close dates, or pipeline stages. We export the Deals as a CSV inventory with field mapping so the customer's team can decide whether to store deal context in a spreadsheet, a separate CRM, or a custom Mailchimp merge field (with the caveat that Mailchimp cannot perform pipeline logic). This is a data preservation step, not a live system migration.

Kizen Pipelines and their stage definitions do not map to Mailchimp. Mailchimp has no concept of ordered deal stages or multiple parallel pipelines. We document the pipeline names, stage names, stage order, and stage probabilities in a written pipeline inventory so the customer's team can plan reconstruction in a separate CRM or spreadsheet tool if deal tracking is required alongside Mailchimp.

Kizen custom Objects are user-defined schemas with custom fields and relationship types (Primary and Additional) that have no Mailchimp equivalent. Mailchimp does not support custom record types or custom database objects. We perform schema discovery on the Kizen instance during scoping, inventory every custom Object and its fields, and deliver a written custom object catalog. For each custom Object, we note whether any data can be preserved as merge fields or tags on the contact record, and flag any custom Object data that requires a separate destination (another CRM, a database, or a spreadsheet export).

Kizen Activity records (calls, emails, meetings, tasks) do not map to Mailchimp. Mailchimp tracks engagement through campaign-level opens, clicks, and unsubscribes rather than as structured activity records attached to individual contacts. We do not migrate Activity history. Post-migration, engagement data is collected by Mailchimp from the point of cutover onward. We document the volume of Activity records in scope so the customer's team understands what historical context is not transferred.

Kizen Forms that capture contact submissions map to Mailchimp signup forms. We export the form field names and types from Kizen, then create corresponding Mailchimp embedded forms or popup forms with matching field labels and types. Form submissions already in Kizen as contact records migrate as standard contact data. Conditional logic on Kizen forms does not transfer to Mailchimp forms; we document the conditional rules as a plain-text handoff for the customer's marketing team to rebuild in Mailchimp's form builder.

Kizen tags applied to Contacts map directly to Mailchimp tags. We export the tag list, then apply tags to the corresponding audience members during contact import. Tags are the closest structural equivalent between the two platforms and are preserved without transformation. Tags without a clear semantic equivalent in Mailchimp are preserved as-is and reviewed with the customer during scoping.