Migrate from Comarch Marketing Automation to HubSpot

Comarch contact profiles map directly to HubSpot contacts. Comarch stores contact name, email, phone, job title, and engagement history — all of which map to HubSpot's standard contact properties. Comarch's loyalty tier and point balance migrate as HubSpot custom properties since HubSpot has no native loyalty module.

Comarch business partner accounts map to HubSpot companies. Comarch stores account name, domain, industry, employee count, and annual revenue — these map to HubSpot's company name, website, industry, number of employees, and annual revenue fields. Parent-child account hierarchies in Comarch map to HubSpot's parent company field.

Comarch campaign enrollment data — which campaigns a contact entered, enrollment date, and campaign status — migrates to HubSpot contacts as a series of custom properties tracking campaign names and enrollment dates. HubSpot's native campaigns track list membership and email metrics separately, so we preserve the enrollment record as a property for continuity.

Comarch loyalty tier levels (Bronze, Silver, Gold, Platinum, etc.) have no HubSpot native equivalent. FlitStack creates a tier_status custom property on HubSpot contacts and maps the tier value directly. This preserves the loyalty status for segmentation and reporting in HubSpot.

Comarch stores accumulated loyalty points per contact. These migrate to a loyalty_points custom numeric property on HubSpot contacts. HubSpot's workflow engine can reference this property for automation triggers, but the point redemption logic must be rebuilt in HubSpot workflows by your team, using HubSpot's workflow builder and related tools.

Comarch tracks contact engagement across email campaigns and website behavior. Open and click history migrates as custom datetime and count properties on HubSpot contacts. Active engagement signals (last email open, last website visit) map to HubSpot's contact properties for use in HubSpot's lead scoring model.

Comarch automation sequences and cross-region customer journey rules have no HubSpot equivalent and cannot migrate. FlitStack exports the Comarch automation definitions as a structured reference document your HubSpot admin uses to rebuild sequences in HubSpot workflows. Timeline and trigger logic must be recreated.

Comarch campaign metadata — campaign name, type (loyalty, promotional, lifecycle), start date, and end date — maps to HubSpot campaigns. HubSpot campaigns store list membership and email performance data, so campaign metadata is preserved for reference. This mapping ensures that all campaign timing information is available in HubSpot for reporting and segmentation purposes.

Comarch extended contact attributes — regional flags, segment codes, preference data — migrate as HubSpot custom contact properties. FlitStack creates these properties in HubSpot during setup and maps the data value-by-value. Custom property names are normalized to HubSpot's naming conventions (lowercase, no spaces).

Comarch contacts can have a primary account and secondary accounts. HubSpot contacts can associate to multiple companies via the associations model. FlitStack maps Comarch's primary account to HubSpot's primary company association and secondary accounts to additional HubSpot company associations on the contact.

Comarch user assignments on contacts map to HubSpot contact owners. FlitStack resolves Comarch user emails against HubSpot user emails — matched users receive the contact owner assignment. Unmatched users are flagged before migration so your team either invites them to HubSpot or reassigns records to a fallback owner.