Migrate from SalesSeek to Mailchimp

SalesSeek People migrate to Mailchimp Members as the primary record mapping. Each Person's email, first name, last name, phone, and title map to the corresponding Mailchimp merge fields (EMAIL, FNAME, LNAME, PHONE, COMPANY). We export the Person record's parent Organization name and industry as TEXT merge fields org_name and org_industry so that company context is preserved on the Member record. The Person's email address serves as the Mailchimp Member dedupe key. Any Person without an email address is flagged during scoping for customer review.

SalesSeek Organizations do not map to a standalone Mailchimp object because Mailchimp uses a flat Audience-Member model. Instead, we attach the Organization name and industry as TEXT merge fields on the related Person record (see above). Additionally, we apply the Organization name as a Tag on each related Member (e.g., tag: 'Legal & General Group PLC') so that segmentation by company is possible via Mailchimp's Tag-based filtering. For accounts with many small Organizations (e.g., one-person companies), we offer a Group-based alternative where Organizations become Mailchimp Groups and Group Categories rather than Tags to reduce tag count.

SalesSeek Tags on People map to Mailchimp Tags directly, preserving the full tag name. We export all distinct tag values and count their frequency. If the tag count exceeds 200 distinct values, we recommend mapping the most frequent tags to Mailchimp Tags and the long-tail to a Group structure to keep the Tag management interface usable. The customer chooses the strategy during scoping based on their segmentation workflow.

SalesSeek dropdown custom fields on People require explicit option mapping to Mailchimp merge field options. We generate a dropdown mapping spreadsheet during scoping listing each SalesSeek field name, its options, and the corresponding Mailchimp merge field name and option labels. Dropdown options must be created in Mailchimp before migration begins because merge field options cannot be set during CSV import. Radio button merge fields in Mailchimp accept only one selected option per Member; if the SalesSeek dropdown allows multiple selections, we recommend a multi-checkbox merge field or Tags instead.

Mailchimp text merge fields are capped at 255 characters. For SalesSeek custom text fields exceeding 255 characters, we evaluate whether the content is segmentable (e.g., industry codes, preference strings) and can be stored as Tags, or whether it should be truncated and the full content stored in an external document linked from the Member record. We flag each long-text field during scoping with a truncation plan. Standard text fields under 255 characters migrate directly to Mailchimp TEXT merge fields.

SalesSeek date custom fields map to Mailchimp date merge fields. Date format is validated during the transform step to ensure compliance with Mailchimp's expected date format (YYYY-MM-DD). Any date fields storing timestamps rather than dates are normalized to the date portion only. Date merge fields in Mailchimp support subscriber-based date filtering in Segments (e.g., send to Members who were created after a certain date).

SalesSeek number custom fields map to Mailchimp number merge fields. Numeric values transfer directly without transformation. Number merge fields in Mailchimp support numeric comparison filtering in Segments (e.g., filter by deal value or score thresholds) and are available on Standard and Premium tiers.

SalesSeek Groups that segment People map to Mailchimp Groups under a Group Category. We create a Group Category in Mailchimp named 'SalesSeek Group' and populate it with the Group names from SalesSeek. Each Member receives a Group membership assignment based on their original Group association in SalesSeek. If a Person belongs to multiple Groups in SalesSeek, we create multiple Group assignments in Mailchimp. Group-based segmentation is preserved for any reporting or routing workflows that depend on it.

SalesSeek Filters are read-only via API and orphaned filters (those without a Group association) are periodically deleted by the platform. During scoping, we identify all active Filters and their Group associations. We export the filter definition (field names, operators, and values) and recreate equivalent Mailchimp Segments using the Mailchimp Segments API. Any Filters that were orphaned before scoping may already be deleted in SalesSeek and are noted as such in the scoping report. The customer reviews and approves all Segment definitions before migration.