Migrate from Sellsation CRM to Mailchimp

Sellsation Customers map to Mailchimp Audiences. The Customer company name becomes the FNAME or COMPANY merge field depending on whether the contact is a primary or billing contact. We create one Mailchimp Audience per Sellsation Customer where multiple Contact Persons share the same company, or one combined Audience if Sellsation has no parent Customer relationship. The customer chooses the audience naming convention during scoping.

Sellsation Contact Persons map directly to Mailchimp contacts within the destination Audience. Standard fields migrate as merge fields: first name (FNAME), last name (LNAME), email address (EMAIL), phone number (PHONE), and postal address fields (ADDRESS, CITY, STATE, ZIP, COUNTRY). We deduplicate by email address during the transform phase to prevent duplicate Mailchimp contacts from Sellsation records with shared email addresses.

Sellsation Sales Projects (deal/opportunity records with pipeline stages, deal values, and phase change history) have no equivalent in Mailchimp. Mailchimp does not support pipeline management, deal stages, or deal value tracking. We flag each Sales Project as a non-migratable record, export the underlying data (stage name, value, linked Contact Person) to a CSV delivered alongside the contact migration so the customer's team can use it as a reference for rebuilding pipeline context in a destination CRM if needed.

Sellsation logs calls, notes, and tasks as individual activity records linked to Contact Persons. Mailchimp tracks opens, clicks, unsubscribes, and bounce events as campaign-level engagement metrics but does not store individual call logs, notes, or tasks on contacts. We export activity history as a time-stamped CSV ordered by Contact Person so the customer's team has the full engagement context available for manual entry or import into a destination CRM.

Sellsation appointments with date, time, duration, and attendee lists do not map to any Mailchimp object. Mailchimp has no calendar or scheduling feature. We export appointment data as a CSV with Contact Person reference, date, time, and notes, and flag this for the customer's team to handle via a separate scheduling tool or CRM.

Sellsation multi-level campaigns (combining emails, letters, conditional stage movements, and automated task creation) require manual reconstruction in Mailchimp Customer Journeys. We deliver a written campaign inventory document listing each Sellsation campaign's trigger conditions, enrolled audiences, email content, conditional branches, and automated actions. The customer's marketing team uses this inventory to rebuild campaigns as Mailchimp Customer Journeys, which use a different trigger-and-delay model from Sellsation's stage-based campaign logic.

Sellsation custom fields on Contact Persons migrate to Mailchimp merge fields if they are single-value text, date, or numeric fields. Multi-select or picklist custom fields migrate as Mailchimp tags applied to the contact record. We enumerate all Sellsation custom fields during scoping, classify each by data type and cardinality, and produce a mapping table that the customer's Mailchimp admin uses to pre-create merge fields before the contact import runs.

Sellsation geo map and heatmap data is stored as internal map state rather than standard geographic coordinates. We export any location or address data linked to Sales Projects or Contact Persons as standard address merge fields (ADDRESS, CITY, STATE, ZIP, COUNTRY) in Mailchimp. The visual heatmap and territory visualization does not migrate; we flag this loss in the scope document and note that address-based segmentation in Mailchimp can partially replicate regional targeting.