Migrate from Comarch Marketing Automation to monday CRM

Comarch member profiles with loyalty attributes (tier level, points balance, enrollment date, lifetime value) map to Monday.com Contact records with custom fields created during schema setup. We extract the loyalty tier name, points balance, and enrollment timestamp as separate custom fields on the Contact. Transaction history counts and engagement scores migrate as numeric custom fields. The Comarch member ID becomes the Contact ID or a custom field for lookup resolution.

Comarch loyalty program definitions include tier structures (Bronze, Silver, Gold, Platinum), earning rules, and redemption logic. These do not have a direct Monday.com CRM equivalent, so we represent them as Contact Tags for tier classification and custom fields for program-specific attributes (program name, earning rate, redemption rate). The customer reviews and approves the mapping during scoping. Any partner-specific earning rules or time-limited promotional structures that cannot be represented as flat field values are flagged for documentation and manual configuration in Monday.com.

Comarch segments built from AI-driven analysis and rules-based filtering migrate as Monday.com Contact Groups or Tags depending on the customer's preferred structure. We export segment definitions (name, criteria list) and the member list, then create corresponding Groups in Monday.com CRM and assign contacts to them. Segment membership is refreshed post-migration if the customer wants ongoing dynamic segmentation; static membership lists migrate as group assignments.

Comarch campaign metadata (campaign name, description, start/end dates, channel assignments, audience size, send history) migrates to Monday.com CRM as Campaign records with custom fields carrying the Comarch campaign ID and send metrics. The journey workflow logic itself is proprietary and does not export. We deliver a written journey inventory document listing every Comarch campaign, its trigger conditions, channel sequence, and conditional branches, so the customer's admin has a rebuild checklist for Monday.com's workflow automations.

Comarch promotional offers with discount rules, eligibility criteria, and temporal constraints migrate as custom fields on the relevant Contact records. Offer name, discount percentage, eligibility period, and redemption status become custom fields. Offers that apply to product categories rather than individual contacts are documented separately for manual configuration in Monday.com's product or deal records.

KPIs including growth rate, churn rate, average transaction value, loyalty penetration, CLV, engagement index, enrollments, and NPS migrate as numeric custom fields on the Contact record. Each metric gets a dedicated field with the Comarch metric name preserved in the field label. KPI dashboards built in Comarch BI Point do not migrate; we deliver the underlying metric data so that the customer can rebuild dashboards in Monday.com's built-in chart and dashboard tools.

Comarch channel configurations for email, SMS, push, and call-center migrate as integration reference records. The actual channel integrations (email provider, SMS gateway, push notification service) must be reconfigured in Monday.com post-migration using Monday.com's native integrations or marketplace connectors. We document the current channel assignments per campaign so the customer's admin knows which providers to reconnect.

Enterprise Comarch deployments frequently extend the data model with custom fields for industry-specific attributes (e.g., insurance policy type, retail store ID, telecom contract tier). We extract custom property definitions alongside record data and map them to Monday.com CRM custom fields on the appropriate object (Contact or Company). Field types are mapped: text to text, numeric to number, date to date, picklist to dropdown.