CRM migration

Migrate from Mekari Qontak to Nutshell

Field-level mapping, validation, and rollback between Mekari Qontak and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.

Mekari Qontak logo

Mekari Qontak

Source

Nutshell

Destination

Nutshell logo

Compatibility

63%

5 of 8

objects map 1:1 between Mekari Qontak and Nutshell.

Complexity

BStandard

Timeline

3-5 weeks

Rollback included Accuracy guarantee Field-level validation

Overview

What this migration involves

Moving from Mekari Qontak to Nutshell is a replatforming from an Indonesia-centric omnichannel CRM built around WhatsApp Business API to a straightforward B2B sales CRM priced in USD with unlimited contact storage. The structural shift is significant: Qontak bundles Deals and Tickets as separate pipeline objects with an enumerated status model that varies by plan tier, while Nutshell uses a unified Account and Person (Contact) model with Opportunity as its sole deal-tracking object. We resolve that mapping during scoping, preserve ticket status history as Nutshell Activity records, and document the automation and chatbot flow structure for the customer's admin to rebuild. Qontak's HMAC-authenticated API, daily broadcast quotas, and the WABA number offboarding process are the three operational constraints we handle as part of the migration rather than leaving to the customer.

Field-level fidelity

Every standard and custom field arrives verified.

Schema-aware mapping

AI proposes the map; you confirm before any record moves.

Relationships preserved

Parent–child, lookups, and ownership stay linked.

Full activity history

Calls, emails, meetings — with original timestamps.

Attachments & notes

Documents, uploads, and inline notes move with the record.

Why teams make this switch

Two sides of the same decision

Leaving

Mekari Qontak logo

Mekari Qontak

What's pushing teams away

  • 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.

Choosing

Nutshell logo

Nutshell

What's pulling them in

  • Lowest cost entry point among mid-market CRMs—Foundation plan starts at $13/user/month, making it accessible for teams validating CRM fit before committing.
  • Integrated sales automation and email sequencing on Pro plans without requiring a separate email marketing platform, per verified Capterra reviews.
  • Consistently praised for intuitive interface and fast onboarding, with case studies reporting 100% team adoption rates within initial deployment periods.
  • Strong customer support responsiveness cited across G2 reviews, with dedicated support tiers available on Enterprise plans.
  • Native integrations with WhatsApp, Facebook Messenger, Instagram, and Slack reduce reliance on third-party middleware for common communication channels.

Object mapping

How Mekari Qontak objects map to Nutshell

Each row shows how a Mekari Qontak object lands in Nutshell, including any object-level transformations, lookup resolution, or schema-design dependencies.

Typical mapping — final map is confirmed during the sample migration step.

Mekari Qontak

Contact

maps to

Nutshell

Person (People)

1:1
Fully supported

Qontak Contacts map to Nutshell People records. The primary key mapping uses email address as the dedupe anchor; phone number serves as secondary anchor for contacts without email. Custom Contact properties in Qontak map to Nutshell custom fields on People, with type conversion applied: Qontak date pickers become Nutshell date fields, checkbox properties become Nutshell checkboxes, and multi-select or tag-based properties become Nutshell text fields with semicolon-separated values. The original Qontak contact ID is preserved in a custom field qontak_id__c for audit and cross-reference.

Mekari Qontak

Company

maps to

Nutshell

Account

1:1
Fully supported

Qontak Companies map to Nutshell Accounts. Qontak's company domain property becomes the Account Website field. Qontak's industry and company size properties map to Nutshell custom fields on Account since Nutshell Accounts do not have native industry or size fields. Account is created before any Person import so that the Person-to-Account link is satisfied at insert time.

Mekari Qontak

Deal

maps to

Nutshell

Opportunity

1:1
Fully supported

Qontak Deals map to Nutshell Opportunities with the Account lookup resolved from the associated Qontak Company. Qontak dealstage values map to Nutshell stage values (Prospecting, Qualification, Proposal/Price Quote, Negotiation, Closed Won, Closed Lost) based on the customer's specific Qontak pipeline stage names. The deal amount, expected close date, and owner all migrate directly. Qontak pipeline is captured as a custom Opportunity field pipeline_name__c to preserve multi-pipeline context when Qontak Sales Suite or Qontak 360 was used.

