Migrate from Mekari Qontak to monday CRM

Qontak Contact records map to People items in Monday.com CRM's dedicated People Board. Standard fields (full name, phone number, email, address) map to the corresponding People column types. Qontak custom Contact properties map to additional columns in the People Board, with Qontak picklist values converted to Monday.com Status or Dropdown columns. Channel attribution (WhatsApp number, Instagram handle) migrates as text fields since Monday.com does not have a native channel attribution model. We resolve the People Board item by email match before import to prevent duplicate contacts.

Qontak Company records map to Monday.com CRM's Companies Board. Company name, domain, industry, employee count, and address fields map to equivalent columns in the Companies Board. The Company-Contact relationship is preserved by linking the People item to the Companies item via Monday.com's built-in People-Company link. If the customer uses Qontak's standalone Company records without individual Contact records, we create a Companies Board with one item per Company and add relevant custom properties as columns.

Qontak Deals map to Monday.com CRM's native Deals Board. Deal name, value, currency, expected close date, and stage migrate to the corresponding Deals Board columns. Qontak pipeline stage names map to Monday.com Deal Stage values, and we configure the stage sequence in the Deals Board before migration. Owner assignment from Qontak resolves to the Monday.com team member by email match. Custom Deal properties (beyond the standard set) migrate as additional columns on the Deals Board item.

Each Qontak pipeline and its associated stage values require mapping to Monday.com Deals Board stage configuration. Qontak stores stage names as enumerated lists that vary by plan tier. We document the current stage order and probability percentages from Qontak and configure equivalent stage labels and ordering in Monday.com Deals before the first Deal import. Any closed-won and closed-lost reasons stored as custom properties in Qontak become dropdown columns in Monday.com Deals.

Qontak Tickets migrate to board items in a Monday.com Service board we create during migration. Ticket subject becomes the item name, status values map to Status column options in the Service board, and agent assignments map to Assignee columns. Custom Ticket fields (priority, category, source channel) migrate as additional columns. The Ticket-Contact link is preserved by linking the Service board item to the corresponding People item in the CRM. If the customer uses Qontak's Ticket pipeline with multiple stages, we create a parallel stage structure in Monday.com's Status column.

Qontak agent records (Supervisor and Agent roles) map to Monday.com team members by email. We extract role assignments from Qontak and preserve them as a Role column on the People Board item for the agent's own contact record, since Monday.com does not have a native agent-role concept. Channel allocation rules from Qontak do not migrate as configuration; we document them for the customer's admin to reconfigure in Monday.com's team settings.

Qontak Contact Lists and Segments store membership and segmentation criteria as separate objects. We export list definitions (name, criteria logic, member count) as a written inventory. In Monday.com, dynamic segmentation is handled via Group filtering on the People Board; we document which Qontak list criteria maps to which group filter and recommend a static or dynamic group structure. List membership is recalculated at migration time against current contact data rather than preserved as historical point-in-time membership.

Chatbot flow definitions use Qontak's internal JSON schema and cannot be imported into Monday.com or any other platform. We extract the full decision tree structure (trigger conditions, response branches, integration actions) and deliver it as a documented flow map with rebuild recommendations. The customer uses the flow map to recreate logic in Monday.com's Workflow Automations or a third-party chatbot platform. This is a documentation deliverable, not an automated import.

Approved WhatsApp message templates are tied to the Qontak-hosted WhatsApp Business API account (WABA) number. The templates cannot be transferred to Monday.com automatically. We document every active Qontak template (name, category, body content, variable placeholders) and provide a re-registration guide for submitting them to Meta Business Manager directly. If the customer is also doing a WABA number port or new registration, we coordinate the timing with the offboarding request so template content is preserved before the Qontak WABA access is released.

File attachments stored in Qontak's media CDN are downloaded during migration and re-uploaded to Monday.com file storage attached to the relevant board item (People, Company, Deal, or Ticket). We preserve the original filename and attach date, and map the file to the appropriate Monday.com item via the API. Long-term media hosting in Monday.com is subject to the account's file storage limits; we flag any attachment volumes that approach the storage ceiling during scoping.

Qontak custom Contact and Deal properties are fully accessible via the Mekari API. We extract the full custom property schema (field name, data type, picklist values for enumerated types) and create equivalent custom columns in the corresponding Monday.com boards before import. Qontak multi-checkbox properties map to Monday.com Tags or Dropdown columns depending on whether multi-select is needed. Date, numeric, and text custom properties map directly to Monday.com column types.