Migrate from User.com to Mailchimp

User.com Contacts map directly to Mailchimp Members within a target Audience. The primary email address serves as the dedupe key; contacts without an email address cannot migrate as Members and are flagged separately. Standard fields (first name, last name, phone, city, country) map to Mailchimp merge fields FNAME, LNAME, PHONE, CITY, COUNTRY. Any contact without a valid email is held in a reconciliation report for the customer to resolve before import.

User.com Companies have no direct Mailchimp equivalent. We map company_name, domain, and industry to Mailchimp merge fields (COMPANY, INDUSTRY, WEBSITE) stored on the Member record. For multi-company relationships, we use Tags on the Member to encode company affiliation, since Mailchimp's data model does not support a separate Company object. The customer chooses during scoping whether to use merge fields or tags for company data.

User.com custom properties on Contact map to Mailchimp merge fields. Mailchimp caps text merge fields at 255 characters; any User.com custom property exceeding this length is truncated with a note in the reconciliation report. Date fields map to Mailchimp Date field type. Choice fields from User.com map to Mailchimp dropdown or radio merge fields. Boolean fields from User.com (stored as f/t post-2023 export format change) normalize to Y/N or yes/no strings. Standard accounts are limited to 30 merge fields; Premium supports up to 80.

Tags on User.com Contacts migrate directly to Mailchimp Tags on the corresponding Member record. Tags are preserved as-is with no transformation, as both platforms treat tags as flat string labels. Multi-value tag strings from User.com (pipe-separated or comma-separated depending on export version) are split and assigned individually to Mailchimp. Tag cleanup recommendations are included in the migration scope for any tags that appear to be system-generated or empty.

User.com Segments are dynamic groups based on contact attributes and behavioral conditions. We export the full segment definition including all filter conditions, operators, and logic at migration time and deliver it as a written specification. Mailchimp Segments must be recreated manually using Mailchimp's segment builder. We provide the segment names, conditions, and recommended Mailchimp equivalents as a reference document for the customer's admin.

User.com Deals have no Mailchimp equivalent. Mailchimp is an email marketing platform without a sales pipeline or opportunity management module. We do not migrate Deals. We deliver a written inventory of all active Deals including stage, value, owner, and associated contact as a reference document the customer can use to import into a dedicated CRM post-Migration if needed.

User.com Events (calendar and activity events) do not have a Mailchimp equivalent. Mailchimp does not maintain a calendar or event management module. We do not migrate Events. The customer should export event history to a BI tool or spreadsheet for archival before migration begins.

User.com Activities (call logs, chat transcripts, push notification history) do not migrate to Mailchimp. Mailchimp tracks campaign-level engagement (opens, clicks, unsubscribes) but not individual activity records. Chat history and call logs should be exported from User.com before migration and archived separately. Push notification subscriber status may be preserved as a Tag on the Member record if the customer wants to track push opt-in separately.

User.com automation workflows are not accessible via documented CSV or API export. We do not migrate automation logic. We deliver a written inventory of every active workflow including trigger type, conditions, delay actions, and CRM/email outputs as a specification for rebuilding in Mailchimp Customer Journeys. We recommend capturing screen recordings of active automations before migration begins.

User.com email templates and campaign performance records (open rates, click rates, send history) are not accessible via documented export endpoints. We do not migrate templates or campaign history. The customer should document template names, layouts, and purposes before migration and recreate them in Mailchimp's template editor. Campaign performance data should be exported to a BI tool for historical reference.