Mekari Qontak

Ticket

maps to

Nutshell

Activity (Task)

1:many
Fully supported

Qontak Tickets map to Nutshell Activity records (Task type) linked to the Person and Account. Qontak ticket status (Open, Pending, Resolved, Closed) becomes a custom Activity field ticket_status__c; Qontak ticket priority becomes a custom field ticket_priority__c. The Qontak ticket ID is preserved as ticket_id__c. Multiple Qontak tickets for the same Contact merge into individual Activity records, one per ticket, preserving the full ticket history as a timeline rather than a single summary field. This approach is chosen because Nutshell does not have a native ticket object equivalent to Qontak's Service Suite.

Mekari Qontak

Custom Properties (Contact)

maps to

Nutshell

Custom Fields (People)

lossy
Fully supported

Qontak custom Contact properties are extracted from the Mekari API with their field types preserved. Nutshell supports custom fields on People, Companies, and Activities via its field builder (text, number, date, checkbox, dropdown). We pre-create all destination custom fields via the Nutshell API before importing data, converting Qontak field types to the closest Nutshell equivalent. Qontak multi-checkbox properties (from tags or segmentation) become Nutshell text fields with comma-separated values unless the customer requests a different format during scoping.

Mekari Qontak

Users/Agents

maps to

Nutshell

Users

1:1
Mapping required

Qontak Agent records (with Supervisor and Agent role assignments) map to Nutshell Users by email match. Qontak role hierarchy is preserved as a custom field qontak_role__c on the Nutshell User since Nutshell's role model uses a simpler active/inactive/integrator pattern. Any Qontak Agent without a matching Nutshell User email goes to a reconciliation queue for the customer's admin to provision before the Person and Activity import begins.

Mekari Qontak

Attachments (Conversation Media)

maps to

Nutshell

File Attachments

1:1
Fully supported

File attachments stored in Qontak's media CDN are downloaded during the export phase and re-uploaded to Nutshell as file attachments on the relevant Person or Activity record. Long-term media hosting becomes the customer's responsibility in Nutshell since Nutshell stores attachments on its own file system without a separate CDN layer. We flag any attachments exceeding Nutshell's size limits for manual handling during the handoff phase.

Mekari Qontak

Contacts Lists/Segments

maps to

Nutshell

Lists

lossy
Mapping required

Qontak list membership and segmentation criteria are exported as structured definitions. Since Nutshell does not have a native dynamic segment object, list membership is re-created in Nutshell using a combination of saved filters (People filters by custom field values) documented during migration. Dynamic segment logic that recalculates based on current contact data does not carry over as an active rule; we document the criteria for the customer's admin to configure equivalent Nutshell filters manually.

Gotchas + challenges

What specifically takes care here

Platform-specific issues from each side, plus the pair-specific challenges that don't show up on either platform's page on its own.

Mekari Qontak logo

Mekari Qontak gotchas

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

Nutshell logo

Nutshell gotchas

High

Contact tier limits enforced on import

Medium

No bulk API endpoint requires paginated extraction

Medium

Email sequences not exportable via API

Medium

Foundation plan disables key sales features

