Migrate your Mekari Qontak data
Indonesia-centric omnichannel CRM built around WhatsApp Business API, unifying messaging channels with embedded sales and service tools for teams operating in Southeast Asian markets.
In its favor
Why people choose Mekari Qontak
The signal that keeps Mekari Qontak on the shortlist. Sourced from G2, Capterra, and customer scoping calls.
WhatsApp Business API partnership credibility in Indonesia makes it the default choice for local teams needing verified business accounts and compliant messaging at scale.
Centralized omnichannel inbox unifies WhatsApp, Instagram, LINE, and Email into a single agent dashboard, eliminating context-switching across disconnected tools.
No-code chatbot builder lets sales and support teams create automated conversation flows without developer involvement, validated by multiple G2 reviewers praising its ease of use.
Built-in CRM with Deals and Tickets gives small and medium Indonesian businesses everything in one platform rather than stitching together multiple vendors.
Automation and reporting tools provide real-time KPIs and conversation analytics that help teams justify channel investment to stakeholders.
Frequent platform updates disrupt established workflows, with at least one reviewer noting significant time spent adapting to new UI patterns.
API integration support is slow and difficult to reach when custom webhook or two-way sync errors occur, particularly around WhatsApp message forwarding.
Daily and monthly broadcast quota limits throttle high-volume marketing campaigns, forcing customers to either split sends across days or upgrade tiers unexpectedly.
Indonesian Rupiah pricing creates currency conversion complexity and unpredictability for international teams or subsidiaries outside Indonesia.
Reasons to switch
Why people leave Mekari Qontak
The recurring reasons buyers give for replacing Mekari Qontak. Presented as facts, not knocks.
Platform scorecard
Strengths, weaknesses, and where Mekari Qontak fits
Grades across six dimensions, plus a SWOT-style view of where the platform shines and where it falls short.
SWOT — strengths, weaknesses, and use-case fit
Strengths
Weaknesses
Where it works
Where it struggles
Pricing tiers
Mekari Qontak pricing overview
Qontak uses a tiered SaaS model with packages for Broadcast, Sales Suite, Service Suite, and Qontak 360 (all-in-one). Pricing is sales-assisted for most tiers with starting prices in Indonesian Rupiah (Rp750,000/month for standalone Qontak) or USD equivalent on G2 ($105/month usage-based). The Omnichannel Starter tier offers a free trial with usage-based pricing after onboarding.
Omnichannel Starter
Tier 1 of 5
Free trial, then usage-based
What's included
Need help selecting your CRM?
Book a free 30 minute consultationPricing is informational. FlitStack AI does not bill on Mekari Qontak's schedule — see our quote-based pricing →
What gets migrated
Mekari Qontak object support
Object-by-object support for Mekari Qontak migrations. Per-pair details surface during scoping.
Contacts
Fully supportedContacts are the primary CRM object in Qontak. Both bulk and selective export are documented via the UI with 'Download All' and 'Download selected' options. We map standard Contact fields (name, phone, email) and custom Contact properties directly to destination CRM Contacts.
Deals
Mapping requiredDeals exist as a pipeline object but stage names and pipeline configuration vary by plan tier. We preserve Deal values and stage assignments but flag any pipeline customizations that need reconfiguration in the destination system.
Tickets
Mapping requiredTickets are used for customer service workflows. Status values and custom ticket fields require field-level mapping since Qontak uses an enumerated status model that differs from most standard CRMs.
Chatbot Flows
Mapping requiredChatbot flows are custom objects with Qontak-specific JSON schemas. We extract flow definitions and decision trees but note that the flow builder interface does not export in a portable format, requiring manual reconstruction in some destinations.
WhatsApp Templates
Mapping requiredApproved WhatsApp message templates are tied to the Qontak-hosted WABA account. Migrating templates requires a new WhatsApp Business API registration in the destination platform or a porting request to Meta.
Contacts Lists/Segments
Mapping requiredList membership and segmentation criteria are stored as separate objects. We export list definitions but note that dynamic segment membership recalculates based on current contact data, not historical snapshot values.
Workflow Automations
Mapping requiredAutomation rules (trigger conditions, action sequences, scheduled broadcasts) use a Qontak-specific workflow schema. We document the trigger-action structure but cannot import automations directly into non-Qontak platforms due to schema incompatibility.
Users/Agents
Mapping requiredAgent records include role assignments (Supervisor, Agent) and channel allocation rules. We map agent names and roles but preserve the Qontak-specific role hierarchy as a custom field in the destination CRM.
Broadcast Campaigns
Not in this platformEmail and WhatsApp broadcast campaign history (sent timestamps, delivery receipts) is stored in Qontak's channel layer, not accessible via the CRM API. We do not migrate historical campaign records as they cannot be exported reliably.
Attachments
Mapping requiredFile attachments in conversations are stored in Qontak's media CDN. We download attachments during migration and re-upload to the destination, but long-term media hosting in the destination depends on the target platform's storage limits.
Custom Properties
Mapping requiredCustom Contact and Deal properties are fully accessible via the Mekari API. We extract the full schema and migrate property values, but destination CRM field types may require conversion (e.g., Qontak dropdown to HubSpot option sets).
| Object | Support | Notes |
|---|---|---|
| Contacts | Fully supported | Contacts are the primary CRM object in Qontak. Both bulk and selective export are documented via the UI with 'Download All' and 'Download selected' options. We map standard Contact fields (name, phone, email) and custom Contact properties directly to destination CRM Contacts. |
| Deals | Mapping required | Deals exist as a pipeline object but stage names and pipeline configuration vary by plan tier. We preserve Deal values and stage assignments but flag any pipeline customizations that need reconfiguration in the destination system. |
| Tickets | Mapping required | Tickets are used for customer service workflows. Status values and custom ticket fields require field-level mapping since Qontak uses an enumerated status model that differs from most standard CRMs. |
| Chatbot Flows | Mapping required | Chatbot flows are custom objects with Qontak-specific JSON schemas. We extract flow definitions and decision trees but note that the flow builder interface does not export in a portable format, requiring manual reconstruction in some destinations. |
| WhatsApp Templates | Mapping required | Approved WhatsApp message templates are tied to the Qontak-hosted WABA account. Migrating templates requires a new WhatsApp Business API registration in the destination platform or a porting request to Meta. |
| Contacts Lists/Segments | Mapping required | List membership and segmentation criteria are stored as separate objects. We export list definitions but note that dynamic segment membership recalculates based on current contact data, not historical snapshot values. |
| Workflow Automations | Mapping required | Automation rules (trigger conditions, action sequences, scheduled broadcasts) use a Qontak-specific workflow schema. We document the trigger-action structure but cannot import automations directly into non-Qontak platforms due to schema incompatibility. |
| Users/Agents | Mapping required | Agent records include role assignments (Supervisor, Agent) and channel allocation rules. We map agent names and roles but preserve the Qontak-specific role hierarchy as a custom field in the destination CRM. |
| Broadcast Campaigns | Not in this platform | Email and WhatsApp broadcast campaign history (sent timestamps, delivery receipts) is stored in Qontak's channel layer, not accessible via the CRM API. We do not migrate historical campaign records as they cannot be exported reliably. |
| Attachments | Mapping required | File attachments in conversations are stored in Qontak's media CDN. We download attachments during migration and re-upload to the destination, but long-term media hosting in the destination depends on the target platform's storage limits. |
| Custom Properties | Mapping required | Custom Contact and Deal properties are fully accessible via the Mekari API. We extract the full schema and migrate property values, but destination CRM field types may require conversion (e.g., Qontak dropdown to HubSpot option sets). |
Gotchas
What to watch for in Mekari Qontak migrations
Issues we've hit on past Mekari Qontak migrations, tagged by severity. FlitStack AI handles every one — surfacing them up front because buyer engineering teams want to know.
WhatsApp Business API number offboarding requires manual support request
Broadcast quotas are enforced at account level, not campaign level
Marketing Messages API migration for WABA numbers registered after August 2025
Chatbot flow JSON is not portable between platforms
Frequent platform UI updates can rename or relocate export options
| Severity | Issue |
|---|---|
| High | WhatsApp Business API number offboarding requires manual support request |
| High | Broadcast quotas are enforced at account level, not campaign level |
| Medium | Marketing Messages API migration for WABA numbers registered after August 2025 |
| Medium | Chatbot flow JSON is not portable between platforms |
| Low | Frequent platform UI updates can rename or relocate export options |
Leaving Mekari Qontak?
Where Mekari Qontak customers move next
12 destinations Mekari Qontak can migrate to.
How a Mekari Qontak migration works
Four steps, Mekari Qontak-specific
Connect
HMAC authentication with client_id and client_secret into Mekari Qontak. Scopes limited to read-only on the data we move.
Map
We translate Mekari Qontak-specific structures (custom fields, objects, value lists) to the destination's model.
Sample
Test with a 50–200 record subset to validate Mekari Qontak quirks before production.
Migrate
Full migration with Mekari Qontak rate-limit handling. Rollback available throughout.
FAQ
Mekari Qontak migration FAQ
Answers to the questions buyers ask most during Mekari Qontak migration scoping. Not seeing yours? Book a call.
Can't find your answer?
Walk through your Mekari Qontak migration with a real engineer — 30 minutes, free, written quote within 24 hours.
Book a free 30 minute consultationReady when you are
Migrate Mekari Qontak.
Without the rebuild.
Free scoping call with a migration engineer. Tell us about your Mekari Qontak setup and destination — written quote back within a business day.