Migrate from Delta Sales CRM to Mailchimp

Delta Contacts map directly to Mailchimp subscribers within a target Audience. We export name, email, phone, address, company linkage, and owner assignment as standard Mailchimp subscriber fields. The email field serves as the dedupe key. Delta's contact status (active/inactive) maps to Mailchimp's subscribed/unsubscribed/bounced/archive status. Any Delta contacts without a valid email address are held in a separate reconciliation file because Mailchimp requires a valid email for every subscriber record.

Delta Companies map to Mailchimp in one of two ways depending on the customer's segmentation needs. We create a COMPANY merge field on the Mailchimp subscriber record to store the company name directly on each contact, preserving the contact-to-company relationship. Alternatively or additionally, we create a Mailchimp Tag per company name and tag all contacts belonging to that company, enabling audience segmentation by company at the Mailchimp level. The choice between merge field and tag strategy is made during scoping based on the customer's reporting requirements.

Delta Leads do not have a direct Mailchimp equivalent because Mailchimp does not distinguish between leads and customers in its data model. All Delta Leads migrate as Mailchimp subscribers, with a LEAD_SOURCE merge field capturing the original lead source value from Delta. We apply a 'Delta Lead' tag to all records that originated as Delta Leads so that the customer can segment the audience and target nurture campaigns specifically to the migrated lead pool.

Delta Products migrate to Mailchimp's product catalog (Mailchimp Commerce) if the customer has Mailchimp Standard or Premium with e-commerce features active. Product name, SKU, price, description, and URL migrate as Mailchimp Product fields. If the customer does not have Mailchimp e-commerce enabled, we store product data as PRODUCT merge fields on the subscriber record, which enables product-interest segmentation but not full product catalog display. We confirm e-commerce plan tier during discovery.

Delta custom fields on Contact, Company, and Lead records map to Mailchimp merge fields. We extract the full custom field definition during CSV export, map Delta field types (text, number, date, dropdown, checkbox) to the closest Mailchimp merge field type (text, number, date, dropdown, radio), and configure the merge field in the Mailchimp audience before import. Merge field values populate on a per-subscriber basis during the import phase. Mailchimp has a documented merge field limit per audience; we confirm field count against this limit during scoping.

Delta Deals (opportunities with pipeline stages, amounts, probabilities, and owner assignments) have no Mailchimp equivalent. Mailchimp does not support a deal or opportunity object, pipeline stages, deal amounts, or probability fields. We export the deal data as a supplementary CSV for the customer's reference and do not import it into Mailchimp. If the customer requires deal pipeline visibility post-migration, we recommend a separate CRM platform (Pipedrive, HubSpot Free, or Salesforce for SMB) to run alongside Mailchimp for sales pipeline management.

Delta Pipelines (named deal sequences with customizable stages) have no Mailchimp equivalent. Mailchimp's data model is subscriber-centric and does not support multi-stage pipeline visualization or sales process configuration. We export pipeline names and stage definitions as a written configuration document that the customer's admin can use to configure any new CRM they adopt post-migration. We do not recreate pipeline stages as Mailchimp segments because that would conflate pipeline pipeline stages with audience segmentation, which is a different concept.

Delta Activity records (calls, meetings, tasks, follow-ups with dates, assignees, and dispositions) are mapped to Mailchimp tags as a historical reference layer. We export the most recent 90 days of activities per contact and create date-stamped tags (e.g., 'call_2025_09', 'meeting_2025_10') on the corresponding Mailchimp subscriber. Full activity history is not migrated because it creates tag bloat and exceeds Mailchimp's practical segmentation utility for marketing audiences. Any activities with disposition values (won, lost, follow-up required) are noted in a separate CSV for the customer's CRM rebuild scope.

Delta Invoices (invoice headers, line items, payment status, and totals) do not migrate. Mailchimp does not support invoicing, billing, or financial record objects. Invoice data is exported as a supplementary CSV reference file. If the customer uses Mailchimp e-commerce integrations (Shopify, WooCommerce), order and purchase history can be captured going forward through those native integrations rather than migrated from Delta.

Delta Payment records (payment amounts, dates, methods, and invoice references) do not migrate to Mailchimp. Mailchimp does not have a payment or transaction object. Payment data is exported as a supplementary CSV reference file for the customer's financial records. If the customer uses Mailchimp Commerce with an e-commerce platform, future payment data flows through the native integration.