Migrate from Comarch Marketing Automation to Salesforce Sales Cloud

Comarch loyalty member profiles with tier, engagement score, and transaction history map to Salesforce Contact attached to an Account. Members without a qualifying business relationship (unregistered subscribers, early-funnel contacts) map to Salesforce Lead. The original Comarch tier level, loyalty points balance, and enrollment date migrate as custom Contact fields (loyalty_tier__c, loyalty_points_balance__c, loyalty_enrollment_date__c) so that tier-based reporting and segmentation rebuilds can reference them in Salesforce Reports and Flow criteria.

Comarch loyalty program definitions include tier structures, earning and redemption rules, and partner configurations. These map to a Salesforce custom object Loyalty_Program__c with fields for program name, tier count, earning rate, and redemption rule type. Earning and redemption rule logic (complex conditional logic not representable as field values) is documented in the rebuild checklist for manual configuration in Salesforce Flow or a custom Aura/LWC component.

Comarch segments built from AI-driven and rule-based filtering map to Salesforce Campaign records with CampaignMember entries linking the segment members. The segment name, definition rule (stored as a text description), and member count migrate as Campaign fields. Segment membership is rebuilt as Campaign Member Status values in Salesforce. Active segments used for ongoing campaigns become Salesforce Campaigns; archived segments become Campaign records with status Archived.

Comarch campaign metadata (name, channel assignment, start and end dates, audience size) maps to Salesforce Campaign. Send history records (opens, clicks, bounces) migrate as custom Campaign fields or CampaignInfluence records if multi-touch attribution is required. The multichannel journey logic itself is proprietary and does not export; we document every campaign's trigger, channels, and audience filter as a written specification for rebuild in Salesforce Marketing Cloud Journey Builder or Flow.

Comarch promotional offers include discount rules, eligibility criteria, and temporal constraints. These map to a Salesforce custom object Promotion__c with fields for offer name, discount_type__c, discount_value__c, eligibility_criteria__c, start_date__c, and end_date__c. Complex eligibility rules (partner-specific, tier-restricted, or time-limited conditional discounts) are documented as text in the eligibility_criteria__c field with a flag requiring manual rebuild in Salesforce as Flow criteria or a custom Lightning component.

Comarch KPIs including growth rate, churn rate, average transaction value, loyalty penetration, CLV, engagement index, enrollments, and NPS migrate as custom fields on the Salesforce Contact (churn_rate__c, clv__c, engagement_index__c, nps_score__c). KPI values are tied to member IDs during extraction and mapped to the corresponding Contact record during migration. We preserve the KPI as_of_date__c timestamp for audit. Churn prediction and AI-generated scores (runtime-computed) do not migrate because they are not stored as exportable records.

Comarch email channel configurations (SMTP settings, sender profiles, deliverability settings) are extracted as configuration records. We map them to Salesforce's Email Relay, Email Load Balancer, or custom Email Integration (SpringCM) depending on the customer's Salesforce edition and existing email infrastructure. If the customer uses Salesforce Marketing Cloud Email Studio, we document the sender profile and deliverability settings for rebuild there.

Comarch SMS channel configurations for EU-country messaging migrate as documented specifications. Salesforce Marketing Cloud MobileConnect (available in Marketing Cloud) or a Twilio Connected App in Sales Cloud replaces Comarch SMS routing. We export the country-level routing rules and short-code configurations as written documentation for the customer's marketing operations team to configure in the destination system post-migration.

Comarch enterprise deployments frequently extend the loyalty member and campaign data model with custom fields for industry-specific attributes (B2B wholesale pricing tiers, insurance policy IDs, retail store codes). We extract all custom property definitions alongside record data and map them to Salesforce custom fields of equivalent type (text, number, picklist, date). Field-level security and field-level sharing are documented for the customer's Salesforce admin to configure post-migration.

Marketing materials, offer PDFs, and program documentation stored in Comarch migrate as Salesforce ContentDocument records via ContentVersion binary upload. File metadata (filename, content type, upload date) preserves from Comarch. Files are linked via ContentDocumentLink to the related Contact, Account, Campaign, or Promotion__c record. We flag attachments for individual download during extraction if the Comarch deployment uses partner-managed file storage.

Comarch EDI and ERP integrations are configured at the account level for B2B workflows. We extract integration endpoint configurations (API URLs, authentication credentials stored as secure notes) as written documentation for rebuild. Integration logic in Comarch (order sync, inventory push) maps to Salesforce Connect external objects or MuleSoft Composer flows, which the customer's integration team rebuilds post-migration.

AI-generated product recommendations and churn predictions computed at runtime from behavioral models are not stored as exportable data records in Comarch. We do not migrate these. We recommend rebuilding AI-driven recommendation logic in Salesforce Data Cloud (available on Enterprise and Unlimited) or a third-party CDP integration. Churn prediction can be rebuilt using Salesforce Einstein Prediction Builder or a dedicated model retrained on migrated KPI data in a data warehouse.

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 (as custom fields on Contact, Campaign, and custom loyalty objects) so that Salesforce Reports and Dashboards can be rebuilt referencing the migrated data. The rebuild checklist includes every Comarch BI Point chart and its underlying KPI for the customer's admin to reconstruct in Salesforce Analytics.

Comarch email, SMS, and push send histories (open records, click records, bounce records, unsubscribe records) map to Salesforce CampaignMember with custom fields for send_date__c, open_date__c, click_url__c, bounce_reason__c, and unsubscribe_date__c. Each send event becomes a separate CampaignMember record. Activity timeline ordering is preserved by setting CampaignMember.CreatedDate to the original Comarch timestamp.