Migrate from Comarch Marketing Automation to Twenty CRM

Comarch loyalty member profiles with tier, points balance, enrollment date, and engagement score map to Twenty Contact records with custom fields. We create custom fields for loyalty_tier__c, points_balance__c, enrollment_date__c, and engagement_score__c during schema setup. The Comarch member_id becomes the Twenty contact's external_id__c for deduplication. Any Comarch custom fields on the member profile map to equivalent Twenty custom fields, with field type matching (date, number, picklist) confirmed during scoping.

Comarch loyalty program definitions include tier structures, earning rules, and partner configurations. Twenty has no native loyalty program object, so program metadata maps to Contact-level custom fields or a related custom object. We create a loyalty_program__c text field and program_tier__c picklist on Contact, and a separate LoyaltyProgram custom object for program-level rules (earning rates, redemption options) that lookup to Contact. Enterprise customers with multiple loyalty programs create one LoyaltyProgram record per program and link members via lookup relationship.

Comarch AI-driven and rules-based segments export as segment definitions and member lists. We map segment membership to Twenty tags on Contact records, creating a tag per Comarch segment (e.g., 'high-value-b2b', 'dormant-90-day'). The tag-based approach keeps segment membership visible in Twenty's contact list view. For segments with complex membership criteria, we document the rule as a custom field or as a tag with a note field describing the original criteria for future segmentation in Twenty.

Comarch campaign metadata (campaign name, type, channel, start/end dates, target audience size) migrates to a Campaign custom object in Twenty. The proprietary journey automation logic (trigger conditions, branching rules, delay steps, action sequences) is not extractable and is flagged for manual rebuild. We export campaign audience member lists and map each to a CampaignMembership custom object linked to Contact, preserving which contacts were targeted by which campaign.

Comarch promotional offers include discount rules, eligibility criteria, and temporal constraints. We map active promotional offers to Twenty Product records with custom fields for discount_type__c, discount_value__c, eligibility_criteria__c, and valid_from__c / valid_until__c. Archived or expired offers map to a PromotionalOffer custom object for historical reference without cluttering the active product catalog.

Comarch KPIs (growth_rate, churn_rate, average_transaction_value, clv, engagement_index, nps) migrate as numeric custom fields on Contact. We create clv__c, churn_risk_score__c, avg_transaction_value__c, and engagement_index__c fields. KPI values are tied to member_id at export, so resolution against the Twenty Contact external_id preserves the metric attribution per contact. KPI records without a matching contact are reconciled during the audience delta phase.

Comarch channel configurations (email service provider, SMS gateway, push notification service, call-center connector) export as integration endpoint references. Twenty has native email and task tracking but no native SMS or push channel. We map the Comarch channel reference to a note on the Contact or as integration configuration documentation for the customer's admin to reconnect in Twenty via a third-party integration (Twilio for SMS, OneSignal for push, a VOIP connector for call-center).

Comarch organizations linked to loyalty members map directly to Twenty Company records. The organization name, domain, address, and industry fields migrate 1:1. Company is created before Contact import so that the Company lookup relationship is satisfied at Contact insert time.

Comarch enterprise deployments frequently extend the member and organization data model with custom fields for industry-specific attributes. We extract custom property definitions alongside record data, map them to Twenty custom fields of matching type, and validate that picklist values align with Twenty's picklist constraints. Any multi-select Comarch attributes map to Twenty multi-select picklist fields.

Comarch marketing materials, offer PDFs, and program documentation export as file references or binary blobs depending on the deployment configuration. We migrate file references as Twenty Note records with the original filename preserved and a URL reference in the note body. If the deployment supports binary blob export, files migrate as Note attachments linked to the parent Contact or Company record.

Comarch AI-generated product recommendations and churn predictions are computed at runtime from behavioral models and are not stored as exportable records. We do not migrate these. We recommend rebuilding recommendation logic in the destination platform using available AI tooling or documenting the recommendation triggers for business-rule implementation post-migration.

Comarch BI Point dashboards and visualizations are rendered client-side from underlying KPI data and do not export as reusable objects. We migrate the underlying KPI data (growth_rate, churn_rate, clv, engagement_index, nps) as numeric fields on Contact so that dashboards can be rebuilt in Twenty using its reporting features. The dashboard rebuild is outside standard migration scope.