Most merchants who know they're overpaying stay put anyway, because the imagined switch involves a dead terminal, lost weekend sales, and hours on hold. A well-run switch is genuinely boring: the new account is approved and tested before the old one is touched, and the cutover is minutes, not days.
The right order of operations
Approval first: the new processing account is underwritten and approved while your current setup keeps running. Nothing changes at the counter yet.
Hardware staged second: new terminals arrive configured, or your existing compatible hardware is re-programmed, and a test transaction settles end to end — before the switch. If anything is wrong, you find out on a test card, not a customer.
Cutover last, at a quiet hour: the moment of switch is choosing which terminal takes the next card. Keep the old account open for a couple of weeks so late chargebacks and residual settlements clear cleanly, then close it in writing.
The questions that prevent surprises
Ask your current processor for your early-termination terms before you commit elsewhere — contracts with liquidated damages clauses are real, and knowing the number turns a scare into arithmetic.
Ask the new processor who owns the hardware, whether your customer card-on-file data can migrate (it usually can, through a supported token migration), and what the first statement will actually look like, line by line, in writing.
Ask both sides what happens to pending settlements on cutover day. The answer should be specific and boring.
What a good switch looks like from the counter
Staff take cards the same way on the same or better hardware; deposits land the next business day; the statement is shorter and legible. The whole event should be a calendar entry, not a story. If a provider can't describe the switch in that level of concrete detail, that vagueness is your answer.
Approve, stage, test, cut over, overlap, close in writing. Six steps, no downtime. Lombard runs this switch for every funded merchant — it's the trade that makes the funding possible, so we've made it a non-event.