Migrate from Composity CRM to Mailchimp

Composity Contacts map directly to Mailchimp Contacts (subscribers) within an Audience. We map first name, last name, email address, phone, and address fields to Mailchimp's standard merge fields (FNAME, LNAME, EMAIL, PHONE, ADDRESS). Any custom contact properties defined in Composity's Custom Data module become Mailchimp merge fields on the contact record. Composity's Account-Contact relationship is preserved as a tag or as Mailchimp's Company field if the destination Mailchimp account has the Organizations feature enabled.

Composity Accounts map to the Mailchimp Audience level with organization data stored as audience-level fields or as tags applied to all contacts belonging to that account. Because Mailchimp does not have a native Account object, we use the account name as an Organization tag or as a custom audience field (account_name) so that contacts can be segmented by their Composity account affiliation. If the customer needs per-account reporting, we recommend tagging strategy or using Mailchimp's built-in Groups.

Composity Leads map to Mailchimp Contacts with a Lead status tag applied. We preserve lead source and qualification data as Mailchimp merge fields (lead_source, qualification_status) or as tags. Mailchimp does not have a separate Lead object; all prospects live in the same audience as contacts. We add a lead_status tag to distinguish migrated Leads from migrated Contacts for segmentation purposes.

If the destination Mailchimp account uses Mailchimp for e-commerce (connected store or Shopify/WooCommerce integration), Composity Products migrate to Mailchimp Product records with SKU, price, and description. Product-to-contact associations (customers who purchased a product) can be modeled as Mailchimp tags or as product interest groups. This mapping only applies if the customer activates Mailchimp e-commerce; it is not part of a standard CRM-only migration.

Composity Deals and Opportunities have no Mailchimp equivalent. Mailchimp is a contact and email marketing platform and does not have deal stages, opportunity values, close dates, or pipeline views. We flag all Deals as non-migratable during scoping and deliver a written inventory of every open and closed Deal with its value, stage, and associated Contact for the customer to manage in a separate tool or spreadsheet after migration.

Composity Invoices (paid, partially paid, and unpaid) have no Mailchimp equivalent. Mailchimp does not store invoice records, payment status, or line-item billing history. We export invoice headers and line items as a CSV deliverable for the customer's accounting or finance team to import into their billing system of record. Unpaid or partially settled invoices requiring balance carry-forward are flagged explicitly.

Composity Production module records (production orders with bill-of-materials references) have no Mailchimp equivalent. Mailchimp does not have a manufacturing, job, or production data model. We flag Production module data as non-migratable and deliver a CSV export of production records for the customer's operations or manufacturing team.

Composity Projects (available in Growth tier and above) have no Mailchimp equivalent. Mailchimp is an email marketing platform and does not manage project records, milestones, or resource assignments. We deliver a CSV export of project records with status, dates, and assigned resources for the customer's project management tool.

Composity Inventory records (SKU, quantity, warehouse location, reorder levels) have no Mailchimp equivalent. Mailchimp does not store inventory data unless the customer uses Mailchimp e-commerce for product catalog management. If Mailchimp e-commerce is not active, inventory records are flagged as non-migratable and delivered as a CSV for the customer's inventory management system.

Composity activity records (calls, emails, meetings, tasks, notes linked to Contacts and Accounts) have no Mailchimp equivalent. Mailchimp tracks campaign-level engagement (opens, clicks, unsubscribes) but not CRM-level activities logged against a contact. We do not migrate engagement history. We deliver a written inventory of activity record counts by type as part of the scoping documentation so the customer understands what is not moving.