Migrate from Loyalistic to Mailchimp

Segment logic does not migrate as rules

Loyalistic segments are dynamic, rule-based groups computed from contact properties and engagement events at query time. Mailchimp segments are static conditions evaluated at send time against the current subscriber state. The segment membership list migrates as a static export of email addresses assigned to Mailchimp groups or tag-based segments. Any segment whose rule relied on real-time behavioral criteria (opened in last N days, clicked any link in last N days, had a property change since last send) cannot be preserved as logic and must be rebuilt as Mailchimp Customer Journeys or recurring segments post-migration. We document every segment rule in the migration scope deliverable with a recommended Mailchimp equivalent.

Contact consent status requires explicit separation

Mailchimp requires explicit opt-in and enforces deliverability standards that penalize platforms with softer permission models. We classify Loyalistic contacts into subscribed, unsubscribed, and cleaned categories before import. Subscribed contacts import as subscribed. Contacts with a Loyalistic unsubscribe action or a bounced status import as unsubscribed (suppression list) to protect sender reputation. Contacts with no activity history or unclear consent provenance are flagged as cleaned and may require a re-confirmation campaign before sending. Skipping this classification step can trigger bounce spikes that damage domain reputation and deliverability scores.

Custom field type mapping can reject records

Loyalistic custom properties have flexible types. Mailchimp merge fields have constrained types (text, number, date, phone, address, birthday, dropdown, radio). We sample all custom fields during scoping to identify type mismatches. Text fields that contain numeric data but are stored as text in Loyalistic must be declared as text in Mailchimp or they may be rejected during import. Date fields must conform to Mailchimp's supported date format. Phone numbers with non-numeric characters require text field declaration. We resolve type conflicts before the production import and document any fields that require format normalization.

Mailchimp charges for all contacts including unsubscribed

Mailchimp's pricing is based on total contact count across all statuses, including unsubscribed and non-subscribed contacts. Loyalistic may count only active or opted-in contacts toward its limit. We audit the Loyalistic contact list for unsubscribed and bounced records before migration and discuss with the customer whether to import them as suppressed (to preserve historical context and avoid re-import risks) or to leave them out and reduce Mailchimp billing exposure. Importing suppressed contacts is the safer choice for deliverability; omitting them reduces cost but requires managing a separate suppression list manually.

Automation workflows and sequences do not transfer

Loyalistic workflow automations and sequence enrollments are platform-specific logic that does not have a Mailchimp equivalent at the migration layer. Workflows define triggers, conditions, and actions in Loyalistic's builder; Mailchimp Customer Journeys use a different trigger model and action library. We do not migrate workflows as code. We deliver a written inventory of every active Loyalistic workflow and sequence with its trigger, conditions, enrollment criteria, and action list, plus a recommended Mailchimp Customer Journey equivalent. The customer's marketing team or a Mailchimp-certified partner rebuilds these post-migration.