Migrate from Marketing Creatio to Mailchimp

Marketing Creatio Contacts map to Mailchimp Audience members as the primary record. We extract email address (Email field), first name, last name, phone (if SMS-enabled audience), and any standard address fields. Creatio Contact IDs are preserved in a custom merge field creatio_contact_id__c for reconciliation. Subscription status in Creatio (Email Available For Marketing) maps to Mailchimp's status field: subscribed, unsubscribed, or cleaned. Duplicate email addresses within the Creatio export are flagged and deduplicated before import using the lowest Creatio Contact ID as the keeper.

Marketing Creatio Accounts have no direct Mailchimp equivalent because Mailchimp uses a flat subscriber model rather than a linked Account-Contact structure. We store the Account name, industry, website, type, and annual revenue as custom merge fields on the associated Audience member. The merge field names use MAILCHIMP_COMPATIBLE_FORMAT (all caps, alphanumeric with underscores). This preserves the company context for segmentation and reporting without requiring a separate CRM at the destination.

Creatio Marketing Campaigns migrate as a written reference inventory rather than an automated transfer. We export the campaign name, start and end dates, audience segment association, email template names, and send status. The customer uses this inventory to manually create Mailchimp Regular Campaigns and map the original Creatio segment to Mailchimp Tags, Groups, or Smart Lists. Automation triggers, send schedules, and A/B testing rules do not transfer and require rebuild in Mailchimp's Customer Journeys.

Creatio Segments define Contact groups based on filter conditions against Contact and Account fields. We document each segment's filter logic, field references, and operator types as a written specification. During migration, we assess whether each segment can be recreated as a Mailchimp Tag (applied manually or via API), a Group (which subscribers opt into), or a Smart List (a dynamic saved search). Complex behavioral segments that reference engagement history do not replicate in Mailchimp without rebuilding against Mailchimp's own event model.

Creatio Leads are person records for unqualified prospects. They migrate to the Mailchimp Audience with the same field mapping as Contacts. We preserve the Lead Status value (New, Open, In Progress, Dead) as a custom merge field lead_status__c. Any lead scoring data from Creatio migrates as a custom merge field lead_score__c. Leads with no email address are flagged and held in a reconciliation queue; Mailchimp requires an email address for every subscriber record.

Creatio Tags are flat string labels applied to Contacts and other records. They migrate to Mailchimp Tags as a direct key-value import. We extract all unique tag strings from the Creatio export, deduplicate them, and apply them to the corresponding subscriber records via Mailchimp's Tags API endpoint. Tags preserve segmentation intent from Creatio without requiring a full segment rebuild in Mailchimp.

Creatio Contact custom fields (fields created via the Object type schema in Creatio IDE) require pre-creation as Merge Fields in the Mailchimp Audience before import. We audit the full custom field schema during discovery, map Creatio field types to Mailchimp Merge Field types (text, number, date, phone, address, website), and create the destination merge fields before any subscriber data loads. Complex picklist fields become Mailchimp radio or dropdown merge field types; multi-select picklists become Mailchimp text with pipe-delimited values.

Creatio Opportunities represent sales deals with amount, stage, close date, and owner. Mailchimp does not have an Opportunity object. We flag Opportunities as out-of-scope for the Mailchimp migration and recommend the customer retains Creatio for Opportunity management, uses a separate CRM (Salesforce, HubSpot), or exports Opportunities as a CSV for offline tracking. We document the Opportunity field schema and record count as part of the migration inventory for the customer to decide on downstream handling.

Creatio Cases are customer service or support records. Mailchimp has no case management capability. Cases are flagged as out-of-scope and documented in the migration inventory. If the customer requires case management post-migration, we recommend a dedicated helpdesk platform (Zendesk, Freshdesk) as a separate migration scope.