Migrate from Comarch Marketing Automation to Mailchimp

Comarch loyalty member profiles include standard contact fields (email, name, address) plus loyalty-specific attributes: tier level, points balance, enrollment date, and program membership. We extract these fields from Comarch and map email and name to Mailchimp's native EMAIL, FNAME, and LNAME merge fields. Loyalty tier and points balance map to custom merge fields we pre-create in the Mailchimp audience before migration (TIER_LEVEL and POINTS_BALANCE as text or number fields). Enrollment date maps to a MERGE6 date field. Members are tagged by their Comarch loyalty tier (Gold Member, Silver Member, Bronze Member) using Mailchimp Tags so segment filters can isolate tier cohorts without requiring additional merge field filters.

Comarch deployments frequently run multiple loyalty programs simultaneously, each with distinct tier structures, earning rules, and partner configurations. Mailchimp operates on a per-audience data model. For single-program Comarch deployments, we create one Mailchimp audience and use Tags to distinguish program membership. For multi-program Comarch deployments, we evaluate whether to create separate Mailchimp audiences per program or consolidate into one audience with tags and merge fields (PROGRAM_NAME, PROGRAM_ID). This decision is made during scoping based on program count and the customer's Mailchimp plan, because Mailchimp charges per-audience on most plans. We document the chosen architecture and configure the audience schema accordingly.

Comarch customer segments are built from AI-driven analysis of zero and first-party data with configurable rules-based filtering. We export segment definitions and member lists from Comarch and recreate them as Mailchimp Segments with equivalent filter conditions. Comarch behavioral conditions referencing cross-platform analytics events (purchase recency, engagement scores computed in Comarch BI) may require adjustment because Mailchimp Segments are built from contact field values, tags, and engagement activity logged within Mailchimp. We document every segment that relies on Comarch-native behavioral data so the customer's admin can supplement with Mailchimp engagement-based conditions post-migration.

Comarch campaign metadata (campaign name, subject line, send date, audience assignment, channel type) migrates directly to Mailchimp Campaign records via the Mailchimp Marketing API. The Comarch customer journey workflow logic, including automation triggers, conditional branches, delay steps, and cross-channel actions, is stored in a proprietary format that does not export via standard APIs. We extract the journey metadata, map it to the Mailchimp campaign record, and deliver a written Customer Journey rebuild guide documenting every step, condition, and action for the customer's admin to reconstruct in Mailchimp Customer Journeys.

Comarch promotional offers include discount rules, eligibility criteria, offer types (discount, bonus points, multiplier), and temporal constraints. We export offer definitions and map them to Mailchimp as Tags (DISCOUNT_OFFER, BONUS_POINTS, etc.) with offer metadata stored in merge fields (OFFER_TYPE, OFFER_EXPIRY). Promotional mechanics such as conditional discount rules, point earning multipliers, and time-limited offer triggers have no native Mailchimp equivalent. If the customer's loyalty program relies on automated promotional mechanics, we recommend a dedicated loyalty app from the Mailchimp marketplace or a custom integration. We flag every offer that cannot be represented in Mailchimp's data model during scoping.

Comarch AI-generated product recommendations and churn predictions are computed at runtime from behavioral models and are not stored as exportable data records. These predictions depend on Comarch's proprietary analytics engine and are recalculated continuously as new behavioral data arrives. We do not migrate AI recommendations. We recommend rebuilding recommendation logic in Mailchimp using third-party integrations (e.g., Nosto, Dynamic Yield) or Mailchimp's product recommendation blocks in campaigns. Churn prediction models require replacement with Mailchimp engagement-based segments (e.g., members who have not engaged in the last 30, 60, or 90 days) as a starting point.

Comarch KPIs including growth rate, churn rate, average transaction value, loyalty penetration, CLV, engagement index, enrollments, and NPS are exported as numeric records tied to member IDs. We migrate these as historical data points associated with each contact record in Mailchimp, stored as custom merge fields or as a structured notes attachment. Mailchimp generates its own native engagement metrics (open rate, click rate, unsubscribe rate) from campaign activity logged after migration, so the Comarch historical KPIs provide a baseline for post-migration reporting rather than a continuation of existing metric tracking.

Comarch supports multichannel delivery including email, SMS, direct mailing, Facebook, and call-center integration. Email channel configuration migrates to Mailchimp's authenticated sending domain and campaign setup. SMS channel configuration depends on whether the customer has activated the Mailchimp SMS add-on, which requires Standard or Premium plan and a separate SMS setup with US or EU number provisioning. We do not migrate Facebook, push notification, direct mail, or call-center channels as Mailchimp has no native equivalents for these channels. We document the full channel inventory from Comarch so the customer's admin can plan alternative channel replacements.

Enterprise Comarch deployments frequently extend the contact data model with custom fields for industry-specific attributes such as insurance policy numbers, retail store IDs, or telecom contract types. We export custom property definitions alongside record data. Before migration, we pre-create corresponding merge fields in the Mailchimp audience with matching data types (text, number, date, phone). Multi-value custom fields require transformation into tag format or pipe-delimited text merge fields to avoid data loss in Mailchimp's single-value merge field model. We review every custom field with the customer during discovery and confirm the transformation approach before import begins.

Comarch marketing materials, offer PDFs, and program documentation can be exported as file references or binary blobs depending on the deployment configuration. We flag attachments for individual download during extraction and provide a file inventory with original file names and associated record references. In Mailchimp, these files upload to the Content Studio for reuse in campaigns. We do not automate attachment migration due to the variation in Comarch storage configurations across partner-administered deployments. The customer's admin reviews the file inventory and uploads relevant assets to Mailchimp Content Studio post-migration.

Comarch EDI and ERP integrations are configured at the account level for B2B wholesale workflows. These integration endpoints (connection strings, API credentials, EDI mapping rules) are Comarch-specific and have no Mailchimp equivalent, because Mailchimp is an audience engagement platform rather than an ERP or EDI system. We extract the integration configuration metadata and document it in the migration handoff so the customer's IT team can evaluate whether equivalent integrations are needed in the new ecosystem. We do not migrate EDI mapping rules, ERP connection points, or wholesale-specific account configurations to Mailchimp.