Migrate from Saleshiker to Mailchimp

Saleshiker Contacts map to Mailchimp Audience subscribers. First name, last name, email address, phone number, and lifecycle stage migrate to Mailchimp merge fields (FNAME, LNAME, EMAIL, PHONE, LIFECYCLE). Custom contact properties map to Mailchimp merge fields; we create these in the staging Audience before import. Lifecycle stage values transform from Saleshiker's enum to Mailchimp tag strings so that the original stage data is queryable via segment builder. We deduplicate on email address and flag any contacts with malformed email addresses for admin review before the production import.

Saleshiker Leads map to the same Mailchimp Audience as Contacts. Because Mailchimp has no separate Lead object, unqualified prospects import as regular subscribers and are tagged with a lead_source value from Saleshiker's source field. We preserve the original lead status and any lead score from Saleshiker as merge fields (LEAD_STATUS, LEAD_SCORE) so the marketing team can segment new-from-Saleshiker leads into a nurture sequence immediately after cutover.

Saleshiker Organizations represent company accounts linked to multiple Contacts. Mailchimp has no organization object, so we merge Organization data into the contact record. The organization name becomes a tag on every linked Contact (tag: ORG_[organization_name]), and key org fields (industry, website, employee count) become per-contact merge fields. We run the organization merge as a pre-import step: we build a lookup table from organization_id to org fields, then enrich each Contact record with the resolved org data before inserting into Mailchimp.

Saleshiker's Deals carry pipeline stage, value, expected close date, and owner. Mailchimp has no deal or opportunity object. We preserve deal value as a custom merge field (DEAL_VALUE) on the primary Contact record, and pipeline stage as a tag (STAGE_[stage_name]). Deal associations to Organizations do not carry forward in a joinable form; the customer admin reconstructs deal-to-contact visibility through Mailchimp segments or a linked CRM integration if needed post-migration.

Saleshiker Pipelines with named stages and ordering have no Mailchimp structural equivalent. We export the full pipeline definition (pipeline name, stage list, stage order, stage probabilities) and present it as a structured table in the handoff document. The customer uses this to design Mailchimp segments and Customer Journeys that reflect their sales pipeline stages for marketing attribution purposes.

Saleshiker Products (name, SKU, price, description) do not map to a Mailchimp object. We export the product catalog as a CSV in the handoff package. Products purchased or discussed by a Contact can be tagged on the contact record (PRODUCT_[product_name]) for segmentation purposes, but the product catalog itself is not a managed object in Mailchimp. The customer rebuilds the catalog in Mailchimp if product-aware email automation is needed.

Saleshiker Tasks carry title, due date, status, and assignee. Mailchimp has no task object. We export Tasks as a CSV and tag the related Contact with TASK_PENDING or TASK_COMPLETE based on status at migration time. Any task with a future due date is flagged in the handoff document so the customer can recreate it in their project management tool or inside Mailchimp Customer Journeys if the task is email-reminder-based.

Saleshiker Email Campaigns include template, send date, and basic open/click statistics. We export campaign metadata as a CSV (campaign name, subject, send date, contact count, open rate, click rate). Campaign content itself lives in Saleshiker's template storage and cannot be directly imported into Mailchimp's template format. We document which campaigns are active or scheduled so the customer can rebuild the highest-performing templates in Mailchimp's builder before the next send.

Saleshiker file attachments (stored per Lead, Contact, Organization, or Deal) have no Mailchimp equivalent as contact-level files. We export attachment metadata (file name, related record, upload date) as a CSV. If the attachment is a document that should be referenced in email outreach (e.g., a product sheet), the customer uploads it to Mailchimp Content Studio and links it in the relevant Customer Journey manually.