A safer phone-transfer checklist
Moving to a new phone is mostly automated and mostly fine, with a short list of things the automation reliably does not carry.
This analysis works through the design decisions behind that, and what they cost the people using the result.
What transfers do not move
Two-factor authenticator codes are the most consequential gap. Many authenticator apps store secrets locally and deliberately exclude them from backups, so a transfer that appears complete can leave you locked out of accounts an hour later.
Messaging history is the second. Some apps back up to their own cloud, some to the platform's, and some not at all — and cross-platform moves usually lose it regardless.
Do the recovery work before the transfer
Generate and store recovery codes for critical accounts while you still have the old device working. Once it is wiped, the recovery path that assumed access to it is closed.
Keep the old device intact and charged for a week rather than trading it immediately. Most transfer gaps surface within the first few days.
What to look for
Before wiping anything, sign in to your two most important accounts on the new phone. If both work, the rest is recoverable at leisure.
The things that do not transfer are the things that matter
Device migration tools move what is easy to enumerate: photos, contacts, messages, installed app lists. What they consistently miss is the layer that actually locks people out — authenticator seeds, passkeys bound to the old device's secure element, and app-specific sessions that require a re-login the user cannot complete without the authenticator that did not transfer.
The correct order is therefore the reverse of the intuitive one. Move two-factor authentication before anything else, while the old device still works, because every other recovery path depends on it. A migration that finishes with a full photo library and an inaccessible bank app has failed at the only step that was hard to undo.
It is also worth keeping the old device intact and charged for a fortnight rather than wiping it on the same day. Most migration gaps do not surface immediately; they surface the first time an app asks for verification, which can be weeks later.
What the Tools catalogue shows
Across the 8 tools apps tracked in this catalogue, store ratings run from 4.0 to 4.9, with a median of 4.5. The narrow spread suggests a mature category where the basics are broadly solved and the differences sit in details rather than in reliability.
Google Play Store by Google LLC currently leads on rating at 4.9, and it also carries the largest recorded audience. Neither figure settles the question this piece is about: a high average records the absence of complaints, not the presence of the design qualities described above.
Why this keeps happening
Most of what looks like carelessness here is a resolved trade-off — engagement against clarity, or revenue against restraint. Naming the trade-off makes the pattern predictable rather than baffling, and predictable problems are ones you can plan around when choosing between two products.
