The verdict in three sentences
Switching gateways must never take the store offline: you run the old and new provider in parallel (dual-run), then move traffic in stages of 10/50/100 %. The two real traps are migrating recurring tokens (card mandates) and re-pointing confirmation webhooks. With a rollback plan ready, the cutover happens with zero downtime in 3 to 6 weeks.
The step-by-step migration plan
A clean migration is a sequence of stages, each with its risk and countermeasure. Here is the typical plan (2026 order of magnitude).
| Step | Risk | Mitigation |
|---|---|---|
| New provider integration (sandbox) | API bugs | Full e2e tests before production |
| Dual-run 2-4 weeks | Double bookkeeping | Daily reconciliation of both flows |
| Cut 10 % of traffic | Undetected failures | Real-time success-rate monitoring |
| Cut 50 % | Conversion gap | Compare old vs new success |
| Cut 100 % | New provider outage | Immediate rollback to old |
| Migrate recurring tokens | Lost mandates | Planned vaulting / re-tokenization |
| Decommission old | Webhooks still live | Keep listening 2 more weeks |
Golden rule: only decommission the old gateway after 2 weeks at 100 % on the new one with no incident.
What actually takes time
Development is not the bottleneck: subscriptions and KYC are. Here is the realistic time split.
| Workstream | Typical duration | Blocking? |
|---|---|---|
| Technical API integration | 3 - 7 days | No |
| New provider KYC approval | 1 - 3 weeks | Yes |
| Dual-run and monitoring | 2 - 4 weeks | Yes |
| Recurring token/mandate migration | 1 - 2 weeks | Yes if subscriptions |
| Webhook re-pointing + tests | 2 - 4 days | No |
With no subscriptions, migration is simpler (3 to 4 weeks). With recurring payments, budget 5 to 6 weeks to re-tokenize cleanly.
Mini case study
Grace runs a Nairobi subscription box with 1,200 recurring customers and solid monthly volume. She switches gateways to cut fees from 3 % to 2.2 %. The 0.8-point saving on her volume compounds into meaningful annual savings. The dual-run migration runs 5 weeks, re-tokenizing all 1,200 mandates. Zero downtime, zero lost customer. The project pays for itself within a year on fee savings alone.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
FAQ
Can you really migrate with zero downtime?
Yes, thanks to the dual-run: the old gateway stays live while the new one ramps from 10 to 100 %. The store is never without a payment method.
What happens to my recurring subscriptions?
That is the trickiest part. Tokens/mandates must be migrated or re-created on the new provider; budget 1 to 2 weeks and a customer comms plan if re-authorization is required.
How long should I keep both providers?
A minimum of 2 to 4 weeks of dual-run, plus 2 extra weeks listening to the old provider's webhooks after the 100 % cutover.
How do I know the migration is going well?
Compare old vs new success rate in real time at each stage. If the new one underperforms, roll back to the old immediately.
How long in total?
3 to 4 weeks with no subscriptions, 5 to 6 weeks with recurring payments to re-tokenize.
Let's talk about your project. We plan your gateway migration without losing a single sale. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
