Migrate from Sentia to Mailchimp

Sentia Contact records map directly to Mailchimp Subscribers in a target Audience. Email address is the dedupe key; duplicates are handled per Mailchimp's merge policy (oldest record wins or contact is updated in place depending on the customer's preference). First name, last name, and phone number map to FNAME, LNAME, and PHONE merge fields. We set the Subscriber status to subscribed if no suppression record exists, and we flag any Contact with a bounced or unsubscribed status in Sentia for suppression-list import before the main contact batch.

Sentia Company names map to the COMPANY merge field on each Subscriber. If the customer uses Sentia Companies to segment by organization (e.g., B2B accounts that receive different campaigns), we create Mailchimp Segments based on COMPANY merge field matching rather than a separate object. Company-to-Contact association is preserved by grouping subscribers with matching COMPANY values into a segment; there is no cross-record link object in Mailchimp equivalent to a CRM Company record.

Sentia Lead records (a distinct object from Contact in Sentia) merge into the Mailchimp Subscriber model. The lead source property (e.g., website form, referral, event) migrates as a custom merge field LSOURCE on the Subscriber. Lead status (new, contacted, qualified) does not have a direct Mailchimp equivalent; we store the status value in a STATUS_CRM merge field and recommend the customer use Mailchimp Tags or Segments to track progression if needed.

Sentia Deals with pipeline stages and monetary values have no equivalent object in Mailchimp. We export Deal records as a CSV including deal name, associated Contact or Company, pipeline stage, value, and close date. The customer uses this export to manually recreate campaign triggers, tags, or notes in Mailchimp if deal milestones need to drive email sequences. We do not create Deals in Mailchimp because no deal object exists.

Sentia pipeline stages (e.g., Prospect, Qualified, Proposal Sent, Closed Won) are custom per organization and do not map to any Mailchimp structure. We export the stage names, probabilities, and order as part of the written pipeline inventory. If the customer wants stage-based email triggers (e.g., send a case study when a deal enters the Qualified stage), they rebuild these as Mailchimp Customer Journeys with tag-based triggers post-migration.

Sentia custom Contact-level properties (available on Starter at $25/user and Ultimate at $30/user) map to Mailchimp merge fields. Mailchimp supports text, number, date, phone, address, and URL merge field types. We validate field type compatibility during scoping and flag any Sentia field with an unsupported type (e.g., complex object references) for manual handling. Merge fields must be created in the Mailchimp Audience before import; we create the field schema during the pre-migration setup phase.

Sentia Tags on Contacts migrate to Mailchimp Tags on the Subscriber record. Tags are preserved as-is and do not require schema configuration; they are applied as array values during import. If a Sentia tag maps to a segmentation concept (e.g., VIP, churned, product-use), we recommend the customer also create a corresponding Mailchimp Segment using that tag as the criteria for reusable audience filtering.

Sentia engagement records (calls, emails, meetings, tasks) attached to Contacts do not replay into Mailchimp. Mailchimp tracks future campaign engagement (opens, clicks, unsubscribes) per subscriber but does not accept historical call or meeting records from an external CRM. We export a written activity log per Contact as a CSV and advise the customer to attach this log to the Contact record in an external system or as a Mailchimp note on the Subscriber if the note feature is enabled on their plan.

Sentia Users who own Contacts and Deals have no direct Mailchimp equivalent because Mailchimp is not a record-assignment CRM. We do not migrate user assignments. If the customer needs to track which sales rep is associated with a contact, we map the Sentia owner email to a custom merge field OWNER on the Subscriber. Mailchimp's Standard and Premium plans support multiple user logins but no record-level owner assignment.