Migrate from Comarch Marketing Automation to Zoho CRM

Comarch loyalty member profiles (with member ID, loyalty tier, enrollment date, points balance, and engagement score) map to Zoho CRM Contact records. We extract the loyalty attributes as custom fields: Loyalty_Tier__c (picklist), Enrollment_Date__c (date), Points_Balance__c (number), Lifetime_Value__c (currency), and Engagement_Score__c (number). Transaction history linked to member IDs migrates as related custom object records in a Loyalty_Transactions__c custom module. The Comarch contact's primary email, phone, and address fields map to Zoho standard fields with dedupe by email address.

Comarch loyalty program definitions include tier structures, earning rules, redemption logic, and partner configurations. We export program metadata and map to a Zoho CRM custom module Loyalty_Program__c with fields for Tier_Name__c, Points_Multiplier__c, Redemption_Rate__c, and Partner_Config__c (long text). Since Zoho CRM does not have a native loyalty program object, custom module schema is designed during scoping and deployed before member import. Any non-standard earning rule types (time-limited multipliers, partner-specific accruals) are flagged for manual review against Zoho's custom module capabilities.

Comarch segments are built from AI-driven analysis of zero and first-party data with rules-based filtering. We export segment definitions (name, criteria, member count) and member contact IDs. Segments with under 10,000 members are mapped to Zoho CRM Tags (one tag per segment name). Segments exceeding 10,000 members or requiring dynamic membership are documented as Zoho Marketing Automation Segments to rebuild post-migration. The segment criteria logic is preserved in a custom field Segment_Criteria__c on the Contact for admin reference during rebuild.

Comarch campaign journey metadata (campaign name, channel assignments, start and end dates, audience size, send history, and send counts) migrates to Zoho CRM Campaign records. The journey workflow logic itself is stored in Comarch's proprietary format and cannot be exported via API. We extract campaign metadata and contact engagement records (opens, clicks, unsubscribes) as Campaign Member status history. The automation logic is documented in the automation rebuild inventory delivered post-migration for the customer's admin to reconstruct in Zoho Marketing Automation 2.0 Journeys.

Comarch promotional offer definitions include discount rules, eligibility criteria, temporal constraints, and partner-specific configurations. We map offer data to a Zoho CRM custom module Promotional_Offer__c with fields for Offer_Type__c (picklist: discount/cashback/free-item), Discount_Value__c (number), Eligibility_Criteria__c (long text), Start_Date__c, End_Date__c, and Partner_Name__c. Offer PDFs and attachments are downloaded individually and re-uploaded to Zoho CRM Attachments linked to the Promotional_Offer__c record.

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 map these to a custom module Loyalty_KPI__c with fields for Member_ID__c (lookup to Contact), KPI_Type__c (picklist), KPI_Value__c (number), KPI_Date__c (date), and Source_System__c (constant: Comarch). This preserves longitudinal KPI data for loyalty reporting even though Comarch BI Point dashboards do not migrate.

Comarch multichannel configurations for email, SMS, push, direct mail, Facebook, and call-center are exported as structured channel reference records. We map these to Zoho Marketing Automation channel configurations (email sender domain, SMS gateway settings, WhatsApp Business account) and to Zoho CRM custom fields on Contact for channel opt-in flags (Email_Opt_In__c, SMS_Opt_In__c, Push_Opt_In__c, Call_Opt_In__c). Sender domain reputation and IP warming for email are documented for Zoho's deliverability setup.

Enterprise Comarch deployments frequently extend the data model with custom fields for industry-specific attributes (banking policy numbers, insurance policy IDs, retail store codes, telecom SIM identifiers). We extract custom property definitions alongside record data and map each to a Zoho CRM custom field of the matching type. Text fields map to text, numeric to number, dates to date, and picklists to picklist with value mapping preserved. Custom field metadata (API name, field type, picklist values) is documented in the schema design phase.

Comarch EDI and ERP integrations are configured at the account level for B2B wholesale workflows. We extract integration endpoint configurations (EDI message types, protocol settings, partner IDs, and ERP connection parameters) as structured records in a custom module Integration_Config__c. These configurations map to Zoho custom fields rather than live integrations; the customer uses this documentation to reconfigure connections in Zoho's native ERP integrations or Zoho Catalyst for custom EDI routing post-migration.

Marketing materials, offer PDFs, and program documentation are exported as file references or binary blobs depending on the Comarch deployment configuration. We flag attachments for individual download during extraction, map them to Zoho CRM native Attachments linked to the parent record (Contact, Loyalty_Program__c, Promotional_Offer__c, or Campaign), and preserve the original filename and MIME type. Large file batches (over 500 attachments) are chunked into separate import batches to stay within Zoho's attachment size limits.

Comarch user and owner records map to Zoho CRM User by email address. We extract every distinct user referenced on loyalty member, campaign, and engagement records. Owner assignments migrate as Zoho CRM Owner lookup fields on Contact, Campaign, and custom module records. Any Comarch owner without a matching Zoho CRM User is held in a reconciliation queue for the customer's admin to provision before record import resumes.