Migrate from Mekari Qontak to HighLevel

Qontak Contacts map directly to GoHighLevel Contacts. Standard fields (name, phone, email, address) map to their GoHighLevel equivalents. Custom Contact properties from Qontak map to GoHighLevel Contact custom fields, with data type conversion applied: Qontak multi-select picklist properties become GoHighLevel multi-select custom fields, date properties map to GoHighLevel date fields, and numeric properties map to GoHighLevel number fields. Phone number field is used as the dedupe key during import to prevent duplicate contacts.

Qontak Company records map to GoHighLevel Companies. The Qontak company name becomes the Company name field, domain becomes Website, and associated custom properties migrate to GoHighLevel Company custom fields. Qontak's company type and industry enumerated fields map to GoHighLevel picklist fields with the same value sets.

Qontak Deals map to GoHighLevel Opportunities. The Qontak pipeline and dealstage map to a GoHighLevel pipeline and stage. We create the GoHighLevel pipeline stages before migration to match the Qontak stage names and probabilities. Deal value, close date, and associated contacts migrate as Opportunity fields. Any Qontak deal custom properties map to GoHighLevel Opportunity custom fields.

Qontak Tickets map to GoHighLevel Tasks using a dedicated migration mode that maps ticket fields to Task fields: ticket subject becomes Task name, ticket description becomes Task body, Qontak ticket status (Open, In Progress, Resolved) maps to GoHighLevel Task status values, and priority maps to Task priority. If the customer uses GoHighLevel's native ticketing feature, we map to that object instead and create the ticket status pipeline before import.

Qontak static contact lists and dynamic segments require two handling paths. Static list membership migrates as a Tag on each GoHighLevel Contact, preserving the list name as the tag value. Dynamic segment membership recalculates in GoHighLevel based on current Contact field values; we export the segment definition (filter criteria) as a written document for the customer to recreate using GoHighLevel's Smart List filters.

Qontak agent records (Supervisor, Agent roles with channel allocation rules) map to GoHighLevel Users for active agents. We resolve by email match. Any Qontak agent without a matching GoHighLevel User is held in a reconciliation queue for the customer's admin to provision. Qontak role hierarchy and channel allocation rules are documented as a written spec for manual recreation in GoHighLevel team settings.

Qontak custom Contact and Deal properties migrate to GoHighLevel Contact custom fields and Opportunity custom fields respectively. We extract the full custom property schema from Qontak at scan time, match each property to the correct GoHighLevel custom field type (text, number, date, picklist, multi-select), and pre-create the GoHighLevel custom fields before data import begins.

Qontak chatbot flows use a proprietary JSON schema that is not portable to GoHighLevel's automation builder. We extract the full decision tree structure, trigger conditions, message content, and conditional branching logic as a detailed flow map document. GoHighLevel's Workflow builder is the recommended rebuild target. The flow map includes recommended trigger equivalents, action blocks, and delay sequences that map to GoHighLevel's visual automation model.

Approved WhatsApp message templates are tied to the Qontak-hosted WABA account and cannot be transferred directly to GoHighLevel. We document all approved templates (header, body, footer, buttons, variables) from the Qontak WABA. The customer must register a new WhatsApp Business API number in GoHighLevel (or port the existing number if eligible) and submit templates for WhatsApp re-approval through the GoHighLevel-connected Meta Business Manager.