Migrate from Mekari Qontak to Microsoft Dynamics 365 Sales

Qontak Contacts with lifecycle stage set to subscriber, lead, or marketing qualified lead map to Salesforce Lead. Qontak Contacts with lifecycle stage set to customer or evangelist map to Salesforce Contact tied to an Account. We compute the split using Qontak's lifecycle_stage property during the transform phase, preserving the original stage value in a custom field qk_lifecycle_stage__c on both Lead and Contact for audit. Phone number format validation is applied since Qontak stores Indonesian mobile numbers with +62 prefix that Dynamics 365 may truncate without explicit field-level format handling.

Qontak Company records map directly to Salesforce Account. The company domain name becomes the Account Website field and serves as the deduplication key during import. Account is created before any Contact import so the AccountId lookup is satisfied at the moment of Contact insert. Parent-company hierarchies in Qontak map to Salesforce Account hierarchy.

Qontak Deals map to Salesforce Opportunity. Deal stage names from Qontak's enumerated list map to Salesforce StageName values after we configure the corresponding Sales Process and Record Type in Dynamics 365. Deal monetary values migrate directly. Any Qontak custom Deal properties map to custom Opportunity fields. We flag any pipeline customizations that require Record Type configuration since Qontak pipeline structure varies by plan tier.

Each Qontak pipeline becomes a Salesforce Record Type with a corresponding Sales Process that whitelists the relevant stage values. Stage probability percentages transfer from Qontak to Salesforce StageProbability. We handle the enumerated stage model in Qontak by mapping each named stage to the nearest Microsoft Dynamics 365 Sales process stage and document any stage values that have no direct equivalent.

Qontak Tickets migrate to Salesforce Case if the destination org includes Service Cloud. Ticket pipeline becomes Case Record Type, Qontak ticket status enumerations map to Salesforce Case Status values, and conversation threads migrate as EmailMessage records linked to the Case. Ticket custom fields map to Case custom fields. We flag whether Service Cloud licensing is required during scoping since it is not included in Sales Essentials or Sales Professional by default.

Qontak chatbot flows use an internal JSON schema that is not portable to Microsoft Dynamics 365 Sales , Power Automate, or any other platform. We extract the full decision tree structure including trigger conditions, branching logic, action nodes, and delay rules. We provide a written flow map with entity relationship references and re-build recommendations mapped to Power Automate cloud flow templates or Dynamics 365 custom page logic. This is a documentation deliverable, not an automated import.

Approved WhatsApp message templates are tied to the Qontak-hosted WABA account and cannot be transferred directly to Microsoft Dynamics 365 Sales or any other platform. We document the full template name, header/body/footer structure, approved variable placeholders, and language. The customer must register a new WhatsApp Business API account in the destination platform (or port the existing WABA number) and resubmit templates for Meta approval. We flag this as a post-migration administrative task.

Qontak agent records including role assignments (Supervisor, Agent) and channel allocation rules map to Salesforce User records matched by email address. Qontak-specific role hierarchy is preserved as a custom field qk_agent_role__c on the User record. Agents without a matching Dynamics 365 User go to a reconciliation queue for the customer's admin to provision before record import resumes.

Qontak custom Contact and Deal properties are fully accessible via the Mekari API and map to Salesforce custom fields. We pre-create destination field schema including data type mapping (Qontak text properties become Text fields, Qontak date properties become Date fields, multi-select Qontak properties become Multi-Select Picklist fields) before any data import. The destination field __c API name convention is applied per Salesforce standard.

File attachments stored in Qontak's media CDN are downloaded during migration and re-uploaded to the destination as Salesforce Files attached via ContentDocumentLink to the parent Contact, Account, or Opportunity record. Long-term media hosting in Dynamics 365 uses SharePoint or Dataverse file storage; the customer must confirm which is enabled in their environment before attachment migration.