Migrate from iPresso to Mailchimp

iPresso Contacts map directly to Mailchimp audience contacts. Standard profile fields (email, first name, last name, phone) migrate by field name match. Custom contact properties require field-level mapping to Mailchimp Merge Fields, including field type alignment (date fields to Mailchimp Date type, number fields to Number type). iPresso lifecycle stages migrate as a custom text or number merge field so the customer retains segmentation logic tied to contact maturity.

iPresso Company records have no direct Mailchimp equivalent. We flatten company attributes onto each related Contact by mapping the Company name to a merge field (Company_Name) and applying the company name as a Mailchimp Tag for every contact linked to that company. This preserves company context for segmentation without creating a separate company object. Industry, employee count, and revenue tier from iPresso Company custom fields map to additional merge fields or tags depending on the customer's segmentation needs.

iPresso campaigns migrate to Mailchimp campaigns as records with audience assignment, subject line, from name, and send date preserved. Campaign performance metrics (open rate, click rate, bounce rate) migrate as a written reference table or as custom merge fields on the contacts who received each campaign so historical performance is queryable in Mailchimp reporting. Campaign audience segments from iPresso do not migrate as active segments; they are documented as conditions for the customer to rebuild as Mailchimp segments post-migration.

iPresso email template HTML content migrates directly to Mailchimp templates. Dynamic personalization tokens referencing iPresso contact properties require field reference updates to use Mailchimp merge tag syntax (FNAME, LNAME, and custom merge field names). We flag every template with dynamic content and provide a token mapping table so the customer's email developer can update template code before activation.

iPresso contact segmentation tags migrate directly as Mailchimp tags. Tag names and memberships transfer as straightforward label associations without complex transformation. We apply all tags to the corresponding contacts during the contact import phase so segmentation is active from day one in Mailchimp.

iPresso landing page content and form field configurations do not export as reusable templates. We extract landing page HTML where accessible and document the page structure, form fields, and submit actions as a written reference for the customer to reconstruct using Mailchimp's landing page builder or a third-party page builder. Form field names and types are mapped in a field inventory so form integrations can be reconnected post-rebuild.

iPresso multi-step workflows with branching, conditions, time delays, and CRM actions do not migrate as automation code because Mailchimp's automation flow model differs structurally. We deliver a written workflow inventory listing every active iPresso workflow with its trigger, conditions, actions, and recommended Mailchimp automation equivalent (Customer Journey, Abandoned Cart, Welcome Series, or Post-Purchase flow). The customer's team uses this inventory to rebuild automations in Mailchimp's automation builder.

iPresso behavioral event history (page views, form submissions, product interactions, channel events) has no native Mailchimp equivalent since Mailchimp does not store structured event records. We transform key behavioral signals into Mailchimp tags and custom fields on each contact record. For example, event names become tags (viewed_pricing_page, abandoned_cart) and recency becomes a custom date field. This preserves behavioral context for segmentation without requiring a data warehouse.