Migrate from NetHunt CRM to Mailchimp

NetHunt Contacts migrate as Mailchimp Subscribers. All standard fields (name, email, phone, address) map directly. NetHunt custom fields become Mailchimp merge fields with the original field label preserved. We use the Mailchimp Members API (POST /lists/{list_id}/members) with status set to subscribed by default. Any Contacts with no email address are flagged as a reconciliation item because Mailchimp Subscribers require a valid email address. Email opt-out status in NetHunt maps to HasOptedOutOfEmail in Mailchimp.

NetHunt Leads migrate as Mailchimp Subscribers using the same Members API endpoint as Contacts. Lead-specific fields (lead source, lead score, lifecycle stage in NetHunt) become Mailchimp merge fields with original field labels. Lead status values from NetHunt are preserved as a merge field for segmentation purposes in Mailchimp but do not map to a native Mailchimp status concept.

Mailchimp has no native Company or Account object. Company names from NetHunt migrate as a merge field (COMPANY) on the Subscriber record. If the customer wants company-level segmentation, we map each unique NetHunt Company to a Mailchimp Tag and apply it to all Subscribers linked to that Company. The choice between merge field and tag is made during scoping based on the customer's reporting needs.

NetHunt Deals have no Mailchimp equivalent. Mailchimp does not support Opportunity records, pipeline stages, deal values, or sales processes. We flag all active Deals during scoping, export them as a CSV for the customer's records, and do not attempt to create them in Mailchimp. If the customer needs deal tracking in Mailchimp, they must use a third-party integration or accept that deal management will move to a separate tool.

NetHunt Pipelines and associated stage definitions have no Mailchimp equivalent. Mailchimp does not support custom sales stages, visual pipeline views, or deal-progress tracking. We export pipeline definitions as part of the migration inventory document.

NetHunt Activity records (emails, notes, meeting records, comments attached to Contacts and Deals) have no Mailchimp equivalent. Mailchimp tracks campaign engagement (opens, clicks, unsubscribes) per Subscriber but does not maintain a native activity timeline. Email body content from NetHunt does not migrate into Mailchimp because there is no object to hold it. We flag activity volume during scoping so the customer understands the scope of data that will not transfer.

NetHunt Call Logs have no Mailchimp equivalent. Call duration, disposition, and recording metadata are lost during migration. We document the existence of call log records in the migration inventory but do not create equivalent records in Mailchimp.

NetHunt Tags migrate as Mailchimp Tags on the corresponding Subscriber. Tags are string values stored per record and map directly via the Mailchimp Tags API (POST /lists/{list_id}/members/{subscriber_hash}/tags). We apply tags in batch during migration. Pre-existing Mailchimp tags that conflict with NetHunt tag names are flagged during scoping for deduplication.

NetHunt Folders containing Records map to separate Mailchimp Audiences if the customer chooses to preserve folder-level segmentation. Each folder becomes its own Audience with field mappings configured per folder's custom field schema. Mailchimp has a limit on the number of Audiences (Standard tier supports multiple Audiences; free tier is limited to one). We configure Audience mapping during scoping and flag if the customer's plan tier constrains Audience count.

NetHunt custom fields within Folders become Mailchimp Merge Fields on the target Audience. Field type mapping is applied: text fields to text merge fields, date fields to date merge fields, number fields to number merge fields, and picklist fields to radio or dropdown merge fields. Merge field names are normalized to uppercase per Mailchimp convention. We create all merge fields via the Mailchimp Merge Fields API before Subscriber import begins.