Migrate from Solitics to Mailchimp

Solitics unified user profiles map to Mailchimp Members within an Audience. Each profile's attributes (name, email, phone, custom properties) migrate as typed merge fields. Mailchimp caps standard plan merge fields at 30 total and each field at 255 characters; Premium raises this to 80 fields. We assess the attribute count during schema discovery and flag any attributes exceeding the character limit for truncation or split-field strategy before migration begins.

Solitics behavioral event sequences (deposits, trades, bets, logins, custom actions) do not map to a native Mailchimp object because Mailchimp has no continuous event log. We migrate the most recent event type and timestamp as merge fields and apply the corresponding value as a Tag on the Member record. Customers who need behavioral history intact should plan to export it to a data warehouse; we document the event schema and provide a structured event-history export file for that purpose.

Solitics segments are live, rule-based definitions built from profile attributes and behavioral conditions. We export each segment as its rule logic (attribute conditions, event conditions, time windows, combinators) in a structured document. During migration, we replicate the rule logic as Mailchimp Segments using the same conditions on the imported Member properties. Tags serve as the static equivalent for behavioral conditions that exceed Mailchimp's segment builder complexity.

Solitics user journeys define automated workflows triggered by events or segment membership, with branching logic, delay rules, and channel steps. Mailchimp's Customer Journeys provide a visual automation builder with trigger, delay, condition, and action steps. We export journey definitions as structured documentation covering entry triggers, step sequence, branching conditions, delay configuration, and channel assignment. We do not migrate journey logic as functional code; the customer's marketing team rebuilds the journey sequence in Mailchimp's automation builder using our documentation as the specification.

Solitics campaign metadata, targeting rules, content blocks, and performance history migrate as Mailchimp Campaigns and stored Templates. Email body content, subject lines, and from-name configurations carry over directly. SMS and WhatsApp campaign content migrates as structured text blocks; channel routing and SMS sender ID configurations do not carry over and must be re-established in Mailchimp's SMS setup. Push notification content migrates as structured documentation if the destination includes a push integration.

Solitics' Smart Gamification module stores mission definitions, loyalty point balances, badge/achievement rules, widget configurations, and threshold logic as platform-native objects. Mailchimp has no gamification engine. We export a complete inventory of all gamification assets — mission rules, point structures, badge definitions, widget configurations — as structured documentation. The customer rebuilds gamification mechanics in a dedicated loyalty platform (Yusp, Antorafa, Smile.io) or as Mailchimp-tagged campaigns; we provide the specification for whichever path they choose.

Solitics custom event types beyond the standard set require a schema discovery pass before migration. We catalog every active custom event name and its property fields from the Solitics API, then assess each property's data type against Mailchimp's merge field model. Properties that fit within Mailchimp's 255-character text limit or standard field types (number, date, phone, address) migrate as custom merge fields. Complex nested objects or high-cardinality values are documented for alternative storage.

Solitics integrations with external systems — trading platforms, sports feeds, bonus engines, back-office databases — are configured connections, not data records, and do not transfer across platforms. We document every active integration, its data flow direction (inbound/outbound), and the credentials or endpoint it uses. The customer's technical team uses our integration inventory as a re-establishment checklist to reconnect data sources to Mailchimp via Zapier, native integrations, or direct API connection.

Solitics channel assets — email templates, SMS message bodies, push notification copy, WhatsApp template text — export as structured content. Email templates migrate with layout, copy, and image references preserved as Mailchimp templates. Localization settings and A/B test variants export as metadata. We do not migrate channel compliance configurations (SMS sender IDs, WhatsApp Business account registrations, push certificates) as these are carrier and platform registrations tied to the source vendor.

Solitics user accounts, journey owners, and campaign managers map to Mailchimp Tags applied to Member records for ownership tracking, or to audience-level user roles if the destination Mailchimp account uses shared team access. Mailchimp's per-user role model (Admin, Manager, Author, Viewer) provides a lightweight equivalent for access control documentation.