Migrate from Inflection.io to Mailchimp

Inflection Contacts map to Mailchimp Subscribers via email address as the primary key. Standard properties (email, first_name, last_name, phone, company) map to Mailchimp's native merge fields (EMAIL, FNAME, LNAME, PHONE, COMPANY). Custom Person fields (text, numeric, date/time, boolean) map to Mailchimp merge fields that we create during setup using the original field names. We preserve PQL scores, lifecycle stage flags, and any behavioral property as custom merge fields at migration time, though these are static values and not updated by Mailchimp post-migration without manual intervention.

Inflection Account records have no direct Mailchimp equivalent because Mailchimp does not model companies as first-class objects. We implement a two-part strategy: (1) we map Account.Name and Account.website into subscriber merge fields (COMPANY, WEB_URL) so that company context is attached to each subscriber record, and (2) we create a per-Account tag in Mailchimp and apply it to all subscribers belonging to that account, enabling filtered views by account. This approach requires the account-to-subscriber relationship to be resolved during scoping by joining on a shared field (email domain or explicit account_id field in the Inflection Contact record).

All Inflection custom Person fields (text, numeric, date/time, boolean, and custom tokens) map to Mailchimp merge fields with equivalent types. Text fields become text merge fields; numeric fields become number merge fields; date fields become date merge fields; boolean fields become radio or dropdown merge fields. We extract the full custom field schema from Inflection during discovery, create the corresponding merge field definitions in each target Mailchimp audience before import, and map values field-by-field during the contact export. Note that Mailchimp merge fields are flat per-subscriber attributes and do not support the nested or relational data that Inflection's custom field tokens allow.

Inflection contact-level tags and segment membership flags map directly to Mailchimp Tags. Tag vocabulary is preserved as-is, and we apply the same tag counts to each subscriber during import. Tags that represent Journey membership (e.g., 'in-onboarding-journey') become informational tags in Mailchimp; they do not trigger automations without manual Customer Journey rebuild. Tags that represent behavioral segments (e.g., 'pql-score-gt-80') are preserved as labels only.

Inflection Segments are audience definitions built on contact properties, product events, and behavioral signals with rule-based logic (AND/OR conditions, event frequency, time windows). We export the full segment definition including rule structure, condition operators, and membership counts for each segment. Mailchimp supports similar rule-based segments with conditions on merge fields, tags, and engagement activity, but the condition syntax differs. We deliver a written segment translation guide that maps each Inflection segment rule to its Mailchimp equivalent, including any conditions that cannot be replicated in Mailchimp due to platform limitations (e.g., product event frequency conditions, account-level conditions, PQL score thresholds). Segment membership does not migrate as static subscriber lists; the customer's admin creates the Mailchimp segments post-migration using the translation guide.

Inflection native forms and integrated third-party forms (Formstack, Webflow, HubSpot, Marketo) are supported for export. We migrate form submissions as subscriber records with all submitted field values mapped to Mailchimp merge fields. Form field mappings transfer as merge field assignments. Form submission timestamps migrate as a custom date merge field. Note that web tracking attribution from Inflection forms (tracking the campaign source of each form submission) does not carry over to Mailchimp unless the customer recreates the UTM tracking infrastructure in Mailchimp's form settings.

Inflection email engagement records (sends, opens, clicks) migrate as a custom merge field set on each subscriber: last_email_sent_date, last_email_open_date, last_email_click_date, total_emails_opened, total_emails_clicked. These are aggregate values captured at migration time. Full email campaign history (individual send records, per-campaign engagement) is documented in a written campaign inventory for the customer's admin to reference but cannot be loaded into Mailchimp as operational data because Mailchimp's campaign history is platform-native and not importable. SMS and phone call engagements from Inflection have no Mailchimp equivalent and are documented separately.

Inflection's live product event stream (billions of behavioral events, usage signals, PQL calculations) has no Mailchimp equivalent. Mailchimp tracks email engagement and e-commerce purchase activity, not in-product behavioral events. We capture the product event schema during discovery as a reference document, preserve any product-derived scores (PQL scores, engagement scores) as custom merge fields on the subscriber record, and deliver a written product event inventory with recommendations for rebuilding behavioral triggers in Mailchimp's Customer Journeys using e-commerce purchase data or re-integrating via a CDP like Segment. This is a material data loss point for PLG companies and is disclosed during scoping.