Pair-specific challenges

  • WABA number offboarding requires manual Qontak support request before export

    When migrating away from Qontak, the WhatsApp Business API number associated with the account cannot be transferred to another CRM provider or registered independently without Qontak submitting the offboarding request on the customer's behalf. The process requires emailing [email protected] with company details and waiting for manual confirmation. We handle this request on the customer's behalf and sequence the contact and conversation history export before the WABA access is released, because losing the WhatsApp API endpoint also cuts off access to conversation history via the Mekari API. The customer's admin should not cancel the Qontak account until we confirm the export is complete.

  • Qontak broadcast quotas throttle bulk contact export during migration

    Qontak enforces daily and monthly email and WhatsApp broadcast limits at the account level regardless of the customer's remaining monthly budget. A customer who hits the daily export quota during migration cannot trigger additional bulk operations until the window resets. We scan the current quota headroom during discovery, chunk large contact imports into sub-quota batches, and use the Mekari API as the primary export channel rather than the UI-based download, which is not subject to the same daily envelope limits. Any migration that encounters a mid-export quota error is paused, the error is logged, and the import resumes once the quota window clears.

  • Chatbot flows and automation rules are not portable to Nutshell

    Qontak's no-code chatbot builder exports conversation logic in an internal JSON schema that cannot be imported into Nutshell, which does not have a native chatbot builder. We extract the full decision tree structure as a written flow map with trigger conditions, decision nodes, action sequences, and conditional branches documented for the customer's admin to rebuild in a third-party chatbot platform (Landbot, Landbot.io, or similar) or as Nutshell workflow rules if the team uses the Nutshell CRM for lightweight automation only. Workflow automation rules face the same constraint: Qontak's trigger-action schema does not map to Nutshell's rules engine and must be rebuilt.

  • Marketing Messages API format changes for Qontak accounts registered after August 2025

    Starting August 20, 2025, new WABA registrations through Qontak default to the Marketing Messages API, which changes the message limit model and delivery reporting structure. We detect whether the source account uses MM API at scan time and adjust the conversation history export format accordingly. MM API conversation records include additional delivery optimization metadata not present in Cloud API exports, and we preserve this as a custom Activity field wa_delivery_optimization__c rather than discarding it.

Migration approach

Six steps for a successful Mekari Qontak to Nutshell data migration

  1. Discovery and quota audit

    We audit the Qontak account via the Mekari API and UI, capturing Contact volume, Deal volume, Ticket volume, custom property schema, pipeline stage names, agent count, and broadcast quota headroom. We verify the WABA number status (Cloud API vs MM API) and confirm whether the account has been migrated to the Marketing Messages API. This scan determines the export batch sizing strategy and whether the MM API export format adjustment is required. We also identify any Qontak plan-tier constraints that affect API access depth.

  2. Nutshell schema configuration

    We create all required Nutshell custom fields on People, Accounts, and Activities before any data import, matching Qontak custom property names to Nutshell field labels with the closest equivalent data types. We configure the Opportunity stages based on the Qontak pipeline stage mapping defined during discovery. We create the Nutshell User accounts (or confirm existing ones) for each Qontak Agent, preserving the Qontak role as a custom User field. The Nutshell API is used for all schema provisioning.

  3. Sandbox migration and reconciliation

    We run a full migration into a Nutshell trial or development account using production-equivalent data volume. The customer's team lead spot-checks 20-30 records (a mix of People, Accounts, Opportunities, and Activity history) against the Qontak source, verifies field mapping accuracy, and confirms the ticket-to-Activity reconstruction is legible. Any mapping corrections are made before production migration begins. This step also validates that Nutshell's file attachment limits accommodate the migrated media.

  4. WABA offboarding and production export

    We submit the WABA offboarding request to [email protected] on the customer's behalf, confirm receipt, and run the full data export (Contacts, Companies, Deals, Tickets, Attachments) before the offboarding is processed. We use the Mekari API with HMAC authentication, chunking exports to respect broadcast quota headroom and handling 429 rate-limit responses with exponential backoff. Conversation history and ticket descriptions are exported as structured JSON with activity timestamps preserved for timeline reconstruction.

  5. Production migration in dependency order

    We run production migration in record-dependency order: Accounts (from Qontak Companies), People (with Account lookup resolved), Opportunities (with AccountId and OwnerId resolved), Activities (ticket history reconstructed from Qontak Tickets into Nutshell Tasks), and Attachments (re-uploaded to the relevant Person or Activity). Each phase emits a row-count reconciliation report before the next phase begins. Any records rejected due to Nutshell validation rules are logged and retried with corrected data.

  6. Cutover, validation, and automation handoff

    We freeze Qontak writes during cutover, run a final delta migration of any records modified during the migration window, then enable Nutshell as the system of record. We deliver the automation and chatbot flow documentation to the customer's admin team, including trigger-action inventories for every active Qontak workflow and a structured chatbot flow map with rebuild recommendations. We support a five-business-day hypercare window for reconciliation issues. We do not rebuild Qontak automations as Nutshell workflow rules inside the migration scope.

