💼 Cost & business

Avoiding vendor lock-in with chatbot platforms: what to check before you commit

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

In short

Vendor lock-in with a chatbot platform comes from three things: not owning your WhatsApp Business Account and API keys, not being able to export your flows and contacts, and being on a closed platform where your provider keys belong to the vendor. Check ownership and export ability before committing, not after you want to leave.

Key takeaways

Confirm who legally owns your WhatsApp Business Account (WABA) and phone number — it should be you, not the vendor.
Ask whether flows export as portable JSON, or only exist inside that vendor's proprietary format.
Check that contacts, tags and custom fields export as a plain CSV, not a locked report.
On a BYOK platform your AI and telephony keys are your own from day one — that alone removes a major lock-in risk.
Test the export function during your free trial, not after you have decided to leave.

What lock-in actually looks like

Vendor lock-in rarely announces itself upfront. It shows up later, when a business wants to switch platforms and discovers that its WhatsApp number is tied to the vendor's Meta Business Manager, its flows only exist as a proprietary configuration nobody else can read, or its years of contact history has no clean export. By then, switching costs real time and sometimes real data loss. The fix is checking these things before signing up, using a checklist rather than trusting a sales conversation.

The good news is that every one of these risks is checkable in a few minutes, before you commit. You just have to know what to ask and actually test the answer rather than accept a verbal assurance.

Ownership check 1: your WhatsApp Business Account

WhatsApp Business API access runs through a WhatsApp Business Account (WABA) connected to a Meta Business Manager. Some platforms set this up under their own Meta Business Manager on your behalf, which can make it harder to move your number cleanly if you switch later. Ask directly: 'Is the WABA created under my own Meta Business Manager, or yours?' A platform using Meta's embedded signup flow typically sets this up under your own Business Manager from the start, so the number and its message history stay tied to your business identity, not the vendor's.

Ownership check 2: your API keys

If a platform uses its own shared AI provider account behind the scenes, you never had your own OpenAI, Claude or Gemini key to begin with. There is nothing to take with you, and you are dependent on that vendor's account staying active and affordable. A BYOK (Bring Your Own Keys) platform is structurally different: you create and hold your own provider accounts, and the platform only ever uses the key you gave it. See BYOK explained for the full model. The same logic applies to your telephony account for voice calling. A platform that requires you to route calls through its own telephony contract, rather than your own Exotel, Plivo, Twilio or SIP account, creates the same dependency.

Ask who owns the WABA and Meta Business Manager the number will sit under.
Ask whether AI provider keys are yours or the vendor's shared account.
Ask whether your telephony account (for voice) is yours or routed through the vendor's own contract.
During the trial, build a small flow and try exporting it: check the format, not just whether an export button exists.
During the trial, add a test contact with a custom field and export contacts, then confirm the field survives the export.
Ask if there is a published REST API, and whether it is available on your intended plan.
Ask what happens to your approved WhatsApp templates if you leave, since they should stay usable because they belong to your WABA.
Ask directly what a full data export looks like if you decided to leave tomorrow.

Export check: flows, contacts and templates

What to check	What good looks like
Flow logic	Exports as structured JSON you (or a developer) can read and rebuild elsewhere
Contacts and custom fields	Exports as a plain CSV with all tags and fields intact
Approved WhatsApp templates	Templates belong to your WABA, not the vendor, so they should remain usable regardless of platform
Conversation history / CRM leads	Exportable in a standard format (CSV or via API) rather than locked to an in-app report

Test this during your free trial: build a small flow, add a test contact, then try the export function immediately. If it is missing, hard to find, or support is vague about it, treat that as a real answer.

A published REST API adds a further layer of confidence: it lets you programmatically pull your own data, including contacts, conversation logs and CRM records, even outside the platform's built-in export tools. Its presence, or absence, is itself a signal. A platform confident enough to expose your data via API is architecturally different from one that keeps everything behind a closed UI.

A lock-in risk decision table

Risk factor	What to check
WABA under vendor's Business Manager	Ask for it to move under your own Business Manager, or treat this as a hard blocker.
No BYOK for AI or telephony	Confirm you can bring your own provider account before committing long-term.
Flows do not export	Budget real rebuild time if you ever switch: this is the costliest lock-in to discover late.
No REST API on any plan	Your only path to bulk data is whatever export tools exist in the UI, so test them thoroughly.
Vague answers to direct ownership questions	Treat evasiveness itself as the answer, and get everything in writing before signing.

How Convo360 addresses this

Convo360 is BYOK by design. Your WhatsApp number connects via Meta's embedded signup under your own Business Manager, your AI provider keys are your own, and your telephony account is your own. Flows can be exported and a migrate-from-uChat import tool shows the platform's own approach to portability in both directions. Contacts export as CSV, and the REST API (Business plan) exposes your data programmatically. None of this guarantees you will never want to switch. It guarantees that if you do, the switch is a data-export exercise, not a rebuild-from-scratch exercise.

Step by step

Ask the ownership questions firstBefore signing up, confirm who owns the WABA, AI keys and telephony account in writing.
Test flow export during the trialBuild a small flow and export it to check the format is genuinely reusable, not a locked report.
Test contact export with a custom fieldAdd a test contact with a tag and custom field, then confirm both survive a CSV export.
Confirm REST API availabilityCheck whether the REST API is available on the plan you actually intend to buy, not just a higher tier.
Get answers in writingFollow up any verbal reassurance with a written confirmation you can refer back to later.

Example conversation

We're evaluating a chatbot platform and the sales rep said 'don't worry about that' when we asked about exporting our data. Should that concern us?

Yes — ask again in writing, or better, test it yourself during the trial. A platform confident about portability will show you the export function directly rather than reassure you verbally.

Try Convo360 with your own keys

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

What is the biggest sign of chatbot vendor lock-in?

Not owning your own WhatsApp Business Account or AI provider keys is the biggest structural risk — it means the vendor, not you, controls the assets your customer relationships run through.

Does BYOK fully prevent lock-in?

It removes a major source of lock-in (provider keys and accounts), but you should still confirm flows and contacts export in a portable format, since flow logic can still be platform-specific.

Can I move my WhatsApp number to a different platform later?

If your WABA sits under your own Meta Business Manager, yes — this is a standard part of how WhatsApp Business API access works, independent of which platform you use.

Should I test data export before committing to a platform?

Yes — test it during the free trial with a sample flow and contact, rather than assuming it works. This is one of the easiest lock-in risks to catch early.

Does Convo360 lock in customer conversation history?

No — conversation and CRM data can be accessed via the REST API on the Business plan, and contacts export as CSV, so history is not trapped behind the UI alone.