Migrate from Nutshell to Mailchimp

Nutshell People records map to Mailchimp Audience contacts. The Nutshell name fields (first_name, last_name) map to Mailchimp FNAME and LNAME merge fields. Email, phone, and address from Nutshell map to the corresponding standard Mailchimp fields. We use Mailchimp's PUT /lists/{list_id}/members/{subscriber_hash} endpoint to upsert contacts, which handles update versus insert based on email hash. If the source Nutshell account uses email as the primary identifier, the upsert is deterministic and idempotent for repeated migration runs.

Nutshell Leads are distinct records with their own field definitions that do not have a separate equivalent in Mailchimp. We merge Lead records into the same Audience as People records, using a custom merge field nut_lead_source__c set to true for records that originated as Nutshell Leads. The lead_status and any lead-specific custom fields from Nutshell migrate to additional merge fields in Mailchimp so that the customer can segment on original record type.

Nutshell Company names map to the Mailchimp COMPANY merge field on each contact. Since Mailchimp contacts are flat (not hierarchically attached to company records), the Company name is stored as a per-contact merge field value. If Nutshell Companies have custom fields the customer wants to preserve (industry, size tier, region), we create additional merge fields in the Mailchimp Audience and populate them from the Company record by resolving the Company lookup on the source Nutshell People record. Multi-company contacts (rare) are handled by storing the primary company in COMPANY and appending secondary names to a nut_companies__c text merge field.

Nutshell custom fields defined on People records map to Mailchimp merge fields in the destination Audience. We enumerate all custom field definitions during scoping, map each to a Mailchimp merge field of appropriate type (TEXT, NUMBER, DATE, PHONE, ADDRESS), and create the merge fields via the Mailchimp API before importing any contacts. Merge field values are populated per record during the batch upsert. Note that Mailchimp merge fields have a 255-character limit on TEXT fields; long text fields from Nutshell are truncated with a warning flag in the reconciliation report.

Nutshell tags on People records map directly to Mailchimp tags on the corresponding Audience contact. We extract the full tag string per People record and apply tags via Mailchimp's POST /lists/{list_id}/members/{subscriber_hash}/tags endpoint in batch operations. Nutshell's flat tag taxonomy maps cleanly to Mailchimp's tag model. If Nutshell uses hierarchical tag categories, we flatten them into dot-separated tag strings (e.g., Region.North.Americabulk to Region.North.America) so the customer can reconstruct segments in Mailchimp if needed.

Nutshell Pipelines have no equivalent in Mailchimp. Mailchimp does not track deal stages, deal values, pipeline probabilities, or sales process flow. We do not migrate Pipelines or Deal records. During scoping, we inventory all active Nutshell Pipelines and Deals and document them in the migration handoff report so the customer's team can decide whether to export to a spreadsheet, move to a separate CRM tool, or use Mailchimp's third-party integrations (e.g., Zapier connecting to a lightweight deal tracker) for ongoing tracking.

Nutshell Activity records (calls, emails, meetings, tasks with timestamps and body content) have no equivalent in Mailchimp. Mailchimp tracks campaign engagement metrics (opens, clicks, unsubscribes) but not the CRM-style activity timeline that Nutshell maintains per contact. We do not migrate Activity records. Email subject lines and dates from Nutshell activity history are not transferred unless the customer specifically requests them as a custom Note documented in the handoff. Customer Journey entry conditions in Mailchimp cannot be seeded from Nutshell activity history without a custom data warehouse integration.

Nutshell Users who own records do not have a direct Mailchimp equivalent. Mailchimp does not assign record ownership to users within an Audience. If the customer needs to track which sales rep is associated with a contact, we create a nut_owner__c merge field and populate it from the Nutshell owner name for contacts where an owner is assigned. This preserves the association for segmentation purposes but does not create a user-permission model in Mailchimp.