Migrate from Datacor CRM to Mailchimp

Datacor CRM Contacts migrate to Mailchimp Subscribers within the target Audience. Core fields (First Name, Last Name, Email) map directly. Phone, physical address, and company name map to Mailchimp standard merge fields (PHONE, ADDRESS). Chemical-industry fields (regulatory compliance contact flag, shipping address distinct from billing, EDI readiness flag) map to Mailchimp custom merge fields that the customer provisions before import. We deduplicate on email address across both the CRM layer and any ERP-extracted records to avoid duplicate subscribers on write.

Datacor CRM Accounts map to Mailchimp Audiences. Multi-subsidiary account hierarchies in Datacor (parent Account with child Accounts) have no direct Mailchimp equivalent; we collapse the hierarchy into flat Audience-level segmentation using tags on Subscribers. Industry classification, regulatory certifications, and compliance status from Datacor Accounts become segment filters or custom merge fields on the Audience. We create one primary Audience in Mailchimp per Datacor account group and use tags to preserve subsidiary-level distinctions.

Datacor CRM Opportunities (with multi-stage sales cycles, regulatory approvals, and quote-to-order processing) have no Mailchimp equivalent. Mailchimp does not manage pipeline stages, deal values, or probability percentages. We do not migrate Opportunities. We deliver a written inventory of open Opportunities (stage, value, close date, owner) as a CSV for the customer's admin to review and act on outside Mailchimp. Opportunities are not archived within Mailchimp because the platform does not support that record type.

Datacor CRM Quotes (multi-line product specs with CAS numbers, GHS classifications, regulatory specifications, and ERP pricing engine references) cannot be represented in Mailchimp. Mailchimp has no quoting object, no product spec fields, and no regulatory attribute fields. We deliver a written inventory of active Quotes as a CSV including header fields, line item details, and total values for the customer's admin to handle outside Mailchimp. The ERP pricing engine integration that produces Datacor Quotes cannot be reconstructed in Mailchimp.

Datacor CRM Cases (customer service requests, complaint tracking, case-thread email history) have no Mailchimp equivalent. Mailchimp does not support case management, ticket queues, or threaded communications. We do not migrate Cases. Plain-text case descriptions and resolutions export as a CSV for admin review; email thread history may export as plain text but Mailchimp has no object to attach it to. We flag this gap explicitly so the customer does not assume service history transfers with contact records.

Datacor CRM Products carry chemical-specific attributes (CAS numbers, GHS hazard classifications, SDS document links, formulation data) that Mailchimp cannot store. Mailchimp's product catalog (available on Standard and Premium plans via Mailchimp Commerce) supports SKU, price, and inventory fields but not regulatory or hazard classifications. We do not migrate Products to Mailchimp. If the customer uses Mailchimp Commerce, we deliver a product CSV that the admin enriches with only the fields Mailchimp Commerce supports.

Datacor CRM Activity records (call reports, logged activities, task records, meeting entries) have no Mailchimp equivalent. Mailchimp tracks email engagement (opens, clicks, unsubscribes) natively as system-generated events but does not store historical call logs, meeting records, or manually logged tasks. We do not migrate Activities. The customer should preserve a backup of Datacor's activity export in its native format. No reconstruction of the activity timeline is possible in Mailchimp.

Datacor CRM's chemical-industry fields (CAS Registry Numbers, GHS hazard classifications, SDS document link, regulatory certification dates, EDI readiness flags) have no Mailchimp native equivalents. We create Mailchimp custom merge fields of the appropriate type (text, date, checkbox) before import, but the customer must provision these in their Mailchimp account under Audience Settings > Merge fields. CAS numbers and GHS classifications require text merge fields; certification expiry dates require date merge fields. If these fields are not pre-created, we write the raw data into a general-purpose NOTES merge field with a prefix label and flag them for post-migration enrichment.