🛠️ How-to tutorials

Migrating from uChat or any chatbot builder without losing data

Updated 2026-09-19 · 4 min read · By the Convo360 team

In short

Convo360's in-app 'Import from uChat' connects by API key to preview and bring in contacts, custom fields and tags — tags map to Convo360 groups. Flow logic isn't imported since it isn't exposed by most builders' APIs, so flows need rebuilding in the flow builder (a close Template Store match speeds this up), and provider keys and WhatsApp templates need re-entering and re-submitting for the parts that actually changed.

Key takeaways

Contacts, custom fields and tags migrate through the in-app import tool; flow logic does not and needs rebuilding.
Tags on your old platform become groups in Convo360 after import.
Provider keys (AI, voice, telephony, payment) never carry over — re-enter them under Integrations for security.
Templates already approved for your WhatsApp Business Account generally stay approved; only new or edited ones need fresh submission.
Run both platforms in parallel briefly, then fully disconnect the old one before pointing WhatsApp's webhook at Convo360.

What migrates, and what doesn't

Contacts, custom fields and tags migrate through Convo360's in-app import tool. Flow logic does not. Most chatbot builders, including uChat, don't expose their flow graphs through an API, so there's nothing for an import tool to read even if one existed. Provider keys never carry over, by design: AI, voice, telephony and payment keys are sensitive, so you re-enter them fresh under Integrations → Provider keys rather than have them silently copied between platforms.

It is worth treating this as a feature rather than a limitation, a fresh key entry is also a natural checkpoint to confirm every provider account is still active and correctly scoped, rather than inheriting an old, possibly stale configuration unchecked.

The exact click path (Convo360 side)

Open the Import from uChat tool in your Convo360 account.
Connect your uChat account with its API key.
Preview what will be imported: contacts, custom fields and tags.
Confirm the import; tags become Convo360 groups automatically.

Rebuilding your flows

Since flow graphs don't transfer, rebuild each important flow directly in the flow builder. This is less work than it sounds: start from the closest match in the Template Store and edit the wording, buttons and logic to match what you had, rather than building from a blank canvas. Prioritise your highest-traffic flows first (the main greeting, order status, FAQ) and leave rarely-used ones for later.

Keep the old platform's flow screenshots or exported text handy while rebuilding, comparing side by side is far faster than trying to recall from memory exactly how a five-step flow branched.

While you're rebuilding, it's worth improving each flow rather than reproducing it exactly: add a Condition branch you'd been meaning to add, tidy a confusing menu, or move a rarely-used option behind a 'talk to us' fallback. A migration is one of the few natural moments to clean up years of small accumulated flow debt without disrupting live customers.

Re-entering secrets and re-approving templates

Reconnect your WhatsApp number to Convo360's Cloud API, and re-add your AI, voice, telephony and payment provider keys under Integrations. Your previously approved WhatsApp templates generally stay approved, since templates belong to your WhatsApp Business Account in Meta, not to whichever platform is connected to it. You'll only need fresh Meta approval for templates you create new or meaningfully edit.

Telephony and payment provider accounts work the same way, if you are keeping the same Exotel or Razorpay account and simply switching which platform holds its keys, nothing about your provider-side setup changes, only where the key is stored.

The cutover plan

Set up and test flows, agents and integrations fully in Convo360 before touching your live number.
Run a short parallel period if possible: test conversations on Convo360 while the old platform still handles live traffic.
Fully disconnect the WhatsApp webhook from the old platform before pointing it at Convo360, to avoid both systems trying to answer at once.
Monitor the first day of live traffic closely and keep the old platform's export handy in case you need to double-check a contact detail.

The single biggest source of friction in any migration is not the technical steps, it is a teammate opening the new system and not finding a flow, a saved reply, or a report they relied on daily. Walk the team through what moved automatically (contacts, tags, groups) and what needs rebuilding (flows, templates) before the cutover happens, not after someone notices something missing.

Troubleshooting

Symptom	Likely fix
Contacts imported without their groups	Tag-to-group mapping was skipped in the preview step. Re-check the import settings before confirming.
Duplicate contacts after import	Contacts are matched by phone number. Check your source export didn't have inconsistent number formatting.
Flows appear missing after import	Expected. Flow logic isn't imported and needs to be rebuilt manually in the flow builder.
Number stuck receiving on the old platform	The old platform's webhook wasn't fully disconnected. Remove that integration before reconnecting in Convo360.
Provider keys appear missing after migration	Expected and by design. Re-enter your AI, voice, telephony and payment keys under Integrations.

What to test before going live, and cost

Confirm imported contacts show the right groups and custom fields.
Test every rebuilt flow end to end before the cutover, not just the happy path.
Send a real WhatsApp test message once the number is reconnected, before announcing the switch.
Keep the old platform accessible (read-only) for a short window in case you need to check historical data.

Your Convo360 plan fee applies as usual (Starter ₹999/month and up, excluding GST); your existing AI, voice and telephony accounts carry over as-is since Convo360 is BYOK, so there's no new provider cost from switching platforms.

The real cost of a migration is time, not money. A careful one-week overlap period is usually enough for a small business, longer for one with dozens of flows and integrations. Rushing the switch to save a few days rarely pays off if it means live customer conversations get missed during the changeover, so it is worth planning an extra day or two of slack into the schedule from the start.

Step by step

Connect uChat via API keyOpen the Import from uChat tool and authenticate with your uChat API key.
Preview and confirm the importReview what will migrate, then confirm to bring in contacts, custom fields and tags.
Rebuild your flowsRecreate key flows in the flow builder, starting from a close Template Store match where possible.
Re-enter provider keysAdd your AI, voice, telephony and payment keys fresh under Integrations.
Reconnect WhatsApp and cut overFully disconnect the old platform's webhook before pointing your number at Convo360.
Test and monitorRun test conversations through every flow, then watch the first day of live traffic closely.

Example conversation

We're switching platforms — will our customers notice or lose their conversation history?

Customers won't notice anything if the cutover is timed well — the number stays the same. Past conversation history depends on what your previous platform allows you to export, so keep read-only access there for a while as a backup.

Start your migration

Start free in minutes — no code, no credit card. Bring your own AI keys and pay no per-message markup.

Start 14-day free trial →See pricing

Frequently asked questions

Does my flow logic transfer automatically from uChat?

No. Most chatbot builders, including uChat, don't expose their flow graphs through an API, so there's nothing for an import tool to read even if one existed. Rebuild each flow manually in the Convo360 flow builder, starting from a close Template Store match to save time.

What happens to my uChat tags after import?

They map to Convo360 contact groups automatically during the import, so any segmentation you built around tags on uChat carries straight over. You can keep using those groups for broadcasts, drip sequences and flow triggers exactly as you would with any group created inside Convo360.

Do I need to re-enter my AI and payment keys?

Yes. Provider keys for AI, voice, telephony and payments never transfer between platforms, by design, since they are sensitive credentials. Add them fresh under Integrations → Provider keys, which also doubles as a useful checkpoint to confirm each account is still active and correctly scoped.

Will my approved WhatsApp templates need re-approval?

Generally no. Templates belong to your WhatsApp Business Account in Meta, not the connected platform, so approved ones carry over. Only new or edited templates need fresh approval.

How do I avoid downtime during the switch?

Test everything fully in Convo360 first, then fully disconnect the old platform's webhook before reconnecting your number, so only one system is ever answering live messages.