Migrate from Sales Snap to Mailchimp

Sales Snap Contact records map to Mailchimp Audience members. We use email address as the primary dedupe key and map standard fields (First Name, Last Name, Phone) to Mailchimp merge fields (FNAME, LNAME, PHONE). The Sales Snap lifecycle stage migrates as a Mailchimp tag (e.g., tag: LifecycleStage-Lead) or as a custom merge field depending on the customer's segmentation strategy. All visible custom fields from the Sales Snap CSV export map to Mailchimp custom merge fields, created in the destination Audience before import.

Sales Snap Company records are exported per-contact and may duplicate across multiple contacts. We deduplicate on company name during import preparation, then map the resolved company name to a Mailchimp merge field (COMPANY). Mailchimp has no native company or account object, so the entire company affiliation collapses into a single-text merge field on the subscriber record. We flag the deduplication step in the project plan and note that if company-level reporting is required post-migration, it must be handled through Mailchimp tags, segments, or a third-party integration.

Sales Snap sequences contain email templates, step order, timing rules, and personalization tokens. Mailchimp Customer Journey Builder uses a trigger-and-action model that is structurally different. We do not migrate sequences as automation code. We export sequence structure (step order, delay days, template content, personalization token names) from Sales Snap CSVs, document it in a sequence inventory, and deliver it to the customer's admin for rebuild in Customer Journey Builder. Email templates themselves are documented as HTML content blocks for re-creation in Mailchimp's template editor.

Sales Snap sequence tasks (follow-up reminders, call tasks, meeting tasks) have no equivalent in Mailchimp. Mailchimp is an email marketing platform; it does not maintain a task management object. We flag sequence-generated tasks as out-of-scope and document their existence in the automation inventory. Customers requiring task management post-migration should configure a separate project management or CRM tool.

Sales Snap engagement history (opens, clicks, replies, call outcomes) per contact migrates as Mailchimp activity tags on the audience member (e.g., tag: Engaged-Opened, tag: Engaged-Clicked, tag: Engaged-Replied). Because Mailchimp tracks opens and clicks at the campaign level per subscriber rather than as a longitudinal log, we also produce a separate CSV audit report with the full engagement timeline by contact for customers who need the historical record. The report is delivered alongside the import and can be imported into a connected BI tool if required.

Sales Snap call engagements (with disposition, duration, and outcome) have no Mailchimp equivalent. Mailchimp does not log phone calls as part of its subscriber activity model. We include call engagement data in the separate audit CSV report with contact email as the key, call timestamp, duration (seconds), and disposition. This report is delivered to the customer's admin for import into a separate CRM or call logging system if needed.

Sales Snap custom fields visible in the CSV export map to Mailchimp audience merge fields. We pre-create all merge fields in the Mailchimp audience before import using the Mailchimp Marketing API. Field types are inferred from the CSV data: date strings map to date-type merge fields; numeric strings map to number-type merge fields; text strings map to text-type merge fields. Picklist and multi-select fields map to text merge fields or tag-based segmentation in Mailchimp depending on cardinality. Any custom field not visible in the Sales Snap export UI is flagged as a discovery gap before import.

Sales Snap Owners (sales reps) referenced on contact records map to Mailchimp tags on the audience member (e.g., tag: Owner-Sarah) or are excluded if the customer does not require rep-level segmentation in Mailchimp. Mailchimp does not have a native user or owner object. We document the owner mapping in the project plan and let the customer decide whether to carry owner attribution as tags or drop it. Tags are created only for owners with more than 10 contacts to avoid tag bloat in small teams.