CRM migration
Field-level mapping, validation, and rollback between Comarch Marketing Automation and Freshsales. We move data and schema; workflows are rebuilt natively in Freshsales.
Comarch Marketing Automation
Source
Freshsales
Destination
Compatibility
5 of 9
objects map 1:1 between Comarch Marketing Automation and Freshsales.
Complexity
BStandard
Timeline
3-5 weeks
Overview
Moving from Comarch Marketing Automation to Freshsales is a data-model simplification: Comarch's loyalty-first platform tracks members, tiers, AI-driven segments, and multichannel journey metadata across email, SMS, push, and call-center; Freshsales is a sales CRM centered on Contacts, Accounts, Deals, and Activity records with Freddy AI for lead scoring. We extract loyalty program structures and member profiles as structured contact records, routing tier information into Freshsales contact scoring groups or custom fields. Customer segments from Comarch's AI engine become Freshsales contact groups or dynamic lists. Promotional offer definitions and engagement KPIs migrate as custom fields or notes against the contact record. Comarch's automation journey logic does not export; we document every campaign trigger and branch as a written handoff for the customer to rebuild in Freshsales Freddy AI. Partner-managed Comarch deployments require partner coordination before extraction can begin.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
Each row shows how a Comarch Marketing Automation object lands in Freshsales, including any object-level transformations, lookup resolution, or schema-design dependencies.
Typical mapping — final map is confirmed during the sample migration step.
Comarch Marketing Automation
Loyalty Member / Contact Profile
Freshsales
Contact
1:1Comarch loyalty member profiles with name, email, phone, address, tier level, points balance, and enrollment date map directly to Freshsales Contact records. We extract member attributes as typed fields: tier level maps to a custom field or Freddy AI scoring group, points balance migrates as a numeric custom field, and enrollment timestamp migrates as a date field. Loyalty member ID from Comarch becomes a custom external ID field for dedupe and cross-reference.
Comarch Marketing Automation
Company / Organization
Freshsales
Account
1:1Comarch deployments that store B2B loyalty program memberships under company records map to Freshsales Account. The company name, industry, and address fields map directly. If Comarch stores individual members without a company link, we optionally create Accounts from domain data or leave the AccountId blank, allowing the customer to link post-migration.
Comarch Marketing Automation
Customer Segment
Freshsales
Contact Group
1:manyComarch AI-driven segments with membership lists map to Freshsales Contact Groups or dynamic contact lists. We export the segment name, definition logic (as a text note), and the member contact IDs. Segments are represented as static groups in Freshsales; the Comarch AI rule logic is documented as a text description for the customer's admin to recreate as a Freshsales dynamic list or Freddy AI filter.
Comarch Marketing Automation
Campaign / Customer Journey Metadata
Freshsales
Deal or Note
lossyComarch campaign records contain campaign name, channel assignments (email, SMS, push, call-center), send date ranges, and audience size. We export campaign metadata as Freshsales Deal records with a custom campaign type field, or as Notes attached to the relevant Contact records. The campaign journey workflow logic itself is proprietary and does not export; we document each campaign trigger, branch condition, and channel sequence in a written handoff for Freddy AI workflow rebuild.
Comarch Marketing Automation
Promotional Offer
Freshsales
Custom Field or Note
lossyComarch promotional offers with discount rules, eligibility criteria, and temporal constraints are exported as structured records. We map offer name, discount type, validity period, and eligibility requirements to Freshsales Contact custom fields or to a Note attached to the contact record. Complex promotional structures with conditional rules are documented as a written offer catalog for the customer to rebuild in Freshsales Freddy AI workflows.
Comarch Marketing Automation
Engagement KPI (Churn, CLV, NPS, Engagement Index)
Freshsales
Custom Field on Contact
1:1Comarch KPI records including churn prediction score, customer lifetime value, NPS, and engagement index are exported as numeric records tied to member IDs. We map these to Freshsales Contact custom fields with the original Comarch KPI name preserved in the field label (e.g., kpi_churn_score__c, kpi_clv__c, kpi_nps__c). Historical KPI values migrate as field data; real-time AI predictions are noted as runtime-only and not migrated.
Comarch Marketing Automation
Channel Configuration (Email, SMS, Push, Call-Center)
Freshsales
Freshsales Channel Settings
1:1Comarch channel configurations are metadata references to email, SMS, push, and call-center integrations. We export channel type and configuration status as lookup records. These map to Freshsales built-in email and phone tools (no migration of channel credentials required), and to a documented list of external channel references for SMS and push providers that the customer reconfigures post-migration.
Comarch Marketing Automation
Loyalty Program Tier Structure
Freshsales
Freddy AI Scoring Group or Custom Field
lossyComarch loyalty programs include tier structures (Bronze, Silver, Gold, Platinum) with earning and redemption rules. We extract the tier names and threshold values and map them to Freshsales custom picklist fields on Contact. Tier-specific earning rules are documented as a written program summary for the customer to implement in Freshsales Freddy AI if automated tier recalculation is required.
Comarch Marketing Automation
Custom Properties / Extended Fields
Freshsales
Custom Fields on Contact or Account
1:1Enterprise Comarch deployments frequently extend the data model with custom fields for industry-specific loyalty attributes. We extract all custom property definitions and map them to Freshsales custom fields on the appropriate object (Contact for member-level attributes, Account for company-level attributes). Field type mapping follows Freshsales supported types: text, number, date, picklist, multi-select picklist, phone, URL, and currency.
| Comarch Marketing Automation | Freshsales | Compatibility | |
|---|---|---|---|
| Loyalty Member / Contact Profile | Contact1:1 | Fully supported | |
| Company / Organization | Account1:1 | Fully supported | |
| Customer Segment | Contact Group1:many | Fully supported | |
| Campaign / Customer Journey Metadata | Deal or Notelossy | Fully supported | |
| Promotional Offer | Custom Field or Notelossy | Fully supported | |
| Engagement KPI (Churn, CLV, NPS, Engagement Index) | Custom Field on Contact1:1 | Fully supported | |
| Channel Configuration (Email, SMS, Push, Call-Center) | Freshsales Channel Settings1:1 | Fully supported | |
| Loyalty Program Tier Structure | Freddy AI Scoring Group or Custom Fieldlossy | Fully supported | |
| Custom Properties / Extended Fields | Custom Fields on Contact or Account1:1 | Mapping required |
Gotchas + challenges
Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.
Comarch Marketing Automation gotchas
Partner-managed enterprise deployments complicate data extraction
Automation journey logic does not export from Comarch
No publicly documented API rate limits for Comarch Marketing Automation
Data Import and Export Tools feature is tier-dependent
Loyalty program tier structures are often deeply customized
Freshsales gotchas
Freddy AI is Pro-tier only despite heavy marketing
Post-migration emails and sequences are disabled
Bot session credits are a one-time 500-session allocation
Phone credits charged per minute with no cap
File storage limits scale with plan tier
Pair-specific challenges
Migration approach
Discovery and tier verification
We audit the Comarch Marketing Automation deployment across tier (SMB/Mid-Market/Enterprise), loyalty program count, segment definitions, campaign volume, promotional offer catalog, engagement KPI records, and custom field inventory. We confirm whether the deployment is partner-administered and establish partner contact if required. On the Freshsales side, we verify the destination plan (Free/Growth/Pro/Enterprise) and confirm which custom field types and custom modules are available. The discovery output is a written migration scope and a destination Freshsales plan recommendation if upgrade is warranted.
Schema design and custom field provisioning
We design the Freshsales schema to receive Comarch loyalty data. This includes creating custom fields on Contact for tier level, points balance, enrollment date, engagement scores (churn, CLV, NPS), and any Comarch custom properties. If the customer has Enterprise Freshsales, we create custom modules for loyalty program definitions or promotional offer catalogs. We deploy the schema into the customer's Freshsales sandbox for validation before production migration begins.
Sandbox migration and reconciliation
We run a full migration into the Freshsales sandbox using production-like data volume. The customer's RevOps or marketing ops lead reconciles record counts (contacts in, segments in, offers in, KPIs in), spot-checks 25-50 random records against the Comarch source, and validates custom field mappings. Any corrections to field type mapping, segment logic, or loyalty rule representation happen here, not in production.
Extraction and transformation
We extract Comarch data through the available export method (API for enterprise tiers, partner-assisted extraction for lower tiers, or manual report downloads if API access is unavailable). We transform loyalty member records into Freshsales Contact format, loyalty tier data into custom fields or Freddy AI scoring groups, segments into Contact Groups, campaign metadata into Deals or Notes, and KPI records into custom numeric fields. We flag any records that fail transformation for manual review before production import.
Production migration in dependency order
We run production migration in record order: Contact custom fields and picklists deployed first, then Contacts (with external ID for dedupe), then Account links resolved, then Contact Groups populated from Comarch segment membership, then KPI custom fields updated per contact, then campaign metadata as Notes or Deals. Each phase emits a row-count reconciliation report before the next phase begins. We use Freshsales REST API with batch chunking and exponential backoff on rate-limit responses.
Cutover, validation, and automation rebuild handoff
We freeze Comarch writes during cutover, run a final delta migration of any records modified during the migration window, then enable Freshsales as the system of record. We deliver the automation journey inventory document to the customer's admin team with every Comarch campaign trigger, branch condition, and channel sequence documented for Freddy AI rebuild. We support a one-week hypercare window for reconciliation issues. We do not rebuild Comarch journey logic as Freshsales Freddy AI workflows inside the migration scope; that is documented separately for the customer's admin team.
Platform deep dives
Comarch Marketing Automation
Source
Strengths
Weaknesses
Freshsales
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Comarch Marketing Automation and Freshsales.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Comarch Marketing Automation: Not publicly documented; varies by enterprise contract.
Data volume sensitivity
Comarch Marketing Automation doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Comarch Marketing Automation to Freshsales migration scoping. Not seeing yours? Book a call.
Walk through your Comarch Marketing Automation to Freshsales migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationAdjacent paths
Other ways to leave Comarch Marketing Automation
Other ways to arrive at Freshsales
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.