Migrate from Comarch Marketing Automation to Odoo CRM

Comarch loyalty member profiles (with loyalty attributes, transaction history, and engagement scores) map to Odoo CRM Contact records as res.partner entries. We extract the member ID, enrollment date, loyalty tier, total points balance, and all demographic fields as structured Contact fields. Comarch engagement scores (0-100 range) migrate as a custom integer field loyalty_score__c. Comarch custom fields for B2B attributes (industry codes, trade license IDs) map to res.partner custom fields configured in Odoo Studio before migration.

Comarch loyalty program definitions (tier structures, earning and redemption rules, partner configurations) do not have a native Odoo CRM equivalent. We extract program metadata as structured records and map them to a combination of Odoo custom fields on Contact (program_id, tier_name, points_expiry_date) and a dedicated Tag Group for program classification. Earning rule logic is documented in the automation rebuild handoff; Odoo's Marketing Automation app rebuilds these rules as trigger-action flows.

Comarch customer segments (built from AI-driven analysis of zero and first-party data with rules-based filtering) map to Odoo CRM Tags. We export the segment name and member list, then create a crm.tag record per segment and link all matching Contact records via crm tagging. Multi-dimensional segments (segments composed of sub-segments) are represented as nested tag hierarchies using Odoo's Groups feature.

Comarch campaign metadata (name, audience size, send date, channel assignments, and performance metrics) migrates to Odoo Email Marketing as campaign records. The journey workflow logic itself is proprietary and not exportable; we extract campaign metadata, audience lists, and send history as a written inventory for the customer's admin to rebuild in Odoo's Marketing Automation app. Channel assignments (email, SMS, push) map to the corresponding Odoo Marketing Suite apps the customer has licensed.

Comarch promotional offers (discount rules, eligibility criteria, temporal constraints, and offer codes) map to Odoo Product records with custom fields capturing offer_type, discount_percentage, eligibility_criteria, valid_from, and valid_until. Offer PDFs and program documentation migrate as ir.attachment records linked to the product. Time-limited offer logic is documented for Odoo Marketing Automation rebuild.

Comarch KPIs (growth rate, churn rate, average transaction value, loyalty penetration, CLV, engagement index, enrollments, NPS) export as numeric records tied to member IDs. We map these to Odoo CRM custom fields on Contact: churn_risk_score, clv_estimated, avg_transaction_value, nps_score. KPI benchmarking data (Comarch BI Point metrics) is mapped to Odoo custom report fields for rebuild in Odoo's pivot view.

Comarch channel configurations (email deliverability settings, SMS sender IDs, push notification credentials, Facebook page links, call-center routing) map to the corresponding Odoo Marketing Suite app settings: Email Marketing accounts, SMS Gateway configuration, Social Marketing accounts, and Events settings. We extract channel config references and map them to the Odoo apps licensed at the destination.

Enterprise Comarch deployments extend the data model with custom fields for industry-specific attributes (B2B trade license numbers, regulatory IDs, partner codes). We extract all custom property definitions alongside record data and map them to Odoo res.partner custom fields created via Developer mode or Studio before migration. Field type mapping: Comarch integer and decimal fields map to Odoo float or integer; date fields map to date; text fields map to text or char depending on length.

Comarch marketing materials, offer PDFs, and program documentation export as binary blobs or file references depending on deployment configuration. We extract attachments and link them to the corresponding Odoo record (Contact, Product, or Campaign) via ir.attachment. We flag attachments for individual download during the extraction phase and batch them for Odoo import via the attachments API.

Comarch EDI and ERP integration endpoints (configured at the account level for B2B workflows) are extracted as integration endpoint records. We map these to Odoo connectors or document them for custom Python integration scripts that the customer's Odoo developer configures post-migration. ERP-specific mappings (sales order pull, inventory push) are flagged as out-of-scope for the CRM migration and noted for a separate Odoo ERP integration engagement.

Comarch AI-generated product recommendations and churn predictions are computed at runtime from behavioral models and are not stored as exportable data records. We do not migrate AI recommendation data. We recommend rebuilding the behavioral scoring model in Odoo AI (if the customer licenses Odoo's AI add-ons) or in a third-party CDP integrated via Odoo's API. Customer-facing recommendation delivery requires a separate implementation project.

Comarch dashboards and visualizations (Comarch BI Point KPIs, loyalty benchmarking, churn prediction charts) are rendered client-side from underlying data and do not export as reusable objects. We migrate the underlying KPI data so that dashboards can be rebuilt in Odoo's reporting module. We deliver a dashboard rebuild checklist with the Comarch KPI names, their Odoo equivalents, and the recommended Odoo view type (pivot, graph, cohort) for each metric.