Platform deep dives

Context on both ends of the pair

Mekari Qontak logo

Mekari Qontak

Source

Strengths

  • Official WhatsApp Business API partner with verified badge support for Indonesian businesses
  • Unified inbox across WhatsApp, Instagram, LINE, Telegram, Email, and LiveChat in a single agent view
  • No-code chatbot builder with visual flow editor praised by multiple reviewers for ease of use
  • Embedded CRM (Contacts, Deals, Tickets) reduces need for separate sales stack
  • Built-in automation for message scheduling, auto-allocation, and follow-up sequences

Weaknesses

  • HMAC-only API authentication limits integration flexibility compared to OAuth 2.0 platforms
  • Frequent UI updates create ongoing learning curve for agent teams
  • Daily and monthly broadcast quotas are restrictive for high-volume marketing use cases
  • Pricing in Indonesian Rupiah complicates cost estimation for international teams
  • Limited public API documentation compared to global CRM platforms
Nutshell logo

Nutshell

Destination

Strengths

  • Simple, intuitive interface with minimal learning curve for sales teams new to CRM
  • Per-seat pricing is transparent and predictable, with annual billing reducing monthly cost
  • Full data export tool available for all account data including backups
  • Open JSON-RPC API allows programmatic access to all core objects
  • Native multichannel engagement (email, SMS, WhatsApp) without third-party add-ons for communication

Weaknesses

  • Reporting and analytics are considered weak, requiring manual Excel exports for detailed analysis
  • No bulk API endpoint—migration requires paginated API reads that must be rate-limited carefully
  • JSON-RPC API is less common than REST, requiring custom integration code compared to standard REST CRMs
  • Add-on costs (Forms, Nutshell IQ, Email Marketing) are per-company charges that stack on top of per-seat pricing
  • Feature restrictions on entry-level plans mean teams often need mid-tier to get basic automation

Complexity grading

How hard is this migration?

Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.

B

Overall complexity

Standard migration

Derived from compatibility, mapping clarity, API constraints, and data volume across Mekari Qontak and Nutshell.

  • Object compatibility

    B

    2 of 8 objects need a mapping; the rest are 1:1.

  • Field mapping clarity

    C

    Field mapping is derived from defaults — final spec confirmed during the sample migration.

  • Timeline complexity

    B

    8-object category — typical timelines run 2–7 days end-to-end.

  • API constraints

    B

    Mekari Qontak: Not publicly documented by Qontak; enforced at account level for broadcast quotas.

  • Data volume sensitivity

    B

    Mekari Qontak doesn't expose a bulk API — REST + parallelization used for high-volume runs.

Estimator

Estimate your Mekari Qontak to Nutshell migration cost

Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.

Step 1

What are you migrating?

Pick a category, then your source and destination platforms.

Category

FAQ

Frequently asked questions about Mekari Qontak to Nutshell data migrations

Answers to the questions buyers ask most during Mekari Qontak to Nutshell migration scoping. Not seeing yours? Book a call.

Can't find your answer?

Walk through your Mekari Qontak to Nutshell migration with a real engineer — 30 minutes, free, written quote within 24 hours.

Book a free 30 minute consultation

Most migrations land between three and five weeks for accounts under 10,000 Contacts, 2,000 Deals, and 1,000 Tickets with a straightforward stage mapping. Migrations with large ticket histories (over 5,000 support records), multi-pipeline Qontak setups requiring stage normalization, or accounts using the Marketing Messages API that requires export format adjustment move to six to ten weeks. The WABA offboarding request adds one to two weeks of lead time before the export can be safely sequenced.

Adjacent paths

Related migrations to explore

Ready when you are

Move from Mekari Qontak.
Land in Nutshell, intact.

Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.

Accuracy guarantee Rollback included Quote in 1 business day