Migrate from WayMore to Mailchimp

WayMore Contact records map directly to Mailchimp Members within an Audience. We extract Contact data via CSV export from the WayMore dashboard, mapping email address to the Member email field, name fields to Merge Fields (FNAME, LNAME), and any custom properties to Mailchimp Merge Fields. Phone numbers map to the phone Merge Field. Opt-out status from WayMore exports as a Mailchimp suppression list rather than an active Member status to maintain compliance and protect deliverability at cutover.

WayMore Companies have no native Mailchimp equivalent. Mailchimp does not store account or company records; Members are flat within an Audience. We document every Company name and domain associated with Contacts and provide a CSV mapping of Contact email to Company name that the customer's team can use to create Tags in Mailchimp (e.g., Tag = CompanyName) or populate a custom Merge Field (COMPANY) if they prefer a structured field approach. This is a configuration decision made during scoping.

WayMore Tags applied to Contacts map directly to Mailchimp Tags on the corresponding Member. We extract the full tag list from the Contact export and apply tags to Members during import using Mailchimp's tag management API. Tags used for labeling, segmentation, or filtering preserve their original names. Mailchimp Tags are additive and do not overwrite Member data, so this mapping is low-risk.

WayMore dynamic Segments (defined by rules such as 'contact visited page X more than twice') cannot replicate as dynamic rules in Mailchimp because the two platforms use different behavioral tracking models. We export the current membership list for each WayMore Segment as a static Contact list and create Mailchimp Segments from that list at import time. The segment definition (rules and logic) is documented separately for the customer to evaluate recreating as a Mailchimp Segment with static inclusion or a Tag-based approach. Dynamic updates will not occur automatically post-migration.

WayMore Email Campaign records export via CSV with subject, content summary, sending history, and timestamps. We map campaign metadata to Mailchimp Campaign records including Campaign Title, Subject Line, From Name, and Send Time. The actual email HTML content requires separate handling: WayMore email templates and campaign content must be downloaded manually from the browser interface and re-created in Mailchimp's campaign builder, or the HTML can be pasted into Mailchimp's code editor if the customer prefers to preserve the existing design. Campaign performance statistics (opens, clicks, bounces) do not migrate; Mailchimp tracks these going forward from the send date.

WayMore SMS campaign records and message templates export via CSV. We map SMS campaign names, content, and sending timestamps to Mailchimp SMS Campaign records. Opt-out status per contact preserves to maintain SMS compliance. Note that Mailchimp SMS requires a dedicated phone number and setup through Mailchimp's SMS product; the customer's existing WayMore SMS number will not port and must be provisioned separately in Mailchimp if SMS continues.

WayMore custom properties on Contacts export with the standard Contact CSV. We map each custom field to a Mailchimp Merge Field, preserving the field name where possible (sanitized to Mailchimp's alphanumeric naming convention). Mailchimp Merge Fields are capped at 255 characters for text fields. Any WayMore custom field with values exceeding 255 characters (such as long-form text notes or JSON data) cannot map directly and requires either truncation (with data loss noted) or storage as a separate documented reference outside Mailchimp. Field type conversion (text vs. dropdown vs. date) requires explicit review during scoping because Mailchimp supports a limited set of Merge Field types.

WayMore Automation Workflows define customer journey logic with triggers, conditions, delays, and CRM actions. These do not migrate to Mailchimp Customer Journeys because the two automation models differ structurally. WayMore workflows operate on CRM-enriched contact data and behavioral signals; Mailchimp Customer Journeys are primarily email and audience-triggered. We deliver a written inventory of every active WayMore Workflow including its trigger, conditions, sequence of actions, and estimated Mailchimp Customer Journey equivalent. The customer's team rebuilds these manually in Mailchimp post-migration. Any pending or in-progress workflow executions are lost at cutover.

WayMore push notification campaigns and subscriber device tokens export as records. However, Mailchimp does not support push notifications as a native channel. Device tokens are platform-specific and cannot transfer between platforms. We export the push notification campaign metadata and content as a CSV reference document. If push notifications continue to be required, the customer needs a dedicated push notification platform (OneSignal, Firebase, or a platform-native solution) and must re-integrate the mobile app or website to collect new device tokens. This is documented as a gap with recommended alternatives.