Migrate from Mekari Qontak to HubSpot

Mekari Qontak contacts map directly to HubSpot contacts. Primary company association uses HubSpot's company link — if a contact has no primary company in Mekari Qontak, it lands as a standalone HubSpot contact without a company association.

Mekari Qontak tracks the first channel a contact came through. We create a HubSpot custom property (Channel_Source__c) and populate it with the Mekari Qontak channel value — WhatsApp, Instagram Direct, Email, Chat, Voice — so your team can filter and segment on acquisition channel post-migration.

Mekari Qontak companies map to HubSpot companies. Company hierarchies (parent/child) in Mekari Qontak map to HubSpot's parent company field. Multi-company associations on contacts are preserved via HubSpot's company associations feature — one primary company per contact with others linked as secondary associations.

Mekari Qontak deals map to HubSpot deals. Deal owner resolves by email match to HubSpot users. If a Mekari Qontak deal has no owner or the owner email doesn't match a HubSpot user, we flag the record for manual owner assignment before the full migration commits.

Mekari Qontak pipelines map to HubSpot deal pipelines. Stage names map value-by-value — if Mekari Qontak stage names don't match HubSpot's default stage labels, we create custom stage names in HubSpot's pipeline builder. Each pipeline becomes a separate HubSpot deal pipeline with its own stage order and probability weights.

Mekari Qontak support tickets map to HubSpot tickets via the Service Hub. Ticket status, priority, and assigned agent transfer to HubSpot ticket properties. If Mekari Qontak tickets use custom statuses beyond Open/Closed, we create matching HubSpot ticket pipeline stages and flag them for your admin's review.

Mekari Qontak custom fields on any object become HubSpot custom properties. We create the HubSpot custom property first, map the field type (text, number, date, picklist), and populate values. Picklist values require value-by-value mapping if the source values don't match HubSpot's default picklist options.

Mekari Qontak owner records (sales reps, agents) resolve by email match to HubSpot user accounts. We check each owner email against HubSpot's user list before migration — matched owners assign directly; unmatched owners are flagged in a pre-migration report so your team can either invite them to HubSpot or reassign records before data lands.

Mekari Qontak WhatsApp message logs migrate as HubSpot engagement records — calls with Type='Message' in the activity log — preserving original timestamp, contact link, and message direction (inbound/outbound). Full message body is stored in a custom long-text field since HubSpot's standard timeline doesn't display WhatsApp transcript content natively.

Mekari Qontak voice call records map to HubSpot call engagements with original duration, call outcome (answered, missed, voicemail), and timestamp preserved. Call recordings stored in Mekari Qontak's cloud storage are downloaded and re-uploaded to HubSpot's file storage, linked to the contact record.

Mekari Qontak live chat and Instagram Direct message threads migrate as HubSpot timeline notes — one note per conversation thread with start/end timestamp, channel label, and message snippet. Full chat transcripts are stored as HubSpot attachments for reference by agents reviewing contact history.

Mekari Qontak file attachments on contacts, companies, deals, and tickets are downloaded and re-uploaded to HubSpot Files. Linked to the corresponding HubSpot record by ID. File size limits per HubSpot's storage tier apply — files exceeding the limit are flagged for your admin to handle separately.

Mekari Qontak workflows, chatbot flows, and automation rules do not have a HubSpot equivalent that can carry configuration over. We export your Mekari Qontak workflow definitions as a structured document your HubSpot admin can use as a rebuild reference. HubSpot workflows must be recreated in HubSpot's workflow builder.

Mekari Qontak's WhatsApp Business API credentials and official number configuration are Mekari-specific and cannot transfer to HubSpot. Your team will need to connect your WhatsApp Business API to HubSpot separately. We document the phone number and WABA ID from Mekari Qontak for re-verification during HubSpot WhatsApp setup.