Switching to a WhatsApp Workspace: Migration Guide

Most teams don't decide to switch tools. They hit a wall. A lead messaged someone who's now on leave and nobody can find the thread. A broker group has three deals buried in the scroll and no one owns any of them. Or the API tool you bought last year keeps charging per message, won't touch your groups, and just flagged another template for "approval." The channel is fine — WhatsApp is where your customers are. The setup around it is the problem.

This guide is for teams making the move to a proper WhatsApp workspace: a shared inbox, a real CRM, and a support desk built on the number you already use. Whether you're coming off personal phones or off an API tool like WATI, AiSensy or Interakt, the goal is the same — switch without losing a single chat, contact, or open deal. We'll cover what to migrate, what not to migrate, the order to do it in, and how to keep your number safe through the change.

TL;DR: what switching actually involves

• You keep your number. A workspace links your existing WhatsApp number by QR scan — no new SIM, no porting, no migration window where customers can't reach you.
• Two starting points, two paths. Coming off personal phones is mostly about consolidating scattered chats. Coming off an API tool is about exporting contacts and escaping per-message billing.
• History is the hard part — plan it first. Decide what "zero lost history" means for you before you flip the switch.
• Run both in parallel for a few days. Don't hard-cut. Connect, test, train, then route everything over.
• Protect the number through the move. A migration is exactly when blast-happy habits get a number flagged. Pace the change.

Why teams switch in the first place

Before the how, be honest about the why — it decides what "good" looks like after you switch. Most migrations we see start from one of three pains.

You've outgrown personal phones (or the free Business app)

The free WhatsApp Business app is built for one person, one phone. The moment a second teammate needs to see the same chats, it cracks:

• Leads live in a phone, not the business. If a customer messaged Priya, only Priya knows. Priya leaves, the relationship leaves.
• No one owns anything. Two people reply to the same chat, or nobody does, because there's no assignment.
• No CRM, no pipeline. "Where's that enquiry from Tuesday?" lives in memory, not a stage.
• Groups are chaos. Deal-flow and questions scroll past with no way to tag, assign or follow up as a team.

If that's you, our guide on whether the WhatsApp Business app is enough for teams goes deeper — but the short answer is usually no, past two or three people.

You're trapped in an API tool

The other common starting point is buyer's remorse on the WhatsApp Business API. Tools built on it (WATI, AiSensy, Interakt, DoubleTick) solve broadcasting, but introduce their own walls:

• Per-message and per-conversation fees that scale with your success, not a flat price.
• Template approvals — every proactive message routed through Meta's review, killing spontaneity.
• No group access at all. The official API structurally cannot read or send to WhatsApp groups. If your business runs on groups, the API is the wrong tool by design — more on that in can the WhatsApp Business API access groups.
• A "CRM" that's really a contact list with tags, not a pipeline you can drag a deal across.

If you're specifically leaving WATI, we have a step-by-step migrate from WATI to Tenashi walkthrough. The principles below apply to any API tool.

You want one place, not a stack

The third reason is quieter but real: teams are tired of stitching a shared inbox to a separate CRM to a separate broadcast tool. A workspace folds the inbox, CRM/pipeline, support tickets, automations and broadcasts into one product on one number — so a chat, a contact, a deal and a ticket are the same record, not four exports.

Personal phones vs API tool: two different migrations

"Switch to a WhatsApp workspace" means two genuinely different projects depending on where you're starting. Get this distinction right and the rest is straightforward.

The personal-phones path is mostly change management — the tech is a five-minute QR scan; the work is getting the team to stop replying from their own phones. The API path is mostly data and number logistics — making sure your contacts come with you and your number is yours to move.

We'll handle the shared steps first, then the parts unique to each.

Step 1: Audit what you actually have

Don't migrate blind. Spend an hour listing the assets that have to survive the switch. Most teams under-count this and lose something they cared about.

Make a simple inventory:

1. Numbers. Which WhatsApp number(s) run the business? Who controls the SIM/login for each? Are any on a Business Solution Provider (BSP) from an API tool?
2. Conversations that matter. Open deals, active support threads, VIP customers. You rarely need every chat from 2023 — you need the live ones.
3. Contacts and fields. Names, numbers, and any structured data you track (budget, source, plan, last order). If it's in an API tool, find the export button now.
4. Groups. Broker groups, customer cohorts, internal coordination groups — list them and who admins each.
5. Automations and saved replies. Away messages, greetings, canned answers, keyword flows you'll want to recreate.
6. People. Who needs access, and at what level — full admin, agent, view-only.

Write it down. This list becomes your migration checklist and your "did we lose anything?" audit at the end.

Step 2: Get clear on "zero lost history"

This is the step everyone skips and later regrets. "Don't lose history" sounds obvious, but it means different things, and the realistic answer depends on where you're starting.

