Migrate from Mekari Qontak to Mailchimp

Qontak Contacts migrate as Mailchimp Audience Members. Each Contact's email address becomes the subscriber_emailaddr; first name, last name, phone, and address fields map to Mailchimp's standard merge fields (FNAME, LNAME, PHONE, ADDRESS). We deduplicate by email address during import, using the most recently updated Qontak record as the authoritative version when duplicates are found. Opt-in status from Qontak (if available via custom property or list subscription flag) maps to Mailchimp's status field.

Qontak Companies have no direct Mailchimp equivalent — Mailchimp Audiences are flat subscriber lists without a native companies or accounts object. We store the company association as a Mailchimp merge field (COMPANY) on each member record, preserving the Account name for segmentation. Alternatively, if the customer uses multiple Qontak lists mapped to different companies, we map each list to a separate Mailchimp Audience and tag members by company for cross-audience analysis.

Qontak list membership and dynamic segment criteria export as Mailchimp Audiences (for static lists) or Segment definitions (for dynamic segments). Dynamic segment membership is recalculated in Mailchimp based on current contact data at the time of migration, not historical snapshot values. We document the original Qontak filter conditions (field, operator, value) as a written segment rebuild guide so the customer's marketing team can replicate the logic in Mailchimp's segment builder.

Qontak Deals (pipeline stages, deal values, probabilities, associated Contacts) have no Mailchimp equivalent because Mailchimp is an email marketing platform with no sales pipeline, opportunity, or deal tracking capability. We extract the Deal schema (pipeline names, stage values, custom fields) as a CSV inventory and export top-stage Deals as Contact merge fields or tags (e.g., HOT_PROSPECT, CLOSED_WON) for downstream segmentation. The customer manually recreates pipeline tracking outside Mailchimp if needed.

Qontak Tickets (status workflow, agent assignment, conversation threads) have no Mailchimp equivalent. We extract ticket status distribution as a written report for the customer's service team reference. If ticket contact associations need preservation, open ticket status maps to a Mailchimp contact tag (e.g., OPEN_TICKET) for segmentation purposes only — this is not a functional ticketing replacement.

Qontak chatbot flows use a platform-specific JSON schema that Mailchimp cannot import. We extract the full decision tree structure — trigger conditions, message blocks, conditional branches, and API actions — as a written flow map and re-build recommendations. The customer uses this document to configure equivalent logic in Mailchimp's automation builder or a third-party chatbot tool if WhatsApp messaging continues post-migration.

Qontak-hosted WhatsApp message templates are tied to the Qontak WABA account and cannot be transferred to Mailchimp. We export the complete template library (name, language, body content, header/footer/media components, status) as a JSON file and provide a written re-registration guide for Meta Business Manager. If the customer uses Marketing Message API templates registered after August 2025, we note this separately since the MM API template model differs from standard Cloud API templates.

Qontak custom Contact properties (text, number, date, dropdown, checkbox) map to Mailchimp merge fields. Text properties with fewer than 255 characters map directly; longer text properties are truncated to the Mailchimp merge field limit. Multi-select picklist values map to Mailchimp tags on the member record for segmentation. Date properties map to Mailchimp date merge fields. We pre-create the merge field schema in Mailchimp before contact import begins.

Qontak Workflows (trigger conditions, action sequences, scheduled broadcasts, auto-allocation rules) use a Qontak-specific automation schema that Mailchimp cannot import. We deliver a written automation inventory: each Qontak Workflow documented with its trigger (event-based or time-based), filter conditions, action sequence (send message, update field, assign agent, schedule follow-up), and recommended Mailchimp automation equivalent. The customer's marketing team rebuilds these in Mailchimp's automation builder post-migration.

Qontak agent records (name, email, role, channel allocation) have no Mailchimp equivalent. We export the agent directory as a CSV (name, email, role, status) for the customer's reference. Mailchimp's user model is account-level collaborators with audience-level permissions, not channel-assigned agents.