Migrate from Tall Emu CRM to Mailchimp

Tall Emu Contact records map to Mailchimp Subscribers within a target Audience. We export Contacts from Tall Emu's grid view using the column chooser to include all standard fields (First Name, Last Name, Email, Phone, Role, Address). Email address serves as the Mailchimp subscriber key for deduplication. Any Contact without a valid email address is held in a reconciliation queue. Standard merge fields (FNAME, LNAME, PHONE, ADDRESS) map directly; additional Tall Emu fields map to custom Mailchimp merge fields pre-created during scoping.

Tall Emu Company records provide the company name, industry, and billing address. We use the company name as a Mailchimp Tag applied to all Contacts linked to that Company record. Industry maps to a custom merge field if the Tall Emu Industry field is populated. The Company billing address is appended to the Contact's address merge fields where available. Companies without linked Contacts are noted as orphaned and require manual review for Mailchimp audience import.

Tall Emu Products carry SKU, pricing tiers, stock on hand, serial number tracking, BOM structures, and reorder points. Mailchimp has no product catalog object. We export the full product inventory as a written product catalog document in CSV and Excel format for the customer's admin to reference in Mailchimp manually or to integrate with a dedicated e-commerce or inventory tool post-migration. BOM and serial number data is outside Mailchimp's scope entirely.

Tall Emu Pipelines and Deals have no Mailchimp equivalent. Mailchimp does not support opportunity records, deal stages, probabilities, or pipeline management. We export the full pipeline structure (pipeline names, stage names, stage order, probabilities) and all open and closed Deal records as a CSV inventory. The customer's admin reviews this inventory and decides whether to document pipeline health externally or move pipeline tracking to a dedicated CRM as a separate project.

Tall Emu Quotes contain line items, pricing, terms, and acceptance status. Mailchimp does not have a quoting object. We export Quote records as a separate CSV inventory (Quote ID, Contact name, total value, status, date) for manual reference. PDF attachments and template styling do not transfer. Quote status values (Draft, Sent, Accepted, Declined) are documented for the customer's admin to recreate as tags or segments in Mailchimp if needed for reporting.

Tall Emu Orders and Invoices carry line items, quantities, pricing, fulfillment status, and payment records linked to Xero or MYOB integration. Mailchimp has no order or invoice object. We export a full order and invoice inventory as CSV for the customer's finance team. Historical paid invoice data is preserved for record-keeping but has no Mailchimp workflow use case. Payment status and terms are documented as a manual reference for reconciliation.

Tall Emu Subscriptions have Plan, Status, Billable Quantity, Price, Period, and Renewal Due Date. These map to Mailchimp Tags applied to the Subscriber record. Active subscriptions become a 'Active Subscriber' tag; expired subscriptions become an 'Expired' tag. Plan name and period map to custom merge fields. Billable quantity and price are informational only since Mailchimp does not have a subscription billing cycle engine. Renewal due dates are noted in a custom merge field for segmentation purposes.

Tall Emu Activity records include meetings, calls, emails, and tasks with assignees, due dates, and completion status. Mailchimp does not support activity logging or task management. We export a summary of activity counts per Contact (total calls, total emails, last meeting date) as a custom merge field in Mailchimp. The full activity log is not migratable. The customer's admin rebuilds any task management workflow in a dedicated project management tool separate from Mailchimp.

Tall Emu custom fields on Contacts (and the subset of modules that support them) map to Mailchimp merge fields where Mailchimp supports the data type. Text, number, date, and email custom fields map cleanly to TEXT, NUMBER, DATE, and EMAIL merge field types. Multi-select or multi-checkbox custom fields map to Mailchimp TEXT merge fields as comma-separated values. Dropdown and radio custom fields map to Mailchimp dropdown merge fields. Any Tall Emu custom field on a module without a Mailchimp equivalent (e.g., custom fields on Products or Orders) is documented separately and not migrated.