Migrate from Firmao CRM to Mailchimp

Firmao Contact records map directly to Mailchimp Members within a single audience. Standard fields (firstName, lastName, email, phone, address) map to Mailchimp address and merge field equivalents. We use the Mailchimp Members API with upsert semantics (POST with status_if_new) to handle re-imports without duplicating existing members. Email addresses serve as the dedupe key. Status in Mailchimp (subscribed, unsubscribed, pending) is derived from any consent or opt-in field in Firmao; if no consent field exists, members are imported as pending to comply with GDPR double opt-in by default.

Firmao Company records denormalize into the Contact-level merge fields in Mailchimp. The Contact's company association (companyId) is resolved by matching companyName against the exported Company list, and the companyName value is stored in a COMPANY merge field on the Member. Additional Company fields (address, phone, website) migrate to separate merge fields on the Member if populated. This is a flat structure: Mailchimp does not support a parent Company object with child Members the way Firmao does. We flag any Contact without a resolved Company for manual review.

Firmao Tags on Contacts (stored as comma-separated strings on the contact record) are extracted and created as individual Mailchimp Tags on the corresponding Member. Mailchimp Tags are additive labels (not a controlled vocabulary), so there is no schema conflict. We preserve all tags present in the sample export. If the same tag appears across multiple Contacts, it appears as a filterable tag in Mailchimp's audience view. Tag-based segments in Mailchimp are created for any tag that represents a behavioral or demographic group (e.g., industry, lead source, region) during the post-migration segment rebuild.

Firmao customFields.customN dot-notation values migrate to Mailchimp Merge Fields named after the semantic label (provided by the customer during scoping or extracted from the import documentation). All merge field values are string type. Mailchimp Standard plan supports an unlimited number of merge fields; the Free and Essentials plans have a cap. We confirm the customer's Mailchimp plan tier during scoping and flag if the merge field count exceeds plan limits. Date, numeric, and boolean custom fields are stored as strings in Mailchimp merge fields with an explanatory note in the migration manifest.

Firmao Deals have no Mailchimp equivalent. Mailchimp tracks subscriber engagement with campaigns, not deal progression through a sales pipeline. We export the Deal records (pipeline, stage, value, owner, close date) as a CSV inventory for the customer's admin to review. If the customer needs to preserve deal context, we recommend exporting Deals to a separate CRM (HubSpot, Pipedrive) as a parallel migration. Deal migration is out of scope for this pair.

Firmao Tasks (assignee, due date, status, contact association) do not migrate to Mailchimp. Mailchimp does not have an internal task management object. We export Tasks as a CSV with contact association, assignee, and due date for manual rebuild in the customer's chosen task management tool (Asana, Trello, Notion). Task relationships to Contacts are preserved in the export as email addresses so the association can be re-linked in the new tool.

Firmao Invoices (line items, tax codes, payment status, VAT data) have no Mailchimp equivalent. Mailchimp is an email marketing platform and does not handle billing, accounting, or financial records. Invoices remain in Firmao or are exported separately by the customer if required for record retention. We note this boundary clearly in the migration scope to avoid scope creep.

Firmao's email conversations and activity logs are not exposed as discrete API objects. The platform surfaces email history through the CRM UI but there is no documented /activity or /email endpoint. Mailchimp also does not import historical engagement data from external CRMs. Email open and click history begins accruing after cutover from Mailchimp sends. We document this limitation explicitly in the migration inventory and advise the customer that post-migration email engagement will start fresh in Mailchimp.