Moving from another WhatsApp platform to ReplyKit: what transfers, what does not, and a two-week plan with no gap in replies
Switching WhatsApp platforms feels risky because the number, the history and the flows all seem tied to the old tool. Most of that is movable, some of it is not, and the parts that are not are usually the parts you were paying for and not using. Here is what transfers, what you rebuild, and a plan that keeps every customer answered.
Quick answer
Export your contacts and any conversation history as CSV from the old platform, save your templates and flow text, and note which number is on your website and Google profile. In ReplyKit, rebuild flows as plain-language instructions and paste templates as knowledge, pair a dedicated number, run both platforms for a week while you test, then move the public number and cancel the old plan. Chat history stays exportable; the official API's templates and broadcasts do not carry over, by design.
What transfers and what does not
| Asset | Moves? | How |
|---|---|---|
| Contacts and lead details | Yes | Export CSV from the old tool; keep it as your record, and import key facts into the agent's knowledge if relevant |
| Conversation history | As an archive | Export; ReplyKit starts fresh on the connected number, and the old export is your record |
| Quick replies and canned answers | Yes | Paste as Q and A into the knowledge base |
| Chatbot flows | Rewritten | Flows become instructions: role, tone, do, never, hand over |
| Message templates (API) | No | Yes; ReplyKit supplies approved reminder and follow-up templates, replies are free text |
| Broadcast campaigns | No | ReplyKit does inbound replies only; keep a campaign tool if you need one |
| The phone number | Usually a new one | API numbers are tied to Meta; pair a dedicated number and move the public listing |
| Team members | Yes | One shared inbox; everyone replies from it |
The two-week plan
- Day 1. Export contacts, history, templates and flow text from the old platform. Note every place the old number appears.
- Day 2. Sign up, paste your website, upload the price list, and paste the old quick replies as Q and A. Write instructions from the old flow's intent, not its buttons; see writing instructions.
- Day 3. Set services and hours. Run the twenty-message test.
- Day 4. Pair a dedicated number. Keep the old platform live.
- Days 5 to 11. Put the new number on one channel, say Instagram, and let real traffic hit it. Teach from the unanswered list daily. Compare handover rates and booking rates with the old tool.
- Day 12. Move the number on Google, the website and print. Set an away message on the old number pointing to the new one.
- Day 14. Cancel the old plan once the old number's traffic has dropped to a trickle.
Three things people miss
- Consent records. If you ran campaigns, keep the opt-in export. ReplyKit does not broadcast, but the records are yours to keep.
- Flows had hidden rules. "Ask for the postcode before quoting" was a branch in the old flow; make it a line in the instructions.
- The number risk changes. The API number was sanctioned; a number connected to ReplyKit is not, which is why it should be dedicated. See Meta's messaging limits explained and the official platform explained before you decide.
Frequently asked questions
Can I keep my WhatsApp number when moving from an API platform?
Numbers on the official API are tied to Meta's platform; the usual approach is to pair a dedicated number and move your public listings to it.
Does my chat history transfer?
Export it from the old platform as your archive. ReplyKit starts fresh on the connected number.
What happens to my templates and flows?
ReplyKit supplies its own approved templates for reminders and follow-ups, so you do not rebuild yours. Flows are rewritten as plain-language instructions, which is usually simpler.
Will there be a gap in replies?
Not if you run both for a week and move the public number only after testing.
Can I keep broadcasting?
Not from ReplyKit. Keep a campaign tool on the official API if you need broadcasts.
Run both for a week, then switch
Rebuild in an afternoon, test on one channel, move the number when it is proven. 7-day free trial.
Sources and further reading
- WhatsApp Business Messaging Policy · opt-in, opt-out and prohibited-use rules every business must follow
- Meta, WhatsApp Business Platform pricing · per-message pricing for the official API, for comparison
- ReplyKit, Will WhatsApp ban my number for automation? · how Meta's messaging limits and quality rating work
ReplyKit is an independent product and is not affiliated with or endorsed by Meta or WhatsApp. This article is general guidance for running a small business, not legal, financial or regulatory advice.