Migrate from NextCRM to Mailchimp

NextCRM Contact records map directly to Mailchimp Audience members. Email address is the dedupe key. Required Mailchimp merge fields (FNAME, LNAME) are populated from NextCRM's first_name and last_name properties; we flag any Contact missing these fields before import so they can be corrected or accepted as partial records. Custom field values from NextCRM map to Mailchimp merge fields using type-appropriate mapping: text to text, date to date, dropdown to dropdown, and number to number. The destination Mailchimp Audience must be created and authenticated before any import begins.

NextCRM Tags transfer directly to Mailchimp Tags on the Audience. Tags preserve as atomic string values and do not require schema configuration at the destination. We apply all tags during import using the Bulk Member Tags API endpoint, batching by 500 tags per request per Mailchimp's rate limits. Tag assignment order does not matter for deliverability.

NextCRM Lists and Advanced Segmentation rules map to Mailchimp Segments. Each List becomes a separate Audience Segment within the Mailchimp Audience, preserving the segment name from NextCRM. Advanced Segmentation rules (behavioral conditions, engagement filters, custom field criteria) do not transfer automatically because Mailchimp's segmenting syntax differs. We document each NextCRM segment's logic with its conditions and criteria, and the customer rebuilds them in Mailchimp's segment builder using the documented rule equivalent.

NextCRM Custom Fields map to Mailchimp Merge Fields (merge tags) in the Audience. We use Mailchimp's REST API to pre-create merge field definitions matching the source field type before importing any records. Multi-Select fields from NextCRM require special handling: Mailchimp Groups are the only way to sync multi-select values, so we create a Mailchimp Group Category per multi-select field and populate Group names from the NextCRM values. Text-type multi-select fields can alternatively map to a text merge field with pipe-delimited values, and the customer chooses the strategy during scoping.

NextCRM campaign records (name, audience assignment, send status) migrate as a Campaign object in Mailchimp. Active sends must be paused before migration begins per Mailchimp's switching guide. We preserve campaign structure and audience list references so campaigns can be re-created and resumed in Mailchimp. Campaign content and templates do not migrate and must be rebuilt; we document the template layout and asset references from NextCRM.

NextCRM Visual Automation Builder workflows are platform-specific and cannot be exported as transferable data. We extract the structure of each workflow including triggers, delay steps, conditional branches, email actions, and tag assignments, and deliver a written inventory document with the recreation steps for each workflow mapped to Mailchimp Customer Journeys equivalents. The customer or a Mailchimp specialist rebuilds the automations post-migration. No active workflow logic moves automatically.

Email sequences and follow-up automations in NextCRM are tied to the Visual Automation Builder and do not export. We document the sequence logic (step order, delay intervals, conditional splits, email content references) for manual rebuild. Mailchimp's Customer Journeys builder supports multi-step email sequences with delays and conditions, and Classic Automations offer a simpler cadence model. The customer's marketing team uses the documented sequence to rebuild in Mailchimp.

We export bounced, unsubscribed, and spam-reported contacts from NextCRM and import them to Mailchimp as a suppression list before importing active subscribers. This order is required per Mailchimp's deliverability best practices to prevent re-engaging suppressed addresses and damaging sender reputation. Suppression list import uses Mailchimp's Import API endpoint with the status set to subscribed for the suppressed addresses so they are excluded from future campaigns.