On this page
- When is switching worth the work?
- What is a phone-number migration and what is a data migration?
- What should you prepare before any account change?
- What steps should the transition follow?
- How much time and money should you allow?
- What should the acceptance test include?
- Which mistakes are easiest to prevent?
- How can you prepare a move to Wydely?
- Frequently asked questions
When is switching worth the work?
Switch when the new setup solves a documented problem that justifies its cost and transition work. Examples include an unresolved workflow requirement, an integration gap or commercial terms that no longer fit. First ask the current provider whether the issue can be resolved without moving the number.
Write a one-page brief with the problem, its operational effect and the outcome you need. “Improve support” is difficult to test. “Let the evening teammate continue an assigned enquiry with its context” can be demonstrated. Compare the proposed result with the current process before agreeing to a move.
What is a phone-number migration and what is a data migration?
A number connection and the provider’s stored workspace data are separate parts of a transition. Confirm each item explicitly. Do not treat successful number registration as proof that old conversations, consent evidence, reports or automations are available in the new workspace.
Scroll table sideways to see all columns.
| Item | Question to resolve | Evidence to keep |
|---|---|---|
| Phone number | Is this exact number eligible for the proposed connection route? | Written route, prerequisites and responsible contacts. |
| Business ownership and access | Which business account and administrators control the assets? | Account identifiers and agreed administrator access. |
| Message templates | Which templates need resubmission, mapping or approval? | Template names, languages, categories, status and sample values. |
| Customer records | Which fields, tags and consent evidence can be exported and imported? | A field map and a test import result. |
| Conversation history and media | What remains accessible and for how long? | Export format, access terms and retention decision. |
| Automations and campaigns | Which journeys and scheduled sends need rebuilding? | Inventory, pause plan and acceptance test. |
| Integrations | Which events, keys and endpoint settings change? | Connection map and test receipts. |
| Billing | What happens to unused balance and the old subscription? | Cancellation date, refund terms and final invoice expectation. |
What should you prepare before any account change?
Record your business account details, number, administrators, active use cases and provider contacts. Confirm you can complete the supported verification steps. Keep credentials and verification codes out of shared planning documents.
Export the records your business is entitled to retain using the current provider’s supported tools. Check a small sample before depending on the file. Preserve opt-outs and consent context with the contact records. A contact list without its permissions is not a ready campaign audience.
Inventory scheduled campaigns, automations, webhooks, store events and API clients. Name an owner for each. Agree the point at which old scheduled activity is paused and how the receiving workspace will avoid duplicate follow-ups.
What steps should the transition follow?
- Confirm the route. Ask the receiving provider to review the exact account and number. Obtain its current instructions and prerequisites.
- Agree scope and commercial terms. Record included data work, setup fees, subscriptions, balances and responsibilities.
- Prepare the new workflow. Map contacts, templates, team access and required integrations. Complete what can be tested before changing the production connection.
- Schedule the change. Choose a time, a named operator and a support contact at each provider. Record any expected interruption.
- Follow the provider’s current account-specific steps. Avoid copying instructions from a different connection type or another provider’s route.
- Test before expanding. Check inbound messages, permitted replies, templates, handoffs, event callbacks and the usage record.
- Make the go or recover decision. Continue only when the agreed critical tests pass. Use the recorded recovery path if they do not.
- Close the old arrangement. Cancel or change the old subscription only after the required access, records and operational tests are resolved.
How much time and money should you allow?
A credible estimate separates provider connection work from data preparation, workflow rebuilding, testing and team training. Ask for an account-specific schedule. This page does not promise a universal migration duration or an interruption-free move.
Scroll table sideways to see all columns.
| Budget item | How to estimate it |
|---|---|
| Provider setup or migration service | Request a written amount and included scope. |
| Overlapping subscriptions | Allow for the agreed test and records-access period. |
| Data preparation | Count the fields, exports and records that need mapping or cleanup. |
| Automation and integration work | List the journeys and external systems that need rebuilding or reconfiguration. |
| Messaging tests | Use an agreed small audience and the current account rate card. |
| Staff training | Schedule the people who will own enquiries and investigate failures. |
See the WhatsApp total-cost worksheet to compare ongoing costs after setup.
What should the acceptance test include?
Use consented test contacts and fictional or appropriately anonymized examples. Keep a timestamp, expected result and observed result for each test. A dashboard badge alone is insufficient evidence of a working end-to-end journey.
- A new incoming enquiry appears in the correct workspace and reaches the intended teammate.
- A permitted reply is visible to the test customer, with a recorded message outcome.
- The required template is available with the right language, variables, links and buttons.
- An automation handles a valid answer, an unexpected answer and the agreed human handoff.
- The essential integration event arrives once, records the right reference and handles a duplicate safely.
- A failed event has an owner, a visible error and an agreed retry process.
- The usage or billing record can be reconciled with the test messages.
Which mistakes are easiest to prevent?
Do not assume every migration route transfers the same assets. For example, WATI migration documentation describes template handling for its own incoming route. That is evidence about that route, not a promise about another provider’s behavior.
Do not remove the old access before required records are secured. Do not continue scheduled sends in two workspaces without a coordinated plan. Do not replace proof with a reassurance that the number “will work.” Write the test, its owner and the recovery decision before the change.
How can you prepare a move to Wydely?
Start with the Wydely account preparation guide. Share your current connection type, intended number, team workflow and required integrations during a walkthrough. Ask the team to confirm the supported migration scope and anything that must be rebuilt.
Frequently asked questions
Can I switch provider without changing my number?
A supported route may be available, but the receiving provider must confirm the eligibility and prerequisites for your exact number and connection type.
Should I delete my existing WhatsApp setup first?
Follow the agreed account-specific instructions. Do not remove a working setup as a generic first step.
Will my templates transfer?
Confirm template treatment in writing for the exact route. Record which templates must be recreated, mapped or approved before the workflow can run.
Will all my chat history move?
Do not assume that. Ask what can be exported, imported or retained for reference, including media and record-retention conditions.
What happens to unused message balance?
The current provider’s terms determine its treatment. Ask about refundability, expiry, minimum balance and the final invoice before cancelling.
How long does migration take?
The connection step is only part of the work. Request an estimate for preparation, approvals, integrations, testing and training on your account.
Can migration be guaranteed to have no downtime?
This guide gives no downtime guarantee. Record expected interruption, support availability, acceptance tests and a recovery decision with both providers.
Do I need to rebuild integrations?
Review every connected system. Keys, event settings, field mappings or workflow logic may need changes. Test required events and failures.
Can I send a campaign immediately after connecting?
First confirm the account, recipient permission, template availability, current limits and message balance. Complete a small agreed end-to-end test.
When should I cancel the old provider?
After required records, access, critical workflows and commercial obligations are resolved according to the transition plan.
Sources and review
Original public-source review: 26 October 2026. Migration documentation and messaging policy reviewed again 27 October 2026. Prepared by Wydely; this guide does not claim an independent performance test.