Migrate from Creatio to Mailchimp

Creatio Contact maps to Mailchimp audience Contact. Email address is the primary key and dedupe identifier. We map standard fields (first name, last name, phone) to Mailchimp merge fields (FNAME, LNAME, PHONE). Creatio lifecycle stage becomes a custom contact property (LIFECYCLESTAGE) stored as a text merge field. Any Creatio calculated fields are flagged during scoping and skipped for static value migration since they compute at display time. Owner assignment from Creatio (a User lookup) is preserved as an OWNER merge field or as a tag for segmentation purposes.

Creatio Account (Company) data maps to Mailchimp merge fields on the Contact record. The Account Name, Industry, Website, and Billing Address become CONTACT_COMPANY, INDUSTRY, WEBSITE, and ADDRESS merge fields in Mailchimp. Where Accounts are used to group Contacts (e.g., all Contacts under one Account), we can create Mailchimp Tags from the Account Name for segmentation rather than storing the Account as a separate entity, since Mailchimp has no native company table.

Creatio Leads that have not been converted to Contacts before migration are imported as Mailchimp audience Contacts with a SOURCE tag set to Lead. We preserve lead status and source attribution as merge fields. Any lead score from Creatio becomes a numeric SCORE merge field. Unqualified leads that would have been converted to Contacts in Creatio are imported as Contacts to avoid creating orphaned records in Mailchimp.

Creatio custom fields on Contact (beyond the base schema fields) are mapped to Mailchimp merge fields. Mailchimp supports up to 60 merge fields per audience. We audit the full custom field list during discovery and flag any fields exceeding this limit, resolving via tag consolidation or by removing fields with no active data. Field type mapping: text to text, number to number, date to date, boolean to radio, and multi-select picklist to comma-separated text or Mailchimp interest group if the list is short.

Creatio does not have a native tag model equivalent to Mailchimp, but teams commonly add tags to Contacts manually or via integrations. We export any tagged Contacts from Creatio and recreate the tag structure in Mailchimp. Tags used for segmenting audiences (e.g., product interest, event attendance, persona) become Mailchimp Tags applied to the contact record. If the customer used Creatio Categories for contact classification, we map those to Tags with a category prefix for clarity.

Email subscription status in Creatio (Active, Inactive, Unsubscribed) maps directly to Mailchimp contact status (subscribed, unsubscribed, cleaned). We extract Creatio unsubscribed contacts first and import them as suppressed contacts in Mailchimp before importing active subscribers, preventing accidental re-subscription. Any bounced email addresses from Creatio are imported as cleaned contacts. GDPR consent fields are mapped to Mailchimp's GDPR consent tags per EU requirements.

Creatio engagement history (calls, emails, meetings, tasks) cannot map to native Mailchimp objects because Mailchimp does not have an activity timeline per contact. We consolidate engagement summary data (last contact date, total engagement count, engagement score) as custom contact properties and write a structured note record per contact noting the most recent activities as a reference log. Historical activities older than 90 days are flagged as excluded and documented in the migration report. Mailchimp's API does not support backdating engagement history beyond this window.

Creatio Opportunities, Cases, and Products have no equivalent object in Mailchimp. These records are excluded from the migration scope. We deliver a written inventory of all open Opportunities and Cases with their current stage, amount, owner, and last-modified date in a structured CSV export so the customer's admin can reference or re-enter this data in their new CRM if applicable. This is not a data loss event but a platform capability mismatch that must be addressed in post-migration planning.