Migrate from BenchmarkONE to Mailchimp

BenchmarkONE Contacts migrate directly to Mailchimp Contacts within a single primary Audience. The First Name, Last Name, Email, Phone, Address, and Title fields map 1:1 to Mailchimp's standard contact fields. Temperature (lead scoring) and Lead Source migrate as custom merge fields tagged as text. The Assigned Sales Rep migrates as a text merge field representing the owner name. Contact Status (Active, Inactive, Unsubscribed) is evaluated at migration time: active and inactive contacts import as Mailchimp Contacts; unsubscribed contacts are diverted to the suppression list import in a separate phase to preserve deliverability.

Mailchimp has no standalone Company or Account object; company data must live as contact-level merge fields. We extract the Company Name from BenchmarkONE and map it to a text merge field (COMPANY_NAME or BUSINESS_NAME) on the Contact. The Company Website URL maps to a separate text merge field. Any contacts sharing the same company in BenchmarkONE receive the same company merge field values in Mailchimp, but Mailchimp does not preserve the parent-child relationship structure. We flag this flattening during scoping so the customer can decide whether to group contacts by company via Mailchimp Tags instead.

BenchmarkONE Tags are free-form segmentation labels applied to contacts. Mailchimp Tags serve the same function: labels applied to individual contacts for audience segmentation. Multiple BenchmarkONE tags per contact (stored as comma-separated in the CSV export) split and map directly to multiple Mailchimp Tags. This is a direct 1:1 transfer with no data loss. During scoping we confirm whether tags are used for content classification (where Mailchimp Topics may be a better long-term replacement) or contact segmentation (native Tags fit directly).

BenchmarkONE custom fields on Contacts and Companies map to Mailchimp merge fields, which support text, number, date, phone, address, dropdown, and checkbox types. We audit the source schema during scoping and type-match each field: date fields become Mailchimp date merge fields; dropdowns become option merge fields with the same value set; checkboxes become birthday or other boolean-style fields where applicable. Long text fields in BenchmarkONE may exceed Mailchimp's 255-character merge field limit and require truncation with a note in the field mapping. We validate merge field definitions in the destination Audience before data load.

BenchmarkONE Deals have no equivalent in Mailchimp's data model. Mailchimp does not support opportunity records, pipeline stages, deal values, or deal owners. We export all active Deals as a structured CSV during migration, including Deal Name, Stage, Value, Close Date, Associated Contact Name, and Owner. This CSV is handed to the customer as a Deal reference document. If the customer requires ongoing deal tracking post-migration, we recommend Pipedrive, HubSpot, or a spreadsheet linked to Mailchimp contacts as a replacement CRM layer.

BenchmarkONE Tasks (linked to contacts, companies, or deals) have no equivalent in Mailchimp. We export active Tasks as a CSV including Task Subject, Due Date, Status, Associated Contact Name, and Owner. Mailchimp Notes attached to contacts are an optional partial replacement for task descriptions, but Notes do not support due dates or assignee tracking. We document this gap in the migration scope and recommend the customer configure a task management tool (Asana, Trello, or a CRM with native tasks) to replace BenchmarkONE's task layer.

BenchmarkONE email campaign metadata (Campaign Name, Send Date, Audience size, Template used) and aggregate performance stats (Total Sent, Opens, Clicks, Bounces, Unsubscribes) migrate to Mailchimp's campaign report data model. We map aggregate open rate, click rate, and bounce rate to Mailchimp reporting fields. Individual email event logs (per-subscriber open and click timestamps) are not supported by Mailchimp's standard import model; these are considered non-migratable and are documented as a gap in the scope.

BenchmarkONE Automations triggered by form submissions, link clicks, website visits, tag changes, or purchases have no direct Mailchimp equivalent because the trigger event models differ structurally. We extract every active BenchmarkONE automation's trigger logic, conditions, and actions and deliver them as a written Customer Journey rebuild reference document. Each automation maps to a Mailchimp Customer Journey trigger type (Campaign Sent, Date-Based, Segment Trigger, API Trigger) where possible. The customer's Mailchimp admin rebuilds the sequences in the Customer Journey builder; this is manual work outside the data migration scope.

BenchmarkONE stores social profile URLs (LinkedIn, Twitter/X, Facebook) on the contact record. Mailchimp supports social profile share and follow icons via merge fields or as custom text fields storing URL values. We map each social network URL to a text merge field (LINKEDIN_URL, TWITTER_URL, FACEBOOK_URL) on the contact. These appear as clickable icons on the Mailchimp contact profile. Mailchimp's social integration features are scoped to platform-native share actions, not inbound social data collection.

BenchmarkONE unlimited user seats mean multiple Sales Reps may be assigned as owners to contacts, companies, and deals. Mailchimp does not have a native User or team member assignment model per contact. We extract all Sales Rep names referenced in owner fields and map them as a text merge field (SALES_REP) on each contact record. This preserves the assignment context as a readable field. If the customer requires multi-user Mailchimp access for campaign management, we note that Mailchimp's Per User pricing applies separately from the contact-based plan.