Migrate from SalesNexus to Mailchimp

SalesNexus Contact records map to Mailchimp Members within a designated Audience. The contact email address is the primary key for deduplication. First name, last name, phone (if present), and any standard fields migrate directly. Custom fields migrate as merge fields (see custom field notes). Contact status (active/inactive) maps to Member status in Mailchimp. SalesNexus does not expose a bulk export endpoint for contacts — we use paginated REST API calls with exponential backoff and chunking to extract the full contact list without triggering rate-limit errors on Starter-plan accounts with 500 API call limits.

SalesNexus Company records have no direct Mailchimp equivalent. Mailchimp is audience-centric, not account-centric. We offer two strategies during scoping: (1) Map each Company to a Tag on the related Member records, preserving the company name as a label for segmentation. (2) Create a MERGE0-style text merge field on the Mailchimp Audience and populate it with the Company name. Strategy 1 is preferred for segmentation use cases; Strategy 2 preserves the data for reporting but does not support multi-company filtering in Mailchimp's native UI.

SalesNexus Email Templates with merge fields and HTML content export as template bodies and subject lines. We convert SalesNexus merge field syntax (typically {{contact.field_name}} or similar) to Mailchimp merge tag format (*|FNAME|*, *|LNAME|*, *|EMAIL|*, *|PHONE|*, and custom *|MERGEn|* or *|FIELDNAME|* tags). HTML email templates migrate as code, and we validate the converted template in a test send before committing to the destination Audience. Plain-text versions are generated from HTML for Mailchimp's multipart format support.

SalesNexus Marketing Forms with field configurations and webhook/post URLs migrate as Mailchimp signup forms. Form field labels and input types map to Mailchimp field types (text, email, number, phone, date, dropdown, radio, checkbox). The SalesNexus form submission history migrates as a list of existing Members with the form's tags applied so that historical form submissions are represented in Mailchimp audience tags. Iframe embed codes from SalesNexus are platform-specific and must be replaced with Mailchimp's form embed code post-migration.

SalesNexus custom fields on Contacts identified by field IDs export via get-all-fields, and each field label, type, and value set maps to a Mailchimp merge field. Mailchimp imposes a 255-character limit on TEXT merge fields, so long-text custom fields from SalesNexus are truncated at 255 characters with a flag in the migration report. Date fields map to Mailchimp DATE merge fields. Number fields map to NUMBER merge fields. Dropdown-style fields map to RADIO or dropdown merge fields with the value set preserved. We create the merge fields on the Mailchimp Audience before importing Members so that field values are populated during the member insert rather than requiring a separate field update pass.

SalesNexus Pipelines (up to 100 on Enterprise) have no Mailchimp equivalent. Mailchimp does not support deal stages, opportunity records, or pipeline tracking. We do not migrate Pipeline records. We deliver a written pipeline inventory documenting pipeline names, stage counts, stage names, and probability defaults so that the customer's admin can decide whether to recreate any pipeline logic in a separate CRM tool if needed.

Pipeline Stages do not migrate. Mailchimp has no stage model. Any historical deal data in SalesNexus pipeline stages is documented as a written record for the customer's admin to evaluate for manual entry into a future CRM tool.

SalesNexus Tasks (open and completed) have no Mailchimp equivalent. Mailchimp does not have a task or activity management layer. We export the task list as a CSV inventory and deliver it to the customer's admin for manual review or import into a separate task management tool if needed.

SalesNexus drip automation sequences are stored server-side and are not accessible via the public API. We can export the list of active contacts enrolled in each sequence and the sequence names, and apply those sequence names as Mailchimp Tags on the corresponding Member records so that enrollment history is preserved as a segmentation label. The trigger logic, delay rules, and conditional branches must be manually rebuilt in Mailchimp Customer Journeys. We provide a sequence audit report listing all active automations and their enrollments for the admin's rebuild reference.

Nexi AI features (AI Email Assistant, AI Meeting Notes, Smart Recommendations) are platform-native and do not expose exported data. Any Nexi-generated content stored as contact notes is exported as plain-text notes, but the AI model state and inference outputs cannot be migrated. We document which Nexi features are active in the source account and deliver a feature inventory so customers understand what will be lost before committing to the migration.

SalesNexus email archival (unlimited on all plans) exports email subject, body, date, direction (sent/received), and related contact. In Mailchimp, we represent this as Member tags (e.g., 'Emails Opened', 'Campaign Sent') and a contact note containing the last five archived email subjects and dates. Full email body archival does not have a native Mailchimp storage equivalent, so we provide a CSV export of all archived emails linked by contact email for the customer's records.