Migrate from CRM Runner to Mailchimp

CRM Runner Contact records map directly to Mailchimp Audience members. The email address is the required merge field; first name and last name map to FNAME and LNAME. Any CRM Runner custom fields on contacts with text values under 255 characters map to Mailchimp merge tags. Fields exceeding 255 characters are flagged and either truncated or moved to a separate notes document for manual review. We dedupe by email address during import and flag records with missing email addresses for the customer's review before insertion.

CRM Runner Company records have no direct Mailchimp equivalent. We handle the contact-to-company relationship by creating a Mailchimp tag or group named after each Company record and applying it to all Audience members linked to that company in CRM Runner. The customer chooses tag or group strategy during scoping. Tags are simpler; groups enable group-level email suppression. We preserve the company name as the tag or group label and record the original CRM Runner company ID in a merge field crm_company_id__c for reconciliation.

CRM Runner Jobs (work orders, job status, location, assigned team members) have no Mailchimp equivalent. Job data does not migrate into the Mailchimp Audience. We extract the last job date, job status, and job location as optional merge fields on the Contact if the customer specifies this as a segmentation need, but the full Jobs object is excluded from standard scope. We recommend pairing the CRM migration with a dedicated field-service or project management tool for Jobs data.

CRM Runner Team Members (employee records with roles and permissions) do not map to Mailchimp contacts because they represent internal staff rather than marketing recipients. If the Team Member also has a Contact record in CRM Runner (e.g., the person is both an employee and a customer), we migrate that Contact but flag the Team Member record separately for the customer to decide whether to import as an Audience member. The permissions and role data from CRM Runner does not migrate to Mailchimp.

CRM Runner stores call logs, SMS threads, and in-app chat as discrete records attached to contacts or jobs. Mailchimp has no activity timeline equivalent — it only tracks email campaign engagement (opens, clicks, unsubscribes). We do not migrate communications history to Mailchimp. We do export the communications history as a separate JSON artifact for the customer's records, but this data set has no usable destination in Mailchimp and must be archived or moved to a separate system.

CRM Runner Tasks with due date, assignee, and status have no Mailchimp equivalent. Mailchimp does not support a task or to-do object. We do not migrate Tasks. If CRM Runner Tasks are linked to specific Contacts and the customer wants to preserve the task context, we export the task subject, due date, and status as a custom merge field on the Contact record during the Contact migration phase, accepting the loss of assignee and status fields.

CRM Runner custom fields on Contacts map to Mailchimp merge tags with the 255-character limit enforced. Multi-select picklist fields from CRM Runner map to Mailchimp groups with each picklist value as a group option. Checkbox fields map to Mailchimp merge tags with 1/0 values. Date fields map to Mailchimp date merge tags. We flag any CRM Runner custom field exceeding the 255-character limit during scoping and present three options: truncate, export as a separate notes document, or drop the field entirely.

CRM Runner deal pipeline stages (e.g., Prospect, Qualified, Proposal, Won, Lost) have no Mailchimp equivalent. Mailchimp is not a sales pipeline tool and does not track opportunity stage, deal value, or close probability. We do not migrate pipeline data. If the customer wants to use pipeline stage as a segmentation signal in Mailchimp, we can import the last-known pipeline stage as a tag or merge field on the Contact, but this is an informational label, not a functional pipeline.