Migrate from Comarch Marketing Automation to Pipedrive

Comarch loyalty member profiles with loyalty attributes, transaction history, and engagement scores map to Pipedrive Person records. We extract member_id, email, name, phone, address, enrollment date, and loyalty tier level, then map them to Pipedrive's name, email, phone, and address fields plus custom fields for loyalty_tier, enrollment_date, and engagement_score. The member_id becomes the Pipedrive org_id if the Comarch account has a single-account structure, or maps to a separate Organization record if Comarch stores member records under corporate accounts.

Comarch B2B accounts storing loyalty program configurations for enterprise clients map to Pipedrive Organization records. We extract account_name, address, industry, partner_status, and ERP integration references, mapping them to Pipedrive's name, address fields, and custom fields. If Comarch stores both B2C individual members and B2B corporate accounts, we resolve the Organization before importing related Person records so that the relationship is established at import time.

Comarch AI-driven customer segments built from behavioral rules map to Pipedrive Labels on Contact and Organization records. We export segment definitions (name, rule criteria, member count) and apply Labels to the matching Pipedrive records during migration. Segments with complex multi-condition rules that cannot be represented as simple Labels become Pipedrive Smart Lists defined post-migration using Pipedrive's filter conditions.

Comarch campaign metadata (name, channel, send date, audience size, send status) migrates to Pipedrive Activity records as campaign history entries. The campaign journey workflow logic is proprietary and does not export via API; we document every campaign's trigger conditions, channel sequence, delay rules, and branching logic in a written rebuild guide for Pipedrive Workflows. The customer rebuilds each journey manually in Pipedrive's visual Workflow builder.

Comarch promotional offer definitions including discount rules, eligibility criteria, and temporal constraints map to custom fields on the relevant Contact record. For time-limited offer campaigns tied to deal activity, we create a Pipedrive Deal with the offer details in custom fields and link it to the Contact or Organization. Offer rules that require complex conditional logic are documented in the automation rebuild guide for Workflow recreation.

Comarch KPIs including growth rate, churn rate, average transaction value, loyalty penetration, CLV, engagement index, enrollments, and NPS migrate as numeric custom fields on Pipedrive Person or Organization records. Each KPI is tied to the original member_id. We preserve the timestamp of the most recent KPI calculation in a field called kpi_last_updated for audit and reporting continuity.

Comarch loyalty program metadata including program name, tier structure, earning rules, and partner configurations migrates as custom fields on the Organization record for B2B programs or as account-level custom fields for B2C programs. Custom tier logic, partner-specific earning rules, and time-limited promotional structures require customer review during scoping to map non-standard rules to Pipedrive-equivalent fields or note them as Workflow conditions to rebuild.

Comarch channel configurations for email, SMS, and push are exported as integration reference records and mapped to Pipedrive Activity entries showing send history per Contact. Channel credentials (sender IDs, SMS provider configurations) are documented for manual reconfiguration in Pipedrive's email integration settings or third-party SMS connector setup post-migration.

Enterprise Comarch deployments frequently extend the data model with custom fields for industry-specific attributes. We extract custom property definitions alongside record data, create matching custom fields in Pipedrive during schema setup, and map values during import. Field types are reconciled: multi-select values become Pipedrive multi-select fields, dates become date fields, and JSON-stored values are flattened into text fields with a documented format.

Comarch marketing materials, offer PDFs, and program documentation exported as file references or binary blobs are flagged for individual download during migration. We document the file URLs, names, and associated Contact or Campaign record in a file inventory spreadsheet. The customer downloads files post-migration and re-attaches them to the relevant Pipedrive records using Pipedrive's file attachment feature.

Comarch EDI and ERP integration endpoint configurations for B2B workflows are exported as documented integration specs (endpoint URLs, authentication method, data mapping rules). These do not migrate as live connections; we deliver a written integration handoff document that the customer's IT team uses to configure equivalent Pipedrive integrations or middleware connections post-migration.