Migrate from Followup CRM to Mailchimp

Followup CRM contacts map 1:1 to Mailchimp audience members via the Members API. Email address serves as the unique identifier for each contact — any contacts missing an email address are flagged as un-importable and are surfaced for manual review before the migration run commits to the Mailchimp audience. Duplicate email addresses across multiple Followup CRM records are also flagged for resolution before import.

Followup CRM companies do not have a direct Mailchimp equivalent. The company name migrates as a text merge field on the audience member record. Company-level properties (industry, employee count, annual revenue) also migrate as merge fields on the contact — Mailchimp has no separate company or account object.

Followup CRM deals — with amount, stage, close date, and pipeline assignment — have no native Mailchimp structure. We store deal name as a tag (e.g., DealName: Kitchen Renovation), deal amount as a number merge field, and deal stage as a tag so contacts can be segmented by pipeline status in Mailchimp.

Followup CRM pipeline objects organize deals into named stages. Mailchimp has no pipeline or stage object. We capture pipeline name as a contact tag prefix (Pipeline: Sales) and each stage name as a secondary tag so segments can filter contacts by their most recent deal stage.

Pipeline stage values (e.g., Prospect, Proposal Sent, Won, Lost) from Followup CRM become Mailchimp tags on the contact record. We map each stage name to a tag string and preserve the stage-entered timestamp as a text merge field if it exists, since Mailchimp's automation triggers cannot reference historical stage-transition dates.

Followup CRM follow-up reminders attached to contacts have no direct Mailchimp equivalent. The reminder text and due date migrate as a contact note. If the reminder has a specific date, we tag the contact with a trigger tag (FollowUpDue: YYYY-MM-DD) so a Mailchimp automation can route the contact into a follow-up campaign at the correct time.

Followup CRM quotes and proposals are document objects tied to deals. Mailchimp stores no document content. Quote name and total amount migrate as a contact note for reference, and the quote amount maps to a number merge field on the contact if a numerical value is present.

Followup CRM team quotas and goal metrics are CRM performance objects with no Mailchimp equivalent. We preserve quota name and assigned target value as tags on the contact record for the owner (e.g., Quota2024: $150,000), but actual quota tracking and performance reporting must be rebuilt in a BI tool or a separate CRM.

Followup CRM owner assignments on contacts map to two Mailchimp merge fields (OWNER_NAME__c and OWNER_EMAIL__c as text fields) so the sales rep identity is permanently attached to each contact record. The owner can also be added as a Mailchimp tag if segmentation by rep is needed for reporting.

Followup CRM file attachments on contacts and deals have no Mailchimp equivalent — Mailchimp does not store files on contact records. We log each attachment filename and original URL in the migration audit log so the files can be re-uploaded to a linked cloud storage tool and the reference can be added as a contact note.

Followup CRM call and meeting records attached to contacts migrate as Mailchimp contact notes with the original timestamp in the note body. Email activity is represented by Mailchimp's own engagement tracking (opens and clicks) once the migration is live — historical emails cannot be replayed in Mailchimp's platform.

Followup CRM's internal record ID is stored on each contact as a text merge field called SOURCE_RECORD_ID__c. This enables delta-run reconciliation (detecting which records have changed since the test migration) and allows cross-referencing back to the source system if a rollback is required.