Migrate from Mekari Qontak to Odoo CRM

Qontak Contacts map to Odoo CRM Contacts with name, phone, email, and custom properties preserved. Qontak's role-based channel allocation (Supervisor, Agent assignments) migrates as a custom contact field rather than a native Odoo role object. Email and phone normalization happens during transform to match Odoo's required field formats. Any Qontak contact without an email or phone receives a placeholder contact_info field for admin review.

Qontak Companies map to Odoo Partner records with the Company Type = Company flag set. Qontak's company-level custom properties migrate to custom fields on the Partner. Company domain from Qontak becomes the Partner's website field and serves as the dedupe key during import to prevent duplicate company records.

Qontak Deals map to Odoo CRM Opportunities. The Qontak dealstage property maps to an Odoo Stage with probability percentage preserved. Pipeline assignment maps to an Odoo Sales Team and a Stage within that team. Closed-Won and Closed-Lost reasons from Qontak custom properties become Tags on the Opportunity in Odoo. We create the Odoo Stages before migration using the probability percentages from Qontak to ensure the pipeline reflects historical win/loss rates.

Each Qontak pipeline (Sales Suite or Qontak 360 tier) becomes an Odoo Sales Team with its own Stage sequence. Qontak stage probability values map to Odoo Stage probability percentages. If the customer uses multiple Qontak pipelines mapped to different business units, we configure corresponding Odoo Sales Teams so that deal assignment remains scoped per team.

Qontak Tickets map to Odoo Helpdesk Tickets if the customer enables the Odoo Helpdesk app alongside CRM. Ticket status values from Qontak's enumerated model map to Odoo Ticket Stage values. Custom ticket fields migrate to Odoo custom fields on the ticket model. If Helpdesk is not in scope, we map Tickets to Odoo Project Tasks with a 'Service' tag for classification.

Qontak Contact Lists and segmentation criteria are exported as list definitions with membership rules. We migrate static list membership as Odoo Contact Lists. Dynamic segment membership recalculates against migrated contact data post-import, not as historical membership; we document the original Qontak segment criteria for the admin to reconfigure as Odoo filters or saved filter groups.

Qontak agent records (name, email, role: Supervisor or Agent, channel allocation rules) map to Odoo User accounts. We match by email. Channel allocation rules from Qontak are preserved as a custom field on the Odoo User for admin reference; Odoo's native access rights groups (Sales / Administrator / Portal) are assigned based on the Qontak role.

Qontak chatbot flows are stored in Qontak-internal JSON schema and cannot be imported into Odoo CRM directly. We extract the full decision tree structure, including trigger conditions, branching logic, action nodes, and delay configurations, and document it as a written flow map with screenshots and JSON exports for the customer's Odoo admin or a chatbot implementation partner to rebuild using a third-party Odoo chatbot app or external platform.

Qontak-approved WhatsApp message templates are tied to the Qontak-hosted WABA account. Migrating templates requires either a new WhatsApp Business API registration in the destination platform or a porting request through Facebook Business Manager. We flag WABA number ownership and template inventory during scoping. If the customer intends to continue WhatsApp messaging via an Odoo-compatible WhatsApp Business API partner (e.g., Starfish, Twilio, or a Qontak alternative), we document the template names, categories, and content for re-registration under the new WABA.

Qontak automation rules (trigger conditions, action sequences, scheduled broadcasts) use a Qontak-specific workflow schema. We document every active automation with its trigger, conditions, actions, and recommended Odoo equivalent (server action, automated action, or Python code via Studio). The rebuild in Odoo is performed by the customer's Odoo admin or an Odoo implementation partner post-migration.

Qontak custom Contact and Deal properties are fully accessible via the Mekari API. We extract the full schema and migrate property values. Odoo field types require conversion: Qontak checkbox properties become Odoo Boolean fields, date properties become Odoo Date fields, and multi-select text becomes Odoo Char or dedicated selection fields depending on the option count. We create all custom fields via Odoo Studio or data migration script before record import.

File attachments in Qontak conversations stored in the Qontak media CDN are downloaded during migration. We re-upload attachments to Odoo as IrAttachment records linked to the parent Contact, Company, or Opportunity via the corresponding res_model and res_id. Long-term media hosting in Odoo relies on Odoo's attachment storage configuration (database or file system) which the customer's IT team sets during Odoo installation.