YundaDeskThe hardest part of switching support software is rarely the purchase decision. It is the move. Owners want the new system to catch customers faster. Agents worry about losing old conversations, macros and customer context.
A good migration lets the new system inherit what the team already knows: the knowledge base feeds the AI agent, historical conversations become test cases, and every channel lands in one workspace. Use this checklist in order.
Define the migration scope: what moves and what gets archived
Do not start with “move everything.” Full migration sounds safe, but it often drags expired policies, discontinued products, unused channels and duplicate customer records into the new system.
Split assets into three groups:
| Type | Recommended handling | Examples |
|---|---|---|
| Must move | Import and verify before launch | Current policies, best-selling SKU FAQs, active customer records, conversations from the last 6 to 12 months |
| Archive | Keep searchable, but exclude from default AI knowledge | Old campaigns, discontinued SKUs, historical complaint files |
| Drop | Do not migrate; keep only in old-system backup | Expired auto-replies, duplicate tags, unused macros |
The goal is a clean starting point. For AI support, answer quality depends on what the system can read. If old wrong scripts move into the new knowledge base, the new system will simply repeat old mistakes faster.
Switching Support Software: start platform evaluation with the market shift
Move the knowledge base first: give AI evidence from day one
In a support software migration, the knowledge base should come before interface polishing. For an AI agent, the knowledge base is not a document cabinet. It is the evidence used to answer customers.
Organize it in four layers:
- Policy layer: shipping times, delivery countries, return conditions, warranty and customs notes.
- Product layer: sizing, materials, compatibility, usage steps, installation and common misunderstandings.
- Process layer: order lookup, address changes, shipping nudges, cancellations and what information to collect for after-sales requests.
- Boundary layer: for refunds, compensation, price changes and escalated complaints, AI may calm the customer and collect context, but must hand off for human approval.
The import can be simple: upload documents, crawl website pages, and add manual Q&A. Each item should be traceable, testable and revertible when something is wrong. In YundaDesk, the knowledge base is the foundation that feeds the AI agent. Later, when agents correct AI or answer what AI missed, those items become learning suggestions that an owner confirms before they take effect.
That is the difference between “gets smarter over time” and ordinary auto-replies. AI does not quietly rewrite business rules by itself. The team turns experience into skills, then a human approves them. For the full mechanism, see teaching AI that gets smarter.
Use historical conversations as a test set, not just a backup
Many teams migrate historical conversations only so agents can search them later. The bigger value is testing whether the new system can handle real customers.
Export three groups of conversations:
- High-frequency questions: tracking, shipping, sizing, discount codes and return conditions.
- High-risk questions: refunds, compensation, complaints, review threats and platform disputes.
- Multilingual questions: sample beyond English based on target markets, such as Spanish, Portuguese, Arabic or Thai.
Before launch, feed these questions to the AI agent one by one. Check whether it answers from the knowledge base; whether it hands off when it does not know; and whether refund, compensation or price-change requests always go through approval. Do not judge only whether the reply “sounds human.” Look for made-up answers, overreach and missed handoffs.
Reconnect channels with a schedule: avoid customer-facing gaps
For cross-border sellers, support is rarely just one email inbox. Website widgets, custom API, email, WhatsApp, Telegram, Messenger, Instagram, TikTok, LINE, WeChat, VKontakte, Zalo and YouTube can all be customer entry points. The risk is simple: an entry point disconnects before the new one is ready.
Manage channel cutover with a table:
| Channel | Owner | Cutover window | Acceptance check |
|---|---|---|---|
| Website widget | Ops or engineering | Low-traffic hours | Start a test chat and confirm it enters the new workspace |
| IT or support lead | After forwarding or MX changes | Test inbound and outbound mail from an external address | |
| WhatsApp / Messenger | Social lead | Same day as reauthorization | Test DMs, notes and customer-profile merge |
| TikTok / Instagram | Content team | Ad low point | Test whether comments and DMs enter the same queue |
Use a verifiable switch window. After each channel is connected, confirm that messages land in one workspace, identities can merge, and agents can see context. For the broader logic, read omnichannel inbox explained.
Set the AI/human boundary during migration
Teams often ask “can AI answer this?” and forget “what must never be automated?” Set that boundary before launch.
Use three tiers:
| Risk | What AI can do | Where humans must step in |
|---|---|---|
| Low | Answer tracking, sizing, policy and usage questions | When the customer explicitly asks for a person |
| Medium | Answer first and collect information, such as address changes or shipping nudges | Conflicting information, unhappy customer, request outside policy |
| High | De-escalate, summarize and collect order context | Refunds, compensation, price changes, complaint escalation |
The AI agent faces customers and can answer 24/7 from the knowledge base. Yuna is the merchant-facing AI assistant: it helps teams ask business questions, configure settings conversationally and teach experience to the AI agent. It does not talk to customers. The shared workspace lets AI and humans switch in one click, so customers do not have to repeat themselves.
Refunds, compensation and price changes always require human approval and audit. AI should not execute them automatically.
Roll out in stages: observe, confirm, then automate
Do not flip every channel to full automation at once. A steadier path is to roll out by channel, market or question type.
Use three stages:
- Observe only: connect the new system, but do not auto-reply yet. Watch classification, knowledge hits and handoffs.
- Confirm every reply: AI drafts responses, agents approve before sending, and corrections become reviewable learning suggestions.
- Auto-send: allow automation only for low-risk, high-confidence questions. High-risk cases still hand off.
YundaDesk can start conversations at appropriate moments, but the guardrails stay on: cooldowns, frequency caps, quiet hours, no interruption while the customer is already chatting, do-not-disturb lists and human approval for sensitive actions. Observe first, confirm next, automate last.
Review after launch: turn migration into the next upgrade
Review one to two weeks after launch: which knowledge items missed, which channels still feel fragmented, which human answers should become reusable knowledge, and which customer records did not merge.
Review these points:
- Did questions the AI missed become learning suggestions?
- Did owners review and accept useful agent corrections?
- Is every new skill or knowledge item traceable, testable and revertible?
- Do all channel messages enter one workspace and one customer profile?
- Does billing match expectations, and do included AI credits cover current usage?
A good support software migration reduces tool-hopping, gives AI evidence from day one, and turns human experience into controlled, reusable capability. Selection decides which tool you buy. Migration decides whether that tool actually catches customers.
Switching support software does not have to be perfect in one move, but every step should be verifiable. Clean the knowledge base first, reconnect channels carefully, test AI before launch, and keep humans in charge of high-risk actions. That turns migration from a risky cutover into a stronger operating system for support.