Fear of migration is the primary reason merchants stay with underperforming payment processors. The risk is real but manageable: with the right plan, merchants can switch processors without losing a transaction, interrupting a subscription, or forcing customers to re-enter card details. This guide walks through every step.
Before You Start: Migration Readiness Assessment
Before initiating a processor migration, confirm:
- Contract review: Check for early termination fees, notice periods, and any provisions about data export
- Stored cards inventory: How many customers have saved payment methods? Are they subscriptions or one-click checkout cards?
- Active subscriptions: How many active recurring billing relationships are running? What is the next billing date?
- Compliance status: Is your PCI status current? Switching processors may require a new SAQ with the new provider.
The Migration Timeline
Week 1–2: New Processor Setup
- Complete onboarding with the new processor (ConvesioPay’s onboarding takes hours, not weeks)
- Install and configure the new WooCommerce plugin in staging environment
- Configure fraud rules, 3DS settings, and payment method mix
- Set up webhooks and test notification delivery
- Run full test suite on sandbox: happy path, declines, refunds, 3DS challenges
Week 3: Parallel Processing Period
- Enable both the old and new processors in WooCommerce
- Route a small percentage (5–10%) of new transactions to the new processor
- Monitor authorization rates, error rates, and checkout behavior on the new processor
- Verify settlement is arriving in your bank account as expected
- Do NOT migrate subscriptions yet — only new transactions
Week 4: Stored Card Migration
This is the technically complex step. Stored cards must move from your old processor’s token vault to the new processor’s vault.
- Request a token migration from your old processor. Many processors will facilitate a secure token export to a competing processor — this is a card network requirement. They may not volunteer this; you need to ask explicitly.
- The token migration typically requires coordination between both processors and takes 1–3 weeks to complete once initiated.
- After migration, validate a sample of transferred tokens by running test charges on the new processor.
- Customers with successfully migrated tokens never re-enter their card details.
Week 5–6: Subscription Migration
- Update WooCommerce Subscriptions to charge through the new processor
- Time subscription cutover to occur well before the next billing cycle (minimum 2 weeks buffer)
- For subscriptions using payment methods that couldn’t be migrated, send targeted email asking customers to update their payment method
- Monitor the first renewal cycle closely for failures
Week 7: Full Cutover
- Route 100% of new transactions to the new processor
- Remove or disable the old processor plugin in WooCommerce
- Notify your old processor of termination (in writing, per contract terms)
- Confirm any final settlements have been received from the old processor
- Archive your old processor’s transaction data (you need 7 years for tax/compliance)
Common Migration Risks and How to Avoid Them
| Risk | Mitigation |
|---|---|
| Subscriptions fail after cutover | Parallel testing period; staggered subscription cutover; network tokenization |
| Token migration refused by old processor | Escalate — card network rules require token portability upon merchant request |
| Settlement gaps during transition | Maintain bank account buffer for 2 settlement cycles during parallel period |
| Old processor early termination fee | Negotiate waiver, or calculate whether migration ROI justifies the fee |
| Webhook configuration errors | Thorough sandbox testing before any live traffic |
ConvesioPay’s onboarding team supports merchants through the technical migration process, including coordination with the outgoing processor on token transfers. Flat rate: 2.9% + $0.30, no monthly fees, no long-term contract.
Ready to get started? Learn more about ConvesioPay or view pricing.