Switching a recovery tool looks, on a vendor page, like a weekend project: connect the processor, import the settings, turn it on. The migration ledger tells a longer story. Every switch moves more than a login. It moves retry schedules tuned over months, card update links embedded in old emails, cancel flows your customers have already seen, and a body of historical evidence about which messages your specific subscribers actually answered. A ledger, written before the switch, is how you avoid discovering those assets by losing them.
Line one of the ledger is the failure queue itself. At any moment there are accounts mid-recovery: a retry scheduled for Thursday, a customer who promised to update a card on payday, a save offer already accepted and waiting on its next charge. A switch that starts the new tool from a clean slate abandons those accounts at the exact midpoint of their best chance. The ledger names them, with their next action and date, and the migration is not finished until each one has been carried across or deliberately closed. Vendors rarely ask about this list. Ask yourself, in writing, before the demo call.
Line two is pricing arithmetic done on your own volume, not on a pricing page's example business. Percentage-of-recovery models and flat fees diverge as recovery succeeds, and the month you are most likely to evaluate a switch, a bad month, is the month that flatters the percentage model most. Run twelve months of your recovered revenue through both shapes. That exercise is the honest core of what to weigh when you look for a Churnkey alternative that charges flat: not which logo is better, but which cost curve you want attached to your own success, and what the exit from each pricing shape looks like if you switch again.
Line three is the evidence archive. Your old tool holds the record of what worked: which retry timing recovered the annual plans, which subject line the finance managers opened, which decline families never recovered no matter what you sent. Export it before the contract ends, in a form you can read without the tool. Too many migrations keep the settings and lose the learning, so the new tool starts optimising from generic defaults while two years of your subscribers' behaviour sits in an account nobody can log into by spring.
Line four is smaller and purely human: the customers currently inside a cancel flow or a pause. Their experience spans the switch. A save offer made under one system must be honoured under the other, at the same terms, on the same dates, or the business has taught a careful customer that its promises expire with its software contracts. The ledger lists every open promise by name. It is usually a short list. It is the list most likely to generate the angriest email you receive this year if it is forgotten.
Write the four lines before you sign anything, and the migration conversation changes. Instead of asking a new vendor whether switching is easy, you can ask what they will do about each named item, and judge the answers one by one. Easy is a claim. A carried queue, honest arithmetic, an exported archive, and honoured promises are a plan.
That plan-first standard is what Swipe Again publishes its own terms against: a flat fee you can run through your ledger in minutes, and recovery work that starts from your existing queue rather than discarding it. If a switch is on your table this quarter, open the ledger first. Four lines, an afternoon, and the decision that follows will be one you can defend in December, not just in the demo.
Top comments (0)