Migrate from Star CRM to Mailchimp

Star CRM Contact records map to Mailchimp Audience Members. The contact email address is the primary key and import identifier. First name, last name, phone, and address fields map to Mailchimp merge fields (FNAME, LNAME, PHONE, ADDRESS). We preserve the original Star CRM contact ID in a custom merge field for audit traceability. Subscriber status in Mailchimp is derived from the contact's email marketing consent flag in Star CRM; contacts without a documented opt-in status are imported as unsubscribed to preserve deliverability standing.

Star CRM Company records do not have a direct Mailchimp equivalent. We create a company name tag on each related contact (applying the company name as a lowercase tag) and optionally create a COMPANY merge field on the audience to store the company name as a text value. If the customer uses multiple Star CRM companies per contact (rare but possible), all company names are joined as comma-separated tags.

Star CRM Deals have no Mailchimp equivalent because Mailchimp does not include an Opportunity or pipeline object. We can preserve deal information as custom merge fields on the associated Audience Member (for example, DEAL_VALUE as a number field, DEAL_STAGE as a dropdown field, DEAL_CLOSE_DATE as a date field), but this data functions as read-only contact attributes rather than active pipeline management. Customers who need deal tracking must use a separate CRM or Mailchimp integrations with platforms like HubSpot or Salesforce.

Star CRM Pipelines define deal stage sequences and do not have a direct Mailchimp equivalent. Pipeline stage names can be imported as Mailchimp Tags or used to create Segments, but Mailchimp Segments are dynamic audience filters used for targeting campaigns rather than sales process trackers. We discuss with the customer during scoping whether pipeline stage information should be preserved as Tags (for campaign filtering) or dropped from migration scope if it has no marketing relevance.

Star CRM Activity records capturing calls, emails, meetings, and tasks cannot map to a native Mailchimp engagement object because Mailchimp engagement data is generated by Mailchimp campaigns, not imported from external sources. We migrate Notes from Star CRM as Mailchimp Notes attached to the corresponding Audience Member. Call logs and meeting records migrate as text Note content. Email engagement history does not migrate because it would create a false record of Mailchimp campaign activity that never occurred.

Star CRM Tags on Contacts map directly to Mailchimp Tags on the corresponding Audience Member. Tags are applied at import time using the Mailchimp Tags API endpoint, batched to respect API rate limits. Multi-value tags in Star CRM (comma-separated) are split into individual Mailchimp tags during the transform phase.

Star CRM custom contact properties map to Mailchimp Merge Fields. Mailchimp supports up to 40 merge fields per audience, with types including text, number, date, dropdown, email, phone, URL, address, and birthday. We match Star CRM property types to the closest Mailchimp field type during schema design. If the Star CRM instance has more than 40 custom properties across all objects, we prioritize contact-level custom fields and flag remaining properties as out-of-scope.

Star CRM User records (sales reps, admins) have no Mailchimp equivalent because Mailchimp does not have a per-user seat model for contact management. Owner assignment on Star CRM Deals or Activities is preserved by adding the owner name as a custom field value on the associated records rather than as a User record. If the customer needs multiple Mailchimp users, Mailchimp's own team member access model is used post-migration.

Star CRM file attachments (documents, images) associated with Contact or Deal records cannot migrate to Mailchimp because Mailchimp does not support file attachments on Audience Members. We download all attachment files, build a manifest linking each file to its parent Star CRM record ID, and deliver the manifest to the customer. Files can be stored in a separate document manager or Google Drive, with links to the relevant contacts recorded as merge field values if needed.