Migrate from Mekari Qontak to Zoho CRM

Qontak Contact records map to Zoho CRM Contact with all standard fields (Full Name, Email, Phone, Mobile) preserved. If Qontak stores a Company field on the Contact, we also create a corresponding Zoho Account and link via the Account Name lookup. Custom Contact properties migrate to Zoho custom fields with type conversion applied (Qontak dropdown to Zoho picklist, Qontak text area to Zoho multiline text). We deduplicate on email address during import and flag any duplicate Email addresses for admin resolution.

Qontak Company records map to Zoho CRM Account. The Qontak company domain becomes the Account Website field and serves as the dedupe key. If Qontak Contacts reference a Company without a separate Companies export, we create Accounts from the Contact.Company association during the Contact import phase. Account City, Country, and Industry map from Qontak Company fields with minor label adjustments.

Qontak Deals map to Zoho CRM Potentials with the Deal amount, closing date, owner, and pipeline stage preserved. Qontak pipeline stage names map to Zoho Potential Stage values during migration; we pre-create the Zoho pipeline layout with matching stage names before import. Deal custom properties (Closed-Lost reason, products associated, etc.) migrate as Zoho custom fields. If Qontak Deals reference a Contact, we create the Contact-Account-Potential linkage in Zoho at migration time.

Qontak pipeline configurations (stage names, probabilities, and stage order) are enumerated per plan tier. We pre-create the Zoho pipeline layout with matching stage names and configure probability percentages from Qontak's stage values before migration begins. If Qontak uses different pipelines per line of business, we create multiple Zoho CRM layouts with separate Pipeline assignments per Potential Record Type.

Qontak Tickets map to Zoho CRM Cases. The Ticket status enumerated list (e.g., Open, Pending, Resolved, Closed) maps to Zoho Case Status values. Qontak custom ticket fields migrate as Zoho Case custom fields. If the customer also licenses Zoho Desk for multi-channel service, Cases sync natively between CRM and Desk. Qontak conversation threads (WhatsApp message history linked to tickets) do not migrate as a structured object; we export conversation metadata and timestamps as a Case custom text field for admin reference.

Qontak chatbot flows export in a Qontak-internal JSON schema that is not portable to Zoho's chatbot framework. We extract the full decision tree structure (trigger conditions, branch logic, action sequences, and message content) into a detailed written flow map and rebuild recommendations. Zoho offers Zoho SalesIQ for chatbot capabilities, but the customer's admin rebuilds flows in the chosen tool post-migration. This object does not migrate as executable code.

Approved WhatsApp message templates in Qontak are tied to the Qontak-hosted WABA account and cannot be transferred to Zoho. We document the existing template content (header, body, footer, buttons) as a written inventory. The customer either registers a new WABA directly with Meta Business or via Zoho's WhatsApp Business integration for Zoho CRM, then submits templates for re-approval. Qontak templates cannot be imported into Zoho or reused without Meta re-verification.

Qontak agent records (name, email, role: Supervisor or Agent, channel allocation) map to Zoho CRM Users. We resolve agents by email match during migration. Qontak role assignments (Supervisor, Agent) map to Zoho Profiles and Roles, with Supervisor mapping to a role that includes visibility of team members' records. Any Qontak agent without a matching Zoho User is held in a reconciliation queue for the admin to provision before record import proceeds.

Qontak contact list definitions (list name, membership criteria, static vs dynamic) export as written documentation. Static list membership migrates as a Zoho CRM Tag on the relevant Contacts. Dynamic segments recalculate based on migrated contact data and are not preserved as historical membership snapshots; we document the segment criteria so the admin can recreate the dynamic filter in Zoho CRM Views. We do not migrate segmentation as active automation.

Qontak workflow automation rules (trigger conditions, action sequences, scheduled broadcasts) use a Qontak-specific schema that cannot import into Zoho Workflow Rules. We deliver a written inventory of every active Qontak automation with its trigger object, conditions, actions, and recommended Zoho Workflow Rule equivalent. The customer's admin rebuilds these in Zoho via Setup > Workflows. This inventory is a written deliverable, not an automated import.

Qontak custom Contact, Deal, Ticket, and Company properties fully accessible via the Mekari API migrate as Zoho CRM Custom Fields. We extract the full property schema during scoping, map Qontak field types to appropriate Zoho field types (e.g., Qontak multi-checkbox to Zoho multi-select picklist, Qontak date picker to Zoho date field), and pre-create all custom fields in the Zoho CRM layout before the main record import phase begins.