Migrate from Comarch Marketing Automation to Nutshell

Comarch stores member profiles with loyalty attributes, transaction history, and engagement scores. We extract these records as structured People objects in Nutshell. Loyalty tier, enrollment date, points balance, and engagement score migrate to custom fields on the People record. Where Comarch stores member IDs with a loyalty prefix, we preserve the original Comarch ID in a custom identifier field for audit and reconciliation. Comarch's GDPR-aligned contact data migrates to Nutshell's People records with email opt-out status preserved in Nutshell's standard unsubscribe field.

Comarch segments built from AI-driven analysis and rules-based filtering export as segment definitions and member lists. We export both the segment rules documentation and the member ID list. Segment membership maps to Nutshell Lists, and Comarch's AI-driven segment criteria are documented as a rebuild checklist for the admin to recreate using Nutshell's filter and list-building features. Static segment lists migrate as Nutshell Lists with direct People membership.

Comarch campaign journeys export as campaign metadata records and audience lists. We map Comarch campaign names, send dates, channel assignments (email, SMS, push), and send volumes to Nutshell Campaign records. The audience list migrates as a Nutshell Target linked to the Campaign. The journey automation logic (branching conditions, time delays, channel routing, and AI-driven send-time optimization) is stored in Comarch's proprietary format and does not export; we document every active journey as a rebuild checklist for the admin.

Comarch promotional offer definitions include discount rules, eligibility criteria, and temporal constraints. We export offer definitions as structured records and map eligibility data to Nutshell custom fields on People. Offer terms and promotional period dates migrate to custom date fields and text fields, with a note field documenting the original Comarch offer logic for the admin to rebuild using Nutshell's email templates and basic automation rules.

Comarch KPIs including growth rate, churn rate, average transaction value, CLV, engagement index, enrollments, and NPS export as numeric records tied to member IDs. We map each KPI to a corresponding Nutshell custom field on the People record or Company record, preserving the original Comarch metric name and source timestamp. Historical KPI trend data migrates as a structured text or JSON custom field if multi-period data is available in the export.

Enterprise Comarch deployments frequently extend the data model with custom fields for industry-specific attributes. We export all custom property definitions alongside record data. We create equivalent Nutshell custom fields for People, Companies, and Leads during the schema setup phase, matching Comarch field types to Nutshell field types (text, number, date, dropdown). Any Comarch custom field type without a direct Nutshell equivalent is mapped to text and flagged for admin review.

Nutshell has no native loyalty management module, so Comarch loyalty program structures require a redesign using Nutshell's available primitives. We document Comarch program metadata, tier structures (Bronze, Silver, Gold, Platinum, or custom), earning rules, and redemption logic as a written redesign brief. The brief maps each Comarch loyalty concept to a Nutshell equivalent: tier names become Tags on People records, earning rules become custom formula fields or documentation notes, and redemption history migrates as a custom field. The admin implements the redesign post-migration using the provided brief as a guide.

Comarch EDI and ERP integrations are configured at the account level for B2B wholesale workflows. We export integration endpoint configurations as structured documentation (endpoint URLs, authentication types, mapping rules, and test credentials). Nutshell's native integrations cover QuickBooks, Xero, Mailchimp, and 100+ apps via Zapier, but EDI and custom ERP connections are not natively supported. We document which Comarch EDI integrations the customer uses and provide a rebuild guide mapping each connection to either a Nutshell-supported integration or a recommended middleware approach. The admin executes the integration rebuild post-migration.