First principle: Never close your existing account until the new one is approved, tested, and live. Running parallel accounts for a short overlap period is the safest way to switch without a payment gap.
The right order for switching processors
Identify why you're switching and what you need
Rate reduction, account stability, chargeback support, high-risk approval, or subscription billing capability each point to different processor options. Be clear on your actual need before applying anywhere.
Get a new account approved before notifying your current processor
Some processors accelerate fund holds or reviews when they detect an outgoing transfer. Apply for your new account, get approved, and have gateway credentials in hand before touching your current setup.
Plan your subscription migration separately
Active subscriptions linked to your old processor can't just be moved; you either need to re-bill customers on the new account or use a card vault migration service. This step requires a specific plan before you switch anything.
Test the new gateway with live transactions before full migration
Run a small percentage of new orders through the new processor before migrating fully. Confirm authorizations, settlement timing, and reporting all work correctly before committing.
Migrate fully, then close the old account on your timeline
Once the new account is confirmed stable, shift all volume. Keep the old account open for 30 to 60 days to handle any late chargebacks or refund requests tied to old transactions before formally closing it.
The most common mistakes
- Closing the old account before the new one is live and confirmed
- Not having a subscription migration plan before switching gateways
- Applying to multiple processors simultaneously (triggers risk flags)
- Switching processors mid-month and creating settlement confusion
- Not reviewing the new contract's termination fee structure before signing
- Assuming all your current features (recurring, Level 2/3, specific card types) are available on the new account without confirming
“We thought switching processors would take two weeks. Cambridge mapped out the subscription migration, coordinated the gateway transition, and kept us running without a single day of downtime. It took six weeks done right, but we never missed a beat.”Subscription software company 15,000 active subscribers migrated cleanly