Migrate from Comarch Marketing Automation to Microsoft Dynamics 365 Sales

Comarch member profiles with loyalty attributes, transaction history, and engagement scores map to Microsoft Dynamics 365 Sales Contact. We extract loyalty tier level, enrollment date, point balance, and status as custom fields on Contact (e.g., loyalty_tier__c, points_balance__c, enrollment_date__c, partner_id__c). The Comarch member ID is preserved as an external identifier for dedupe and reconciliation. Historical transaction records are mapped to a custom Transaction__c object linked to Contact.

Comarch loyalty program definitions (tier structures, earning rules, redemption rules, partner configurations) are exported as metadata records. Because Microsoft Dynamics 365 Sales has no native loyalty program object, we map program-level rules to a custom Loyalty_Program__c object and reference it from Contact via a lookup field. Custom tier thresholds and point-accrual rates are stored as custom fields and documented for the admin to configure in Microsoft Dynamics 365 Sales or Power Automate.

Comarch AI-driven and rules-based customer segments are exported as member lists tied to segment IDs. We map segment membership to a custom multi-select picklist on Contact (segment_names__c) or to static lists in Microsoft Dynamics 365 Sales . For AI-driven segments relying on Comarch behavioral models, we recommend rebuilding segment logic in Dynamics 365 Customer Insights post-migration and connecting via the native Dataverse connector.

Comarch campaign metadata (campaign name, type, start and end dates, channel references, audience size) maps to Microsoft Dynamics 365 Sales Campaign. We export the campaign record and audience list; the journey workflow logic is stored in a proprietary Comarch format and does not export via API. We deliver a written inventory of every active campaign journey with its trigger conditions, channel sequence, and delay logic so the customer's admin can rebuild in Dynamics 365 Marketing or Power Automate.

Comarch promotional offer definitions (discount rules, eligibility criteria, temporal constraints) are exported as custom Offer__c objects in Microsoft Dynamics 365 Sales . The mapping preserves offer type, discount percentage, start and end date, and eligibility rules as custom fields. Note that Microsoft Dynamics 365 Sales does not have a native coupon or offer management feature; the customer uses a third-party ISV or builds offer logic in Power Automate for redemption tracking.

Comarch KPIs (growth rate, churn rate, average transaction value, loyalty penetration, CLV, engagement index, enrollments, NPS) are exported as numeric records tied to member IDs. We map these to custom fields on Contact (e.g., clv__c, churn_risk_score__c, engagement_index__c) and to a custom KPI_History__c object for longitudinal tracking. Analytics dashboards are not migrated as rendered objects; underlying KPI data is preserved so dashboards can be rebuilt in Power BI.

Comarch channel configurations (email service provider IDs, SMS gateway references, push notification credentials, call-center integration settings) are exported as integration reference records. We map channel activity data from Comarch's send history to Microsoft Dynamics 365 Sales Email and Task records linked to the Contact. Native SMS and push require third-party ISV configuration in Dynamics 365 (e.g., ClickDimensions, a Microsoft Dynamics partner) 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 and map them to Microsoft Dynamics 365 Sales custom fields on Contact. Field types are mapped: text to Text, date to Date, numeric to Number, and picklist values to Picklist. Lookup relationships to other Comarch objects are mapped to Dynamics 365 lookup fields on the equivalent custom object.

Comarch marketing materials, offer PDFs, and program documentation are exported as file references or binary blobs. We map these to SharePoint document libraries connected to Microsoft Dynamics 365 Sales via the native SharePoint integration. Files are attached to the relevant Contact, Account, or Campaign record. Individual file downloads are handled during extraction; large binary attachments may require chunked download and re-upload to SharePoint.