Migrate from Dashcord to Mailchimp

Dashcord Contacts map to Mailchimp Subscribers within a target Audience. We use the Contact's email address as the subscriber identifier and merge field anchor. Standard Contact fields (FirstName, LastName, Email, Phone, MailingAddress) map to Mailchimp merge fields (FNAME, LNAME, EMAIL, PHONE, ADDRESS). Any custom Contact fields created by Dashcord or the customer's Salesforce org become additional Mailchimp merge fields. Deduplication is handled by email address at import time.

Dashcord Leads also map to Mailchimp Subscribers. We export all Salesforce Leads with IsConverted = false to preserve the pre-conversion contact pool. Lead fields (FirstName, LastName, Email, Phone, Company) map to the same merge field set as Contacts. Leads that have already converted to Contacts in Salesforce are excluded to avoid duplicate Subscriber creation. The customer's admin decides whether to import converted Leads as a separate Audience or tag them differently.

Dashcord Account name and Industry map to the BUSINESS merge field in Mailchimp as a reference annotation. Mailchimp does not have a native company object, so Account-to-Contact relationships are resolved by attaching the Account name as a merge field value on each Subscriber record. This allows segmentation by company or industry in Mailchimp without a separate Account migration.

Dashcord Salesforce Campaigns migrate as tags on the Subscriber records, not as native Mailchimp campaigns. Each Salesforce Campaign Name becomes a Mailchimp tag (e.g., Q1_Newsletter_2025, Webinar_Series_2024) applied to every Subscriber who was a Campaign Member. The customer's admin rebuilds Mailchimp email campaigns separately, using these tags to recreate audience segments. We preserve the Campaign Member status (Sent, Opened, Clicked, Responded) as tag suffixes for reference.

Each Salesforce Campaign Member record generates a Mailchimp tag on the linked Subscriber. The tag format is campaign_name__status (e.g., Product_Launch_2025__Opened). A single Subscriber can have multiple tags reflecting participation across multiple Dashcord campaigns. We do not create Mailchimp Segments from tags as part of the migration; that is a post-migration segmentation exercise for the customer's marketing team.

Dashcord lifecycle stage values (stored as custom picklist fields on Lead and Contact) migrate to a LIFECYCLE merge field or as a tag on each Subscriber. The customer chooses the strategy during scoping: merge field preserves the raw stage label for all future Mailchimp campaigns, while tag strategy allows for dynamic segment creation in Mailchimp Customer Journeys. We preserve the full set of picklist values from the Salesforce org metadata for completeness.

Numeric lead scores stored as custom fields on Salesforce Lead (e.g., Dashcord_Score__c) migrate to a LEAD_SCORE merge field on the Subscriber. Mailchimp has no native scoring engine, so the score value is informational and used for segmentation rules (e.g., audiences with LEAD_SCORE > 70 receive a different automation path). If the customer's Mailchimp plan supports it, a Scoring Plus add-on can be enabled post-migration.

Dashcord's event management module stores event attendance records as custom Salesforce objects. We inspect the custom object's field definitions during pre-flight to identify event name, date, registration status, and attendance fields. These map to Mailchimp tags (EVENT_Webinar2025__Attended) or custom merge fields. Large event history becomes a tagged annotation rather than native event records since Mailchimp does not have an event management object.

Dashcord email send, open, and click data stored as Salesforce Activity records (Tasks with type Email and Emails standard object) migrates as tagged annotations on Subscriber records. Each activity type generates a tag suffix (e.g., Email_Sent_Date, Email_LastOpened). We preserve the original activity timestamp in the tag for segmentation use. Mailchimp does not accept external engagement history as native activity records; the tag approach makes historical engagement visible in the subscriber profile without breaking Mailchimp's activity model.

File attachments on Dashcord records (stored as Salesforce ContentDocument linked via ContentDocumentLink) are not migrated. Mailchimp's file management system (Content Studio) operates independently from Salesforce's document model, and file re-attachment would require manual re-upload by the customer's admin. We flag any records with significant attachments in the pre-flight report so the admin can re-upload critical assets post-migration.