Migrate from Net-Results to Mailchimp

Net-Results Contacts map directly to Mailchimp Members within the target Audience. Standard fields (first_name, last_name, email, phone, address) map to Mailchimp merge fields FNAME, LNAME, EMAIL, PHONE, and ADDRESS. Lifecycle metadata and custom fields expand to additional merge fields, subject to Mailchimp's 255-character text merge field limit. We flag any custom field exceeding this length and advise truncation or tag-based storage for long-text values. Status (active, unsubscribed, bounced) maps to Mailchimp Member status at migration time.

Net-Results Company records have no native Mailchimp equivalent. The company_name and domain fields migrate as text merge fields (COMPANY, COMPANYDOMAIN) on the Member record. If the customer uses a CRM alongside Mailchimp (Salesforce, HubSpot), we recommend mapping Company records to a CRM integration rather than storing account context in Mailchimp merge fields. This is a configuration decision made during scoping.

Net-Results Campaigns map to Mailchimp Campaigns as metadata (name, type, send date, status). Campaign type (newsletter, automated, triggered) maps to Mailchimp campaign type. Note that Net-Results Campaign-Campaign Member enrollment history does not map to Mailchimp because Mailchimp tracks sends per Member in reporting rather than as a campaign-enrollment record.

Net-Results individual send events (open, click, bounce) are activity-level records with no direct Mailchimp object equivalent. We migrate open/click/bounce status as Tags on the Member record (e.g., tag: opened_campaign_2024Q1, clicked_link_A) to preserve engagement context within Mailchimp. Member-level status flags (status: subscribed, unsubscribed, bounced, cleaned) migrate directly and override any conflicting state during the suppression reconciliation pass.

Net-Results drag-and-drop templates export as HTML with embedded asset references. Mailchimp's template engine does not render Net-Results layouts identically; we export the HTML and image assets, flag each template for manual review, and advise customers to test sends from imported templates before launching active campaigns. This is a known limitation documented in Net-Results platform notes and confirmed by the pair-specific evidence showing template HTML reformatting as a migration challenge.

Net-Results workflow logic is not exportable as a portable artifact. We inventory every active Net-Results workflow by name, associated contact count, step count, trigger type, and action sequence. This inventory is delivered as a written document with recommended Mailchimp Automation equivalents (e.g., Net-Results drip campaign maps to Mailchimp Customer Journey automation). The customer's team rebuilds the automations in Mailchimp Automations; this rebuild effort is outside migration scope.

Net-Results hard bounces, unsubscribes, and manually suppressed contacts export as a suppression list. We import this into Mailchimp as a non-subscribed Member list against the target Audience. During reconciliation, we deduplicate against any existing Mailchimp suppression records to avoid false opt-out flags on active contacts that may have been re-subscribed since the original suppression event. This post-load pass is mandatory to protect deliverability.

Net-Results custom fields on Contacts and Companies require explicit field-by-field mapping against Mailchimp's merge field schema. Mailchimp supports text, number, date, phone, address, and dropdown merge field types. We inventory all custom fields during discovery, map types accordingly, and flag any field exceeding Mailchimp's 255-character text limit. Long-text values are either truncated with a note or moved to Tags at the customer's preference.