Migrate from SalezShark to Mailchimp

SalezShark Contacts map to Mailchimp Audience members. The primary key is email address; we use Mailchimp's upsert behavior (create if new, update if existing by email) during import. Standard fields (first name, last name, email, phone, address) map directly to Mailchimp's FNAME, LNAME, EMAIL, PHONE, and address merge fields. Status in SalezShark (active/inactive) maps to Mailchimp's subscribed, unsubscribed, or cleaned status — we use the contact's last activity date and email engagement history to set initial status at import time to avoid sending to bounced or disengaged addresses immediately after migration.

SalezShark Account records do not have a direct Mailchimp object equivalent because Mailchimp has no Company or Account concept. We pull Account-level fields (company name, industry, website, annual revenue, employee count) and map them to Mailchimp merge fields (COMPANY, INDUSTRY, WEBSITE) or as tags on the associated Contact record (e.g., tag: Industry:Technology). The customer chooses the strategy during scoping based on how they plan to use segmentation in Mailchimp.

SalezShark Leads map to Mailchimp Audience members tagged with 'Source: Lead' to distinguish them from converted Contacts. We preserve the Lead's conversion score and status in a merge field (LEAD_STATUS, LEAD_SCORE) if those fields exist in SalezShark and the customer requests them. Unconverted Leads that have not yet moved through a sales process are imported as subscribed members so they can enter Mailchimp's automation Journeys immediately.

SalezShark Custom Fields (available on Basic tier and above) map to Mailchimp audience merge fields. Mailchimp caps merge fields at 30 on Essentials and Premium plans, and 80 on Mailchimp Premium. We audit the custom field count during scoping; if the count exceeds Mailchimp's limit, we prioritize fields used in segmentation or automation conditions and flag the remainder as candidate fields to create post-import. Text merge fields in Mailchimp are limited to 255 characters, so long-text fields from SalezShark are truncated at import with a note to the customer.

SalezShark Opportunities and Pipelines have no Mailchimp equivalent. Mailchimp does not track deal stages, deal values, or pipeline velocity. We do not migrate Opportunity records. We deliver a written inventory of every open Opportunity with its stage, value, close date, and owner so the customer's sales team can re-enter these manually in their preferred sales tracking tool (or a new CRM if they adopt one alongside Mailchimp). Closed-won Opportunities may be imported as tags on the related Contact (e.g., 'Customer: Deal $X,000') for historical reference.

SalezShark Tasks (calls, emails, meetings, tasks) do not map to any Mailchimp object. Mailchimp tracks email engagement activity (opens, clicks, bounces, unsubscribes) but not sales call logs, meeting notes, or internal task completion. We do not migrate task history. If the customer needs to preserve activity history for compliance or customer relationship context, we recommend a secondary CRM tool to maintain it separately from Mailchimp's audience data.

SalezShark Workflow Automations (Professional tier, $39/user/month) do not migrate to Mailchimp Customer Journeys because the trigger models differ significantly. SalezShark uses property-triggered workflow rules with CRM-object conditions; Mailchimp uses behavioral triggers (email opens, link clicks, signups, date-based) and Journey builder steps. We export every active SalezShark Workflow as a written specification — trigger conditions, filter logic, and downstream actions — and deliver it to the customer so their marketing team can rebuild equivalents in Mailchimp's automation builder. We do not rebuild automations as part of the migration scope.

SalezShark Campaign membership (Contacts and Leads enrolled in campaigns) migrates as Mailchimp tags on the Audience member record. Campaign names become tag prefixes (e.g., 'Campaign: Q4 Webinar'). Email content, templates, and creative assets do not migrate; we recommend re-creating key templates in Mailchimp using its drag-and-drop builder. Campaign-level reporting metrics (opens, clicks, bounces) do not transfer and are regenerated in Mailchimp post-migration.

SalezShark User records (sales reps, admins) map to Mailchimp account users and audience permissions, not to contact records. We do not migrate User data as contact records. We map SalezShark Owner fields on Contacts and Leads to a SALES_REP merge field in Mailchimp so the contact record carries attribution to the original owner. The customer's Mailchimp account user setup is managed separately through Mailchimp's account settings post-migration.