Migrate from Twenty CRM to Mailchimp

Twenty People records map directly to Mailchimp Contacts. Email is the unique identifier on both systems. We use email as the dedupe key during import and run a verification pass against each address to catch hard bounces before they enter Mailchimp and trigger billing penalties. Name, phone, job title, and address fields map to Mailchimp's standard merge fields (FNAME, LNAME, PHONE, ADDRESS). A valid phone number is required for SMS-capable Mailchimp tiers if the customer plans to use SMS campaigns.

Twenty Companies have no direct Mailchimp equivalent because Mailchimp organizes contacts in flat Audiences without a parent Account object. We denormalize company data into contact-level attributes: domain becomes a text merge field COMPANY_DOMAIN; industry maps to a dropdown merge field COMPANY_INDUSTRY; employee count maps to a number merge field COMPANY_SIZE; city or region maps to a text merge field. We also apply a tag per company (e.g., tag: Acme Corp) so that the customer can filter the audience by original company without requiring a separate CRM. The tag taxonomy is designed during scoping to avoid exceeding Mailchimp's tag limit recommendations.

The Twenty People-to-Company relationship (companyId foreign key) maps to a Mailchimp tag on the contact. Each unique Company name becomes a tag applied to all People records that reference it. This preserves the company grouping that would otherwise be lost in a flat contact list. If a Person has no companyId, no tag is applied. We coordinate with the customer on tag naming conventions during scoping because tags appear in Mailchimp campaign filtering.

Twenty Opportunities (deals with stage, amount, close date, linked Company, and linked Person) have no Mailchimp equivalent. Mailchimp does not have a pipeline, deal stage, or opportunity amount field. We flag Opportunities during discovery, deliver a written record of all open and closed opportunities with their values and stages, and document that the customer needs a separate CRM or spreadsheet to maintain pipeline data. We do not create placeholder contacts or tags for opportunities because that would distort the audience data.

Twenty Tasks (title, due date, assignee, completion status, linked to any record type) have no Mailchimp equivalent. Mailchimp does not have a task management or to-do feature. Completed and incomplete tasks are documented in the migration handoff report. The customer needs a separate task management tool (Notion, Asana, or a CRM) for post-migration follow-up tracking.

Twenty Notes (free-form text linked to any record) migrate to Mailchimp contact notes. We map Note.body to the Mailchimp contact note field, set the note timestamp to the original Twenty createdAt date, and link it to the contact by email. Notes on Company records are applied as notes to all People contacts that belong to that company so the context is preserved at the contact level. Notes on Opportunity and Task records are not migrated because those objects do not exist in Mailchimp.

Twenty Custom Objects (user-defined entities like Subscriptions, Events, Rockets) have no native Mailchimp equivalent. We assess each Custom Object during scoping: if it has an email field, we denormalize its key fields into merge fields on the matching contact (e.g., Subscription_Status, Event_Attended). Custom Objects without an email field cannot migrate because Mailchimp contacts are the only recipient type. We deliver a written schema map of all Custom Objects with their field types and note which are eligible for merge field denormalization versus which require a separate system.

Twenty Owners (assigned to People, Companies, Opportunities, Tasks) can be preserved as Mailchimp contact tags (e.g., Owner: [email protected]) or as a text merge field OWNER_EMAIL if the customer wants to track which team member owns the contact in Twenty. We use owner email as the tag value for consistency. This is optional because Mailchimp does not have a native owner or user assignment concept. The customer decides during scoping whether owner attribution is required.