The honest truth about WhatsApp chat history: WhatsApp chats are tied to the number and device. When you link your existing number to a workspace by QR scan, you keep ownership of the number and the conversation continues seamlessly going forward — the customer keeps messaging the same number, and from connection onward every message lands in your shared inbox with full history captured there. What a workspace does not do is retroactively suck years of old messages off three different agents' personal phones into a database. That's a WhatsApp platform limit, not a tool limit, and any vendor promising otherwise is overselling.

So define your target realistically:

• "Going forward, nothing is lost" — achievable and the right bar for most teams. From the moment you connect, every chat, group, note and deal lives in the workspace permanently.
• "My contacts and structured data come with me" — fully achievable via CSV import (and exports from your old API tool). This is where the real value sits.
• "Every historical message from every phone is in the new tool" — not realistic for old chats stranded on personal devices. Capture what matters (open threads) manually during the parallel-run, and let the rest live where it always has.

Setting this expectation up front is the difference between a smooth switch and a disappointed team. For the mechanics of linking, see connect your existing WhatsApp number in minutes.

Step 3: Connect your existing number (the actual switch)

Here's the part people brace for and then find anticlimactic. Linking your number to a workspace is a QR scan, the same gesture you use for WhatsApp Web:

1. Open the workspace and start the connect flow.
2. On the phone that holds your WhatsApp number, open Linked Devices.
3. Scan the QR code shown by the workspace.
4. Your number is now linked. Chats and groups begin syncing into the shared inbox.

That's it — no new SIM, no porting, no number change, and no downtime for your customers. They keep messaging the exact number they always have. Because it's your number rather than a fresh API number, you also keep full access to your groups, which the API can never offer.

The API-tool caveat: reclaiming your number

If you're switching off an API tool, there's one extra wrinkle worth handling early. Your number may currently be registered to that tool's BSP on the official API. To link it to a workspace as a normal WhatsApp number, you may need to deregister it from the API first so it can run as standard WhatsApp again. Check your current vendor's offboarding process before you cancel anything, so there's no gap where the number is in limbo. Plan this for a quiet window, not your busiest sales hour.

Step 4: Bring your contacts and data across

Conversations continue automatically once you connect — but your structured data is the asset you actively migrate, and it's where a workspace earns its keep over personal phones.

• From an API tool: export your contacts (most tools offer a CSV export of contacts, tags and custom fields). Map their fields to your workspace's contact fields and custom fields, then import. Tags usually become custom fields or pipeline stages — decide the mapping deliberately rather than dumping everything into notes.
• From personal phones: there's rarely a clean export, so build the contact list from your real pipeline. Import a CSV of known customers if you keep one in a spreadsheet, and let new inbound chats create contacts automatically from connection day onward.

Once contacts are in, set up the layer the old setup never had: custom fields for the data you track, and a drag-drop pipeline for your deals. This is the moment a pile of chats becomes a CRM. Our guides on custom fields and contact profiles and building a sales pipeline on WhatsApp cover how to structure both so they fit your sales motion instead of a generic template.

Step 5: Rebuild your automations and team setup

With the number connected and data in, recreate the small things that make the day flow — and add the team structure personal phones could never give you.

Recreate from your audit list:

• Greetings and away messages for after-hours and first contact — see greeting and away message examples.
• Canned replies for the questions you answer fifty times a day, so agents aren't retyping. Set these up using canned replies for WhatsApp.
• Auto-assignment rules so inbound chats land on the right agent instead of waiting for someone to claim them.

Set up the team layer:

• Invite your people and set roles — admin, agent, view-only — so access matches responsibility. See roles and permissions for a WhatsApp inbox.
• Decide assignment ownership — round-robin, by region, by product — so every chat has one accountable owner.
• Turn on internal notes and @mentions so the team coordinates inside a chat without the customer seeing. More in internal notes and @mentions on WhatsApp.

If support is part of your job, this is also where you wire up tickets and SLAs so questions get tracked and answered on time rather than scrolling away — our WhatsApp customer support guide walks through that.

Step 6: Run both in parallel, then cut over

Resist the urge to hard-cut on day one. A short parallel run catches the gaps before they cost you a customer.

1. Connect and test quietly. Link the number, send test messages, confirm chats and groups sync, check assignment and notes work.
2. Onboard the team for a day or two. Have agents reply from the workspace while the old setup is still live as a safety net. Muscle memory is the real migration cost off personal phones.
3. Move the open threads. For active deals and live support tickets, make sure each has a contact, a deal/ticket and an owner in the workspace. This is your manual "capture the history that matters" step.
4. Cut over fully. Once the team is comfortable, route everything through the workspace and retire the old habit — agents stop replying from personal phones, or you finish offboarding the API tool.
5. Audit against your Step 1 list. Tick off every number, group, contact set and automation. Anything missing gets fixed now, while you still remember it existed.

Most teams we talk to are comfortable within a few days, not weeks — the channel is unchanged, so there's no new app for customers and only a modest new habit for the team.

Don't get your number flagged during the switch

A migration is, ironically, one of the riskier moments for your WhatsApp number. The temptation is to celebrate the new tool by firing a big "we've upgraded!" broadcast to your whole list on day one. That sudden spike in outbound volume from a number that normally chats one-to-one is exactly the pattern WhatsApp's spam systems watch for.

Two rules keep the switch safe:

• Don't blast on day one. Warm into broadcasting gradually. If you must announce, segment and pace it over days, not minutes. Our WhatsApp broadcasts guide covers doing this safely.
• Use a tool that paces sends for you. Human-like timing, jitter and burst guards matter most right after a switch, when habits are forming.

This is risk reduction, not a guarantee — WhatsApp's policies are theirs to change — but pacing the migration meaningfully lowers the odds of a flag. For the full picture, see how to avoid getting your WhatsApp banned.

Where Tenashi fits

Tenashi is the WhatsApp workspace for teams, and it's built for exactly this switch. You link your existing WhatsApp number with a QR scan — no new SIM, no porting, no downtime — and within minutes your whole team works one shared inbox covering DMs and groups, with a real CRM and pipeline under every chat and a support desk (tickets, SLAs) on top.

For teams leaving personal phones, that means leads stop living on individual devices: every chat, contact and deal sits in the business, owned and trackable, and stays put when someone leaves. For teams leaving an API tool, it means importing your contacts by CSV, regaining group access the API can't offer, dropping template approvals and per-message fees, and paying a flat price instead. Pricing is simple and predictable: Starter $18/mo, Growth $27/mo, Scale $56/mo, with a 3-day Growth trial that needs no card.

Through the switch and after it, sends are ban-protected — human-paced, with jitter, warm-up, typing presence and duplicate/burst guards plus a safety log — so the number that runs your business stays safer during the risky first days (risk reduction, not a guarantee). And on Growth & Scale, AI can draft suggested replies, summarize a noisy group thread into action items, run OCR on images and translate messages inline — handy when you're getting a team up to speed on a new inbox.

Start your free trial → · See every feature

Related guides

Planning your move? These go deeper on each piece:

• Migration & setup (this cluster): migrate from WATI to Tenashi, WhatsApp CRM cost: what you'll actually pay, and connect your existing number in minutes.
• Shared inbox: the WhatsApp shared inbox for teams guide and how to share one number with a team.
• Running sales: WhatsApp CRM and WhatsApp lead management.
• Choosing a tool: best WhatsApp CRM software in 2026 and the complete guide to WhatsApp for Business.

FAQ

How do I switch to a WhatsApp workspace without losing my number?

You don't change numbers at all. A workspace links your existing WhatsApp number by QR scan — the same way WhatsApp Web works — so there's no new SIM, no porting and no downtime. Your customers keep messaging the exact number they always have, and from connection onward every chat lands in your shared team inbox.

Will I lose my chat history when I migrate?

Going forward, no — from the moment you connect, every chat, group, note and deal is captured permanently in the workspace. What no tool can do is retroactively pull years of old messages off individual agents' personal phones, since WhatsApp ties chats to the device. Capture your open threads manually during a short parallel run.

How do I move off WATI or another API tool?

Export your contacts and custom fields from the API tool as a CSV, deregister your number from the tool's API so it can run as standard WhatsApp, then link it to the workspace by QR scan and import your contacts. You regain group access the API can't offer and drop per-message fees and template approvals. See our migrate-from-WATI guide for the step-by-step.

Do I need a new phone number to use a WhatsApp workspace?

No. The whole point of a workspace is that it runs on your existing number via a QR scan — no new SIM, no porting, no migration window. This is the key difference from the WhatsApp Business API, which typically registers a separate number through a provider and can never access your groups.

How long does switching take?

The technical part is minutes — connecting your number is a single QR scan. The real timeline is team onboarding: most teams we talk to are comfortable within a few days, running the old setup in parallel as a safety net before cutting over fully. There's no new app for your customers, so adoption friction is low.

Is it risky to switch — could my number get banned?

The switch itself is safe, but the day-one temptation to blast a big "we've upgraded" broadcast is risky, because a sudden volume spike is what spam systems watch for. Warm into broadcasting gradually and use a tool that paces sends with human-like timing and burst guards. That reduces the risk, though no tool can guarantee against WhatsApp's policies.

---

Switching to a WhatsApp workspace isn't a rebuild — it's a QR scan, a contact import, and a few days of getting your team off their phones. Start your free trial and move every chat, group and deal into one place, on the number you already use.