The company decides to change providers. Someone hits the migration button on a Tuesday at 10h, the number goes offline, templates disappear, the history remains in the old system, and no one can respond to the 140 customers who messaged that morning. The migration itself takes minutes — the damage comes from everything that wasn’t prepared beforehand.
In this article
- When the switch is justified
- What moves with you and what stays behind
- What to prepare before pressing any button
- The migration sequence
- The real cost of a poorly planned window
- What happens with quality and tier
- How to evaluate the new provider before deciding
- The first thirty days with the new provider
- When not to migrate
- Mistakes that turn migration into a crisis
- Frequently Asked Questions
When the switch is justified
Migration takes effort and only makes sense for concrete reasons. The four that truly justify it:
- Cost per conversation above market or opaque margin charges over Meta’s price.
- Lack of essential features — multiple agents, funnel, automation, per-agent reporting.
- Support that doesn’t respond when the number goes down or a template is rejected.
- Recurring instability, with messages delayed or disappearing.
What doesn’t justify it: a monthly fee promotion. Saving a few reais per month rarely covers the cost of a poorly executed migration, and even less so discovering afterward that the new provider has the same limitations as the previous one.
What moves with you and what stays behind
This is the part that surprises most people. In practice:
- Moves with you: the number itself, the commercial account on Meta, the accumulated quality and tier of the number, and business verification.
- Needs to be recreated or reapproved: the templates, which usually require new registration and approval at the destination.
- Usually stays behind: the conversation history stored in the old system, tags, funnel, automations, and reports.
The third item is the most painful and most overlooked at decision time. The history belongs to the platform that stored it, and export is almost always limited — which is why it’s worth treating backup and retention as a selection criterion before contracting any provider, not after.
Continue reading for free
Fill out once and unlock this and all other blog articles. We don’t charge anything — we just want to know who we’re writing for.
Takes 20 seconds. Prefer to talk directly on WhatsApp?
What to prepare before pressing any button
- Export everything possible from the current system: conversations, contacts with tags, reports from the last 12 months. Do this while the contract is still active — after cancellation, access usually ends quickly.
- Document existing templates with name, category, language, and exact text, including variables. You will recreate them at the destination.
- Note active integrations: website, CRM, ERP, automations, ad links. Each will need to point to the new endpoint.
- Confirm access on Meta. The company must own the business portfolio and WhatsApp account. If the current provider owns it, migration stalls — and this is the most common blocker of all.
- Ask the new provider for a written step-by-step, with estimated downtime.
The fourth item deserves extra attention. Check today, even if you don’t intend to migrate, whether your company owns the Meta account. When the number is under a third party’s portfolio, the company does not control its own channel — and finds out at the worst possible moment.
The lowest impact window: perform migration during the lowest volume hours, usually late at night or Sunday morning, and never on the eve of a campaign or holiday. Publish an absence notice beforehand and assign someone to monitor the first two hours after the switch.
The migration sequence
- Hire and configure the destination first, with users created, permissions defined, and integrations ready to be connected.
- Register templates at the destination and wait for approval before migrating. Having templates approved in advance eliminates the worst-case scenario of being unable to start conversations.
- Notify the team with the exact time and instructions during the window.
- Execute disconnection on the old and registration on the new, in immediate sequence. This is where downtime occurs, usually minutes.
- Test with own number: receive, reply, send media, trigger a template.
- Reconnect integrations one by one, testing each.
- Monitor the first 48 hours observing delivery, errors, and number quality.
The real cost of a poorly planned window
Operation with 320 conversations per day and average ticket of R$ 480.
Migration during business hours vs off-peak
Twenty-five minutes of downtime cost little when no one is messaging. The same procedure, done at 14h on a Tuesday, creates queues, customers without responses, and the impression of a disorganized company precisely for those messaging at that moment.
What happens with quality and tier
A common question: does migrating reset the number’s reputation? No. Quality and sending limits are attributes of the number in Meta’s infrastructure, not the provider. What changes is the technical intermediary.
But there is a real indirect effect: in the first days, the sending pattern usually changes — new templates, automations reconnected, possible test sends. It’s a period when it’s wise to reduce volume and observe, because errors appearing then are usually configuration issues, not reputation. The correct reading of these indicators is in number quality.
How to evaluate the new provider before deciding
Switching just to switch often repeats the problem elsewhere. Six questions that reveal more than any sales presentation:
- Does the company remain the owner of the Meta account? If the answer is evasive, it’s the same captivity again.
- How does history export work? Ask to see the file format, not just the promise that "export is possible."
- What is the price per conversation and what is the provider’s margin over the amount charged by Meta?
- What is the support channel and response time when the number goes down? Ask for a written commitment with coverage hours.
- How many numbers and agents fit in the plan before moving to a higher price tier?
- Is there a trial period with a secondary number? A confident provider grants this; one who refuses is avoiding comparison.
It’s also worth talking to two current customers of the provider, chosen by you and not recommended by them. Five minutes with current users reveal what no sales proposal mentions — especially about support behavior on problem days.
The first thirty days with the new provider
Migration ends on the switch day; validation takes a month. What to monitor during this period:
- Template delivery rate, compared to the previous provider. A significant drop indicates configuration issues, not reputation.
- Sending errors by category, especially those related to service window and unapproved templates.
- Automation behavior, which is often the part that breaks silently — the flow still exists but stops triggering.
- Support response time on the first real occurrence, which is the only honest way to evaluate what was promised at sale.
- First month cost closing, checking if the charged amount matches the agreed per conversation.
Keep reports from the old system at least until this closing. Comparing month to month is the only way to know if the switch delivered what motivated the decision — and if not, to identify it early enough to reverse.
When not to migrate
Three situations where postponing is the better decision: on the eve of a campaign or peak date, when the company is undergoing verification with Meta, and when the number is under quality restriction. In the last two cases, changing the setup during an ongoing evaluation usually prolongs the process rather than resolving it — and a number already under observation shouldn’t receive any avoidable changes.
It’s also worth postponing when the team is incomplete, on collective vacation, or in operational peak. Migration requires people available to test and fix issues in the first hours, and the savings of doing it "when possible" usually cost more than waiting two weeks for the right moment.
Mistakes that turn migration into a crisis
- Canceling the old provider before completing migration. You lose access to history and, in some cases, to support during the process.
- Migrating without approved templates at the destination. The company can’t start conversations for days.
- Forgetting integrations. The website keeps pointing to the old endpoint and leads disappear unnoticed.
- Not notifying the team. An agent who sees the system down starts responding via personal phone, and the resulting mess takes weeks to fix.
- Migrating just for price, without testing the destination. Request a trial period with a secondary number before moving the main one — the number that supports operations should not be a guinea pig.
When done with preparation, migration is a half-hour procedure with almost no impact. Done impulsively, it’s the kind of event the company remembers for months — and that is often blamed as a "WhatsApp problem" when it was actually a planning problem.
Frequently Asked Questions
What is lost when migrating WhatsApp API providers?
The number, the commercial account on Meta, the accumulated quality and tier remain. Templates usually need to be recreated and reapproved at the destination, and conversation history, tags, funnel, automations, and reports usually stay in the old system — so export must be done while the contract is still active.
Does migrating providers reset the number’s quality and limit?
No. Quality and tier are attributes of the number in Meta’s infrastructure, not the intermediary provider. What usually happens in the first days are configuration errors — new templates, automations reconnected — which can be mistaken for reputation drops but have another cause.
How long is the number offline during migration?
Downtime is usually minutes, concentrated between disconnection from the old provider and registration on the new one. Impact depends almost entirely on the chosen time: the same procedure that affects two conversations on a Sunday night affects dozens if done during peak on a Tuesday.
Each conversation tagged in the right campaign
VeyloCRM identifies the origin of each conversation, responds immediately with a screening question, distributes to the team, and shows cost per sale for each campaign.