Migrate from Cordis CRM to Mailchimp

Cordis CRM Contact records map to Mailchimp Audience Members. We use email address as the primary dedupe key and map standard fields (First Name, Last Name, Phone) to Mailchimp merge fields (FNAME, LNAME, PHONE). Custom contact fields identified during scoping become Mailchimp custom merge fields created in the destination audience before import. Unsubscribe status from Cordis CRM exports is mapped to Mailchimp's member status (subscribed/unsubscribed/cleaned) to respect opt-out signals.

Cordis CRM Company records do not map to a native Mailchimp object because Mailchimp has no relational company record. We extract the company name from each Contact's linked Company record and apply it as a Tag on the corresponding Member in Mailchimp (e.g., Tag: CompanyName). This preserves the company association for segmentation and filtering but does not create a separate company-level record. If multiple Contacts share a Company, all receive the same Tag value.

Cordis CRM Pipeline and Deal records have no equivalent in Mailchimp. Pipeline stages, Deal values, and Deal stage history do not migrate. We flag all Pipeline and Deal records in the source export and note them in the migration scope document for the customer to handle manually if needed. This is a fundamental structural difference between a CRM and an email marketing platform.

Cordis CRM Campaign membership (which Contacts were part of which Campaigns) migrates to Mailchimp Tags applied to Members. Each Cordis Campaign name becomes a Mailchimp Tag, and every Member associated with that Campaign receives the corresponding Tag. Campaign-level engagement data (opens, clicks) is not preserved as Mailchimp does not store external campaign history.

Cordis CRM Tasks (automated and manual) have no equivalent in Mailchimp. Task status, due dates, owners, and recurrence rules do not migrate. We document the active task count and hand off a task inventory to the customer for manual recreation or workflow rebuild in Mailchimp Customer Journeys if applicable.

Cordis CRM Documents linked to Contact or Company records do not migrate to Mailchimp, which has no native document management capability. We extract document filenames and linking metadata and deliver them as a separate file inventory so the customer can decide how to store and link documents post-migration (Google Drive, SharePoint, or a separate document management tool).

Cordis CRM custom contact fields identified during scoping are created as custom merge fields in the Mailchimp Audience before Member import. We map the field type from Cordis to the nearest Mailchimp merge field type (text, number, date, phone, address, or dropdown). Options for multi-select or checkbox fields in Cordis CRM are migrated as comma-separated text values in Mailchimp merge fields.

File attachments linked to Contact or Company records are exported individually with filename and linking metadata preserved in a separate file inventory. Mailchimp does not support file attachment storage on Audience Members. We re-associate exported files post-migration using record ID mapping tables delivered alongside the migration report.