Migrate from Mekari Qontak to Freshsales

Qontak Contacts map to Freshsales Contacts for customers with an existing relationship or deal history. Unqualified or early-stage prospects from Qontak (pre-Deal) map to Freshsales Leads. We determine the split by evaluating whether the Qontak Contact has an associated Deal, a dealstage assignment, or a tag indicating sales-qualified status. The original Qontak contact ID is preserved in a custom field qontak_id__c for reconciliation.

Qontak Deals map directly to Freshsales Deals with the dealstage value mapped to Freshsales Deal Stage. Qontak's pipeline assignment maps to Freshsales' pipeline selector on the Deal record. We extract closed-won and closed-lost values along with any custom deal properties and map them to Freshsales custom fields. Note that Freshsales Deals do not require an Account lookup by default, but we recommend linking each Deal to a Contact for full activity timeline continuity.

Qontak Tickets map to Freshsales Tasks for basic tracking, or to Freshdesk Cases if the customer licenses Freshdesk alongside Freshsales. Qontak's ticket status enumeration (Open, Pending, Resolved, Closed) maps to Freshsales Task status values or Freshdesk Case status values. Custom ticket fields from Qontak migrate as custom fields on the target object. Conversation history attached to Qontak Tickets migrates as a series of Task notes or Case EmailMessages depending on the destination.

Qontak custom Contact and Deal properties (text, number, date, dropdown) map to Freshsales custom fields. We extract the full Qontak property schema at scan time and pre-create matching custom fields in Freshsales before migration begins. Qontak multi-select or checkbox properties map to Freshsales multi-select picklist fields. Date and datetime fields preserve format. We flag any Qontak field type (e.g., formula fields) that cannot be computed in Freshsales and document them for manual data entry or calculation field creation.

Qontak chatbot flows are stored in a platform-specific JSON schema that is not portable to Freshdesk Conversation or any other platform. We extract the full decision tree structure, trigger conditions, and action sequences and deliver them as a documented flow map with annotated screenshots and logic notes. Your admin uses this documentation to rebuild conversation flows in Freshdesk Conversation's Bot Builder, which uses a different visual interface and trigger model.

Qontak agent records (name, email, role: Supervisor or Agent) map to Freshsales User accounts. We match by email address. Qontak-specific role hierarchy is preserved as a custom field qontak_role__c in Freshsales since Freshsales' native role model uses a different permission structure. Active Qontak agents require corresponding Freshsales user licenses provisioned before migration.

Qontak list membership and segmentation criteria are exported as static lists. We export the list names and the set of contact IDs in each list. In Freshsales, we create Static Lists with matching names and add members by contact ID lookup. Dynamic segment membership recalculates based on current contact data in Qontak and does not have a Freshsales equivalent; dynamic segments are documented with their filter criteria for manual list recreation.

Approved WhatsApp message templates are tied to the Qontak-hosted WABA account and cannot be transferred to Freshsales. We document the full template library (name, body content, variables, approved categories) and provide re-registration guidance through the WhatsApp Business Manager. Templates must be re-submitted for Meta approval in the customer's new WABA setup.