Migrate from Encharge to Mailchimp

Encharge People map 1:1 to Mailchimp Members within a single target Audience. Standard fields (email, first name, last name, phone) map to the corresponding Mailchimp merge fields. Custom person fields map to Mailchimp merge fields with a 255-character limit enforced; long-text custom fields are truncated at migration time with a warning flag in the reconciliation report. Encharge's opt-in and subscription status maps to Mailchimp Member Status (subscribed, unsubscribed, cleaned, pending).

Encharge Accounts have no direct Mailchimp equivalent because Mailchimp is flat (no company-to-contact relationship). We flatten Account data into the Member record using merge fields: company name maps to COMPANY (a built-in merge field), and additional Account properties (industry, employee count, website) map to custom merge fields we create pre-import. If the customer uses Accounts to model multiple contacts at the same company, we recommend segmenting by company domain post-migration in Mailchimp instead.

Encharge Tags are flat string labels applied to People and migrate directly to Mailchimp Tags on the corresponding Member. We export the full tag history per Person (a Person can have multiple tags) and apply all tags during Member import. Mailchimp Tags are per-Audience, so if the customer uses multiple Encharge workspaces or segregated contact pools, we recommend a separate Mailchimp Audience per pool to preserve tag scoping.

Encharge Segments are dynamic filter-based groups of People with conditions on contact properties and behavioral events. We export the full segment definition (filter rules, operator logic, and combinators) during scoping and reconstruct it in Mailchimp using its Segment builder. Because Encharge behavioral events (page views, custom product events) do not exist in Mailchimp, segment conditions that rely on behavioral criteria are mapped to the closest Mailchimp equivalent (campaign engagement, tag presence, or merge field values) and documented as adjusted scope.

Encharge Email Templates store HTML with subject lines, sender names, and metadata. We export templates as HTML files preserving inline styles, embedded images (as hosted URLs), and merge tag placeholders. Templates are imported into Mailchimp's template library where the customer reviews layout rendering before activating. Mailchimp's template content blocks may require manual adjustment if Encharge templates use non-standard block structures.

Encharge Custom Objects (Deals, Orders, Invoices, or any customer-defined entity) have no Mailchimp equivalent. We migrate Custom Object records as contact-level data: each related Person gets the Custom Object fields written as custom merge fields on their Member record. The relationship structure between Custom Objects is not preserved in Mailchimp. We deliver a written schema map of every Custom Object and its fields so the customer's admin can evaluate alternative storage (Google Sheets, Airtable, or a separate CRM) if the relationships matter.

Encharge Flows store automation logic as JSON configuration referencing triggers, conditions, and downstream actions. There is no export endpoint. We document the full Flow tree during scoping: trigger type, each conditional branch with its conditions and operators, wait-step durations, and downstream actions. This documentation is delivered as a rebuild checklist for the customer's team to recreate in Mailchimp's Customer Journey builder. Flows that use Encharge-specific triggers (Stripe events, Intercom events, product behavioral events) are flagged as requiring alternative trigger setup in Mailchimp.

Encharge Forms capture new People with field definitions and webhook configurations. We export form field schemas and webhook URLs. Form URLs and embed codes must be updated in the destination system post-migration. Mailchimp signup forms (embedded, hosted, or popup) replace Encharge forms; we provide a field-mapping table from each Encharge form field to its Mailchimp equivalent so the customer can set up the replacement form without losing data collection logic.

Encharge Activity records track behavioral events (email opens, page views, custom events) against People. Mailchimp does not have a behavioral activity log; it tracks campaign-level engagement (opens, clicks, unsubscribes, bounces) per Member. We migrate the most recent 90 days of Encharge Activity as custom merge fields on the Member record (last_open_date, last_click_date, last_page_view) to preserve some behavioral context. Full activity history cannot be migrated and is documented as out-of-scope.