Migrate from Mekari Qontak to Pipedrive

Qontak Contacts map directly to Pipedrive Persons via the Mekari API export. We use the contact's primary email address as the dedupe key. Phone numbers migrate as the primary phone field with any additional numbers as custom_fields entries. The original Qontak contact_id is preserved in a custom field qontak_id__c for reconciliation. Any channel attribution (WhatsApp number, Instagram handle) that represents a preferred contact channel migrates as a custom text field since Pipedrive has no native preferred-channel concept.

Qontak Companies map to Pipedrive Organizations. The Qontak company domain_name or website becomes the Organization's Website field and is used as a dedupe candidate alongside name. Organization is created before Person import so that the person-org link is satisfied at insert time. If Qontak has no company on a Contact record, we create a stub Organization named after the Person's email domain for linkage consistency.

Qontak Deals map to Pipedrive Deals with the pipeline stage mapping resolved before migration. Qontak plan tiers affect which stage names are available; we extract the customer's current pipeline configuration via the Mekari API and map each Qontak stage name to a Pipedrive Pipeline stage. Deal value, expected_close_date, owner_id, and custom deal properties migrate directly. The Qontak deal_id is preserved in a custom field qontak_deal_id__c for audit.

Each Qontak pipeline becomes a Pipedrive Pipeline. Qontak stage status values (open, won, lost) map to Pipedrive status values (open, won, lost) with stage probability percentages preserved as Pipedrive probability values per stage. We configure the Pipedrive Pipeline in the destination account before Deal import begins so that stage assignment is valid at insert time.

Qontak Tickets represent customer service interactions and migrate to Pipedrive as a custom object or as Note/Activity entries on the linked Contact or Organization depending on whether the destination Pipedrive account has Service Cloud enabled. Ticket status values (open, pending, resolved, closed) map to custom picklist values or Activity status fields. If the customer uses Qontak Tickets for post-sale support tracking, we recommend Pipedrive's built-in Lead object for new inquiries rather than Ticket migration.

Qontak custom Contact and Deal properties fully accessible via the Mekari API migrate to Pipedrive custom fields. Field types require conversion: Qontak multi-checkbox properties become Pipedrive multi-select custom fields; Qontak date fields map to Pipedrive date fields; Qontak numeric fields map to Pipedrive numeric fields with precision preserved. We create all destination custom fields via Pipedrive's custom fields API before data import begins.

Qontak agent records (with Supervisor and Agent role assignments) map to Pipedrive Users. We resolve agents by email match. Qontak role hierarchy (Supervisor vs Agent) is preserved as a custom field agent_role__c in Pipedrive. Any Qontak agent without a matching Pipedrive User goes to a reconciliation queue for the customer's admin to provision before record import resumes.

Qontak contact list membership is exported as a per-list custom field on each Contact (list_name: true) so that list membership is queryable in Pipedrive. Dynamic segment membership recalculates based on current contact data after migration; we document the original segment filter criteria as a custom text field on the Organization or Person for the customer's admin to rebuild as a Pipedrive filter or segment.

Chatbot flows use Qontak's internal JSON schema and are not portable between platforms. We extract the full decision tree structure, trigger conditions, and action definitions from the Mekari API and deliver a detailed flow map with re-build recommendations for Pipedrive. The customer rebuilds chatbot logic in their chosen platform (Pipedrive does not have a native chatbot builder; this typically moves to a dedicated chatbot platform or is handled via Pipedrive's workflow automation triggers).

Approved WhatsApp message templates are tied to the Qontak-hosted WABA account and cannot be transferred to Pipedrive. We document all active and approved templates (name, language, header/footer/body structure, sample values) so the customer's admin can resubmit templates through the destination platform's WhatsApp Business API registration. New template registration in the destination platform follows Meta's standard WABA approval workflow.

Email and WhatsApp broadcast campaign history (sent timestamps, delivery receipts, open rates) is stored in Qontak's channel layer and is not accessible via the Mekari CRM API. We do not migrate historical broadcast records. We export a summary table of campaign names, send dates, and contact list sizes as a reference document for the customer's admin to re-create campaign context in Pipedrive or a dedicated marketing platform.