Migrate from Spin CRM to Mailchimp

Discovery and export coordination

We audit the Spin CRM account across Contacts, Companies, Leads, Deals, and any visible custom fields. We request a full custom field inventory from the customer and compare it against what the CSV export headers expose. We confirm the export walkthrough with the customer (where to find the settings-menu export per object) and recommend a 24-48 hour data-freeze window before the final export set. On the Mailchimp side, we verify the destination Audience structure, confirm existing merge fields, and identify any new merge fields required based on the Spin CRM custom field list.

CSV export validation and field mapping

We review the exported CSV files from Spin CRM against the expected record counts and column headers. We identify any missing custom fields and request a re-export if needed. We build a field mapping document that pairs each Spin CRM column header with the corresponding Mailchimp merge field (or tag strategy) and documents any columns that have no Mailchimp destination. This mapping is reviewed and signed off by the customer before we proceed to the transform layer.

Contact hygiene pass

Before importing into Mailchimp, we run the Spin CRM Contact export through a data quality check: email address format validation, duplicate detection by email address, and identification of records with missing email addresses (these cannot become Mailchimp Audience members). We deliver a hygiene report to the customer showing the record counts by status (clean, bounced-risk, duplicate, no-email) and recommend either correcting the source data or excluding high-risk records from the initial import to protect the Mailchimp sending reputation. Per Mailchimp's own migration guidance, cleaning the list before import improves initial deliverability rates.

Merge field creation in Mailchimp

We create the required merge fields in the destination Mailchimp Audience based on the field mapping document. This includes TEXT merge fields for company name, owner email, and any Spin CRM text custom fields; NUMBER merge fields for deal values or numeric custom fields; and DATE merge fields where applicable. Merge fields are created via the Mailchimp API or Audience settings. If the customer has multiple Audiences, we repeat merge field creation per Audience. We do not create Tags during this phase; Tags are applied during the import transform based on the segmentation strategy agreed in scoping.

Import and reconciliation

We import the cleaned Contact CSV into Mailchimp using the Mailchimp Marketing API with batch processing and error handling. Each imported record receives applicable Tags (e.g., 'Source: Spin CRM', company name tag, lead-status tag) based on the segmentation strategy. After import, we reconcile record counts: total imported vs total exported, bounced records vs clean records, and duplicate records merged or flagged. We deliver a migration reconciliation report showing the import outcome and any records that failed to import with the error reason.

Gap documentation and automation rebuild handoff

We deliver a written migration summary documenting which Spin CRM objects migrated (Contacts, Leads, Companies via merge field, custom fields via merge tags) and which did not (Deals, Pipelines, Stages, Activities). For the unmapped objects, we include record counts and recommended follow-up actions (Deal export for spreadsheet backup, Activity history archive). We include a written inventory of any Spin CRM workflow or automation patterns that the customer should rebuild in Mailchimp's Automation builder (email automations, campaign sequences, tag-based triggers). We do not rebuild Mailchimp automations as standard scope.