Switching WhatsApp Platforms in the UK: How to Migrate Without Losing Your Number or Contact History

What actually transfers when you switch WhatsApp platforms

Understanding what carries over — and what doesn't — is the first step in planning a clean migration.

What transfers:
- Your phone number. The WhatsApp Business phone number you've built your customer relationships around is tied to Meta, not to your BSP. You can migrate it to a new platform via Meta's embedded signup or by requesting a transfer through your new provider. The number and its established quality rating follow it.
- Your Meta Business Manager account. Your WhatsApp Business Account (WABA) lives in Meta Business Manager, not in your BSP. When you move to a new BSP, you're granting that BSP access to your existing WABA — the account itself stays yours.
- Your display name and profile. Business name, profile picture, description, and website URL are stored at the Meta level. They persist through a platform switch.

What does not transfer:
- Conversation history. Message logs, customer conversation threads, and any notes made inside the old platform are not exportable to a new BSP in a format that another platform will import. Download what you need as PDF or CSV before you close your old account.
- Automation flows. The chatbot flows, keyword triggers, and automation sequences you built in your old platform must be rebuilt in the new one. There is no universal WhatsApp automation export format.
- Approved message templates. Templates approved under your old BSP are technically attached to your WABA, not the BSP — but the re-approval process at your new BSP takes a few hours for standard templates. Expect a 4–12 hour gap.
- Contact tags and labels. If your old platform had customer segments, tags, or pipeline stages, these must be re-created manually or imported from a CSV export.

The number migration process: step by step

Meta's number migration process involves three parties: you (the business), your old BSP, and your new BSP.

Step 1 — Prepare your new BSP account. Sign up with your new provider and complete their onboarding before touching your old account. Do not cancel your old account first — you need it active to receive the OTP during migration.

Step 2 — Initiate the number transfer. Your new BSP will prompt you to connect your WhatsApp number via Meta's embedded signup flow. This shows Meta that you want to associate your existing number with the new BSP. In some BSP setups, you request the transfer through your new BSP's support team who manage it on your behalf.

Step 3 — Verify ownership. Meta sends a one-time password (OTP) to the phone number being migrated — either via SMS or voice call. You must be able to receive this OTP. If the number is a VoIP number or a number that can't receive SMS, arrange in advance how you'll receive the OTP.

Step 4 — Old BSP disconnects. Once Meta processes the transfer, your old BSP loses access to the number. This typically takes 15–30 minutes. During this window, inbound WhatsApp messages will queue but not be processed by either platform.

Step 5 — New BSP gains access. Your number is now active on the new platform. Any new inbound messages will route there. Check that your WhatsApp Business profile (name, picture, description) is correct — occasionally these need re-entering.

Timing: the entire process takes 30 minutes to 4 hours. Schedule it for a Sunday morning or another low-traffic period. For UK service businesses, Tuesday–Thursday 11pm–7am has the lowest WhatsApp inbound volume.

Rebuilding templates and automations on the new platform

Template and automation rebuilding is the most time-consuming part of a platform switch. Do this work before initiating the number migration — you want your new platform ready to send the moment the number arrives.

Template audit first. List every active template from your old platform: appointment reminders, status updates, promotional messages, follow-up sequences. Most BSPs let you export a template list as CSV. You'll resubmit each one to Meta for approval through your new BSP.

Template re-approval timing. Standard utility templates (appointment reminders, order updates) typically approve within 2–4 hours on weekdays. Marketing templates take 4–12 hours for standard content. Complex templates or anything with variables that Meta flags for review can take 24–48 hours. Submit templates as soon as your new BSP account is created — days before the number migration.

Automation flows — plan before rebuilding. Use the switch as an opportunity to audit your automations. The flows you had on the old platform are documented somewhere (in your team's notes, or in screenshots). Rebuild only what's actively used — migration is an opportunity to remove abandoned sequences.

Contact list migration. Export your contact list from your old BSP (most export to CSV with name, phone number, tags/labels). Import into your new platform. Check that phone number formatting is consistent — UK numbers should be in E.164 format (+447XXXXXXXXX). Misformatted numbers will fail to send.

Test before going live. Before the number migration, test your new platform with a secondary number or a sandbox account. Verify that templates render correctly, automation triggers fire as expected, and team inbox assignment works.

GDPR and data handling during a platform switch

Switching WhatsApp platforms is a data processing change that has GDPR implications for UK businesses.

Data processor change notification. Under UK GDPR, your BSP is a data processor — they process WhatsApp message data on your behalf. When you switch BSPs, you're changing data processors. Review your customer consent notices: if they reference your specific BSP by name, update them. If they reference 'third-party messaging platforms' generically, no update is needed.

DPA with new BSP. Before onboarding with a new BSP, ensure they provide a UK GDPR-compliant Data Processing Agreement (DPA). EU BSPs that reference GDPR should also reference the UK GDPR post-Brexit divergence, or provide a separate UK addendum. Ask your new BSP's sales team for their DPA before signing up.

Data export and deletion from old BSP. When you leave a BSP, request deletion of your data from their servers per your contract terms and UK GDPR Article 28. Most reputable BSPs have an account deletion process that includes data purge. Get written confirmation if the data set contains sensitive categories.

Conversation data retention. If your old BSP conversation records contain personal data (customer names, contact details, service history), and you've downloaded them for archive purposes, store them per your data retention policy — typically 6–12 months for service businesses, 6 years for accounting or professional services engagements.

UK vs EU BSP choice. Post-Brexit, UK businesses are not required to use EU-based BSPs. Most major BSPs (WATI, Respond.io, BotSpace) operate under EU GDPR with data stored in EU data centres and UK GDPR compatibility covered under adequacy or standard contractual clauses. The EU-US Data Privacy Framework (2023) covers US-domiciled BSPs' Meta data transfers.