CRM migration
Field-level mapping, validation, and rollback between Mekari Qontak and Nutshell. We move data and schema; workflows are rebuilt natively in Nutshell.
Mekari Qontak
Source
Nutshell
Destination
Compatibility
5 of 8
objects map 1:1 between Mekari Qontak and Nutshell.
Complexity
BStandard
Timeline
3-5 weeks
Overview
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.
Every standard and custom field arrives verified.
AI proposes the map; you confirm before any record moves.
Parent–child, lookups, and ownership stay linked.
Calls, emails, meetings — with original timestamps.
Documents, uploads, and inline notes move with the record.
Why teams make this switch
Leaving
What's pushing teams away
Choosing
What's pulling them in
Object mapping
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
Nutshell
Person (People)
1:1Qontak 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
Nutshell
Account
1:1Qontak 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
Nutshell
Opportunity
1:1Qontak 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
Nutshell
Activity (Task)
1:manyQontak 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)
Nutshell
Custom Fields (People)
lossyQontak 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
Nutshell
Users
1:1Qontak 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)
Nutshell
File Attachments
1:1File 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
Nutshell
Lists
lossyQontak 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.
| Mekari Qontak | Nutshell | Compatibility | |
|---|---|---|---|
| Contact | Person (People)1:1 | Fully supported | |
| Company | Account1:1 | Fully supported | |
| Deal | Opportunity1:1 | Fully supported | |
| Ticket | Activity (Task)1:many | Fully supported | |
| Custom Properties (Contact) | Custom Fields (People)lossy | Fully supported | |
| Users/Agents | Users1:1 | Mapping required | |
| Attachments (Conversation Media) | File Attachments1:1 | Fully supported | |
| Contacts Lists/Segments | Listslossy | Mapping required |
Gotchas + challenges
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 gotchas
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
Nutshell gotchas
Contact tier limits enforced on import
No bulk API endpoint requires paginated extraction
Email sequences not exportable via API
Foundation plan disables key sales features
Pair-specific challenges
Migration approach
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.
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.
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.
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.
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.
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
Mekari Qontak
Source
Strengths
Weaknesses
Nutshell
Destination
Strengths
Weaknesses
Complexity grading
Standard CRM migration. 2 of 8 objects need a mapping; the rest are 1:1.
Overall complexity
Standard migration
Derived from compatibility, mapping clarity, API constraints, and data volume across Mekari Qontak and Nutshell.
Object compatibility
2 of 8 objects need a mapping; the rest are 1:1.
Field mapping clarity
Field mapping is derived from defaults — final spec confirmed during the sample migration.
Timeline complexity
8-object category — typical timelines run 2–7 days end-to-end.
API constraints
Mekari Qontak: Not publicly documented by Qontak; enforced at account level for broadcast quotas.
Data volume sensitivity
Mekari Qontak doesn't expose a bulk API — REST + parallelization used for high-volume runs.
Estimator
Rule-based pricing — no per-record fees, no manual quotes. Migrations over 2M records are scoped individually.
Step 1
Pick a category, then your source and destination platforms.
Category
FAQ
Answers to the questions buyers ask most during Mekari Qontak to Nutshell migration scoping. Not seeing yours? Book a call.
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 consultationAdjacent paths
Other ways to leave Mekari Qontak
Other ways to arrive at Nutshell
Ready when you are
Tell us record counts and timeline. We'll come back with a written quote inside 1 business day — no commitment, no sales pitch.