Migrate from Resulticks to Mailchimp

Resulticks Contact records map 1:1 to Mailchimp Subscribers within a designated Audience. We map standard fields (email, first name, last name, phone number if present) directly. Custom contact properties in Resulticks (which vary per account configuration) are inspected during scoping, and equivalent Merge Fields are created in Mailchimp before import. Resulticks lifecycle stage property maps to a custom Merge Field if the customer requires it for segmentation; Mailchimp does not have a native lifecycle model so it is preserved as a tag or custom field rather than a native object attribute.

Resulticks audience definitions are based on Contact attributes and event conditions. We translate each Resulticks audience into two Mailchimp objects: a corresponding Tag for every contact that matched the audience definition (preserving individual tag membership), and a Mailchimp Segment with equivalent filter logic (using Mailchimp's condition builder) so that the segment is live and updates automatically as new subscribers meet the criteria. The split preserves both the static snapshot and the dynamic behavior of the original segment.

Resulticks campaign metadata (name, status, channel assignment, scheduling dates, sender identity) migrates as campaign records in Mailchimp. The campaign body content, email HTML, images, and template blocks do not export from Resulticks via API and require separate content extraction or rebuild. We flag every campaign that had a body for manual content handoff to the customer's email team.

Contact-level Tags in Resulticks migrate directly to Mailchimp Tags on the corresponding Subscriber record. Tag counts and distribution are preserved at the individual subscriber level. Mailchimp Tags are applied during the Subscriber import phase via batch operations.

Resulticks platform users do not map to Mailchimp Users in a 1:1 sense because Mailchimp's permission model is audience-scoped and role-based (Account User, Audience Manager, Author, Viewer). We map Resulticks users to Mailchimp Account Users with the appropriate role assignment based on their access level in Resulticks. If the customer uses Resulticks user permissions to control campaign access, we document the equivalent Mailchimp role configuration during the migration handoff.

Resulticks behavioral events (page views, email opens, purchase events, custom track events) represent the most complex migration object. Mailchimp tracks opens, clicks, and e-commerce activity per subscriber but does not expose a raw event log in the same way Resulticks does. We migrate a configurable event window (typically the last 90 days) and normalize events into Mailchimp's activity model: open events become Mailchimp opens, click events become Mailchimp clicks, and purchase events are created as Mailchimp e-commerce order records if the customer has Mailchimp Commerce enabled. Full historical event timelines beyond the configured window are documented in a written event schema export for the customer to load into a separate analytics tool if needed.

Resulticks Journey orchestrations (branching conditions, wait steps, AI-driven decision nodes, multi-channel node sequences) are not exportable via documented APIs and require manual rebuild in Mailchimp Customer Journey Builder. We photograph and document every Journey during discovery, creating a written architecture document with node-by-node descriptions, wait durations, branch conditions, and channel assignments. The customer's email team uses this document to rebuild flows in Mailchimp; we do not rebuild Journey logic as code. Content within Journey nodes (copy, images, offer codes) requires separate export from Resulticks.

Resulticks custom contact properties vary by account and may include legacy field types, multi-select values, or date-derived computed fields. We inspect the field schema during scoping, map each custom property to an equivalent Mailchimp Merge Field (using the appropriate type: text, number, date, address, phone, or dropdown), and create the Merge Field in the destination Audience before import. Multi-select values in Resulticks are mapped to Mailchimp tags or to a pipe-delimited text Merge Field depending on the customer's preference for segmentation usability.