Migrate from Comarch Marketing Automation to HighLevel

Comarch loyalty member profiles with attributes, transaction history, and engagement scores map to GoHighLevel Contact records. The Comarch member ID becomes an external ID field in GoHighLevel for deduplication. Loyalty tier membership and engagement scores migrate as Contact custom fields (configured pre-import). Enrollment date and last activity date map to standard GoHighLevel date fields.

Comarch loyalty program definitions (tier structures, earning rules, redemption rules) are configuration objects without a direct GoHighLevel equivalent. We extract program metadata and map tier names to Contact custom fields (e.g., loyalty_tier__c) and Tags for segmentation. Partner-specific earning rules are noted in the migration inventory as rule-based workflows to rebuild in GoHighLevel Workflow Builder. Tier thresholds and point balances map to numeric custom fields.

Comarch AI-driven segments (built from zero and first-party behavioral data) are exported as static member lists. We migrate the segment name and all member Contact IDs. In GoHighLevel, segments become Smart Lists or Tag Groups based on customer preference during scoping. The AI-driven rule logic that built the segment in Comarch is documented for rebuild using GoHighLevel's filtering conditions in Smart Lists.

Comarch campaign metadata (name, start/end dates, audience size, channel assignments) migrates to GoHighLevel Campaign records. The audience member list migrates as Contact records tagged to the campaign. The proprietary journey workflow logic does not export; we document every Comarch journey step, trigger condition, delay, and action as a written workflow rebuild guide for GoHighLevel's Workflow Builder.

Comarch promotional offer definitions (discount rules, eligibility criteria, temporal constraints) map to GoHighLevel Coupons. Offer names become coupon codes, discount percentages become the coupon value, and validity dates map to the coupon start and expiry dates. Complex conditional eligibility rules (e.g., tier-based or spend-threshold based) are documented for rebuild as Workflow conditions.

Comarch KPIs (growth rate, churn rate, average transaction value, CLV, engagement index, NPS) are exported as numeric records tied to member IDs. We map each KPI to a Contact custom field (e.g., clv__c, churn_risk_score__c) on the corresponding GoHighLevel Contact. Dashboard visualizations from Comarch BI Point do not migrate; underlying KPI data is available for rebuild in GoHighLevel's reporting or through a connected analytics tool.

Comarch channel configurations map to GoHighLevel's channel integrations. Email setup maps to Twilio or SMTP configuration in GoHighLevel. SMS maps to Twilio or GoHighLevel's built-in SMS via approved providers. Facebook Messenger maps to GoHighLevel's Facebook integration. Call-center configurations map to GoHighLevel's voice/phone channel. We transfer channel credentials and configuration references, noting that sender reputation and IP warming must be re-established in GoHighLevel post-migration.

Comarch custom fields for industry-specific attributes (common in telecom, retail, and banking verticals) migrate as GoHighLevel Contact custom fields. Field type mapping: text to text, numeric to number, date to date, picklist to dropdown. Required field constraints are reviewed against GoHighLevel's field requirements and adjusted if the source field was optional. Custom fields are created in GoHighLevel before any Contact data is imported.

Comarch EDI and ERP integration endpoint configurations are extracted as connection metadata. GoHighLevel does not have native EDI connectors; we map these to Zapier or Make scenarios that re-establish the connection in GoHighLevel. The customer identifies which integrations are still active post-migration during scoping, and we configure the first version of each Zapier/Make flow as part of the migration scope.

Marketing materials, offer PDFs, and program documentation exported from Comarch migrate as Notes attached to the relevant GoHighLevel Contact, or as files in GoHighLevel's file storage with links recorded on the Contact. We flag attachments for individual download during the extraction phase, as Comarch's attachment storage format varies by deployment configuration.