Migrate from Concord CRM to Mailchimp

Concord CRM Contacts map directly to Mailchimp audience members. Email address serves as the dedupe key. We import subscribed contacts first, then separately import unsubscribed and bounced contacts into Mailchimp's suppression list to maintain compliance and prevent accidental re-subscription. Concord's email opt-in status, phone number, physical address, and custom fields map to Mailchimp merge fields (EMAIL, FNAME, LNAME, PHONE, ADDRESS) or custom merge fields if the field type is supported. Contacts exceeding Mailchimp's Free plan limit of 500 contacts are flagged during scoping and the customer selects the appropriate paid plan before migration begins.

Concord CRM Companies have no direct Mailchimp equivalent because Mailchimp has no Company or Account object. We convert each Company into a tag applied to every Contact associated with it in Concord. The tag format is 'Company: [Company Name]' and preserves the company-contact relationship as a contact attribute. Company address, domain, and industry fields cannot be stored natively in Mailchimp; we map address to a merge field and store domain and industry as additional tags (e.g., 'Industry: Technology') or in a custom text merge field. Companies must be exported from Concord before Contacts so that the company-contact association is resolved during the Contact tagging step.

Concord CRM Deals have no direct Mailchimp equivalent. We convert Deal data into tags on the associated Contact record to preserve deal context. Tags include 'Deal: [Deal Name]', 'Deal Value: [Amount]', 'Deal Stage: [Stage Name]', 'Expected Close: [Date]', and 'Deal Owner: [Owner Email]'. These tags are informational only and do not create Mailchimp CRM records. Pipeline stages from Concord's multiple-pipeline model become tags under the 'Pipeline: [Pipeline Name]' prefix. The customer should select a CRM with native Deal support if ongoing deal pipeline management is required post-migration.

Concord CRM Products (name, price, SKU, description) have no direct Mailchimp equivalent. We tag contacts associated with a product purchase or interest using 'Product: [Product Name]', 'Product SKU: [SKU]', and 'Product Price: [Price]' tags on the contact record. Product information preserved as tags allows the customer to segment audiences in Mailchimp by product interest or purchase history for targeted campaigns. Products that are not linked to contacts in Concord are exported as a separate reference table that the customer can use to build Mailchimp product-based segments manually.

Concord CRM Activities (calls, meetings, tasks) have no native Mailchimp equivalent. We encode engagement history as tags on each Contact record using 'Activity: Call', 'Activity: Meeting', 'Activity: Task', plus the date and a brief note summary. The most recent activity per type is stored; full activity history is collapsed into the tag set because Mailchimp does not maintain a contact activity timeline. Concord's activity-linked resource type (Contact, Company, or Deal) is preserved as an additional tag for audit purposes. The customer should understand that Mailchimp's reporting shows campaign-level engagement (opens, clicks) but not pre-campaign sales activity history.

Concord CRM custom fields map to Mailchimp merge fields where types are compatible. Mailchimp supports TEXT, NUMBER, DATE, ADDRESS, PHONE, and WEBSITE merge field types natively. Boolean, select, and multi-select custom fields from Concord that do not map to a native Mailchimp type are converted to tags using 'Custom: [Field Name]: [Value]' format. Boolean fields produce a tag only if the value is true, omitting the tag for false values to keep the tag set lean. We confirm all Concord custom field names and types during scoping to design the merge field schema before production migration.

Concord CRM workflows (trigger: Company/Contact/Deal created, Deal stage changed; action: Create Activity, Send Email, Trigger Webhook) do not migrate and do not execute during data import. Mailchimp has no equivalent runtime automation engine tied to bulk contact operations. We deliver a written inventory of every active Concord workflow during scoping, including its trigger conditions, actions, and recommended Mailchimp Customer Journey equivalent for the customer's admin to rebuild post-migration. Email-send and contact-tagging automations transfer conceptually to Customer Journey; action-type automations (Create Activity, Trigger Webhook) have no Mailchimp equivalent and require a separate tooling decision.

Concord CRM Users (email, name, role) export via API. There is no Mailchimp equivalent for users or roles. We map the Concord user assigned as the contact owner to a 'Owner: [User Email]' tag or merge field on each Contact record, preserving the ownership attribution. Concord role names are stored as a 'User Role: [Role Name]' tag on contacts owned by users in that role. The customer's Mailchimp account admin is the only Mailchimp-level user role; shared access requires a separate Mailchimp team invitation handled outside the migration scope.