Moving Your Apps to a New Android Phone Without Losing Data
Reinstalling apps is the easy part; carrying their data across is where people lose chat history, saves, and offline files. This guide compares OEM transfer tools, Google cloud backup, and adb export, explains exactly which apps will refuse each route, and gives an order of operations that covers the most ground first.
Most people think migrating a phone means putting the apps back. That part is trivial — you can even pull the APK off the old device and install it directly. What actually hurts is everything attached to those apps: login sessions, chat history, offline maps, downloaded playlists, game progress. A sloppy migration costs you a dozen re-logins and a pile of files you will never get back.
The mental model that fixes this is simple: the APK is disposable, the data is not. Installer files can be re-downloaded from anywhere; application data usually exists in exactly one place. So decide how the data travels first, then worry about how the APKs get installed.
Here are three routes, ordered from broadest coverage to finest control.
Route 1: The OEM transfer tool
Samsung Smart Switch, Xiaomi's Mi Mover, Huawei Phone Clone, and the OPPO/vivo equivalents all do roughly the same thing: move app packages plus whatever Android allows to be backed up over a Wi-Fi Direct link or cable.
Old phone: Settings → System → Transfer / Phone Clone
New phone: same screen, choose "I'm the new phone"
Keep them close; over 5 GHz direct Wi-Fi expect 30–80 MB/sIt is the least effort and needs no PC. The limits are real, though:
- Cross-brand transfers are unreliable. Chat history comes across because WeChat, WhatsApp, and Telegram ship their own migration protocols — not because the tool did anything clever.
- Big OS gaps break it. Android 9 to Android 15 frequently results in apps that simply fail to restore.
- Encrypted data stays put. Anything with
allowBackup=falseis silently skipped.
Route 2: Google cloud backup
Since Android 9, Google's backup is end-to-end encrypted and covers installed app lists, Wi-Fi passwords, SMS/call history, and app data for apps that permit it.
# Force an immediate backup on the old device
adb shell bmgr backupnow --allOn the new phone, pick "Restore from old device" during setup and sign into the same account. Constraints you should plan around:
| Constraint | What it means |
|---|---|
| 25 MB per app | Game saves, offline video, and large asset caches exceed this and are dropped |
allowBackup=false | Banking, payment, and many IM apps opt out; re-login is the only option |
| Cadence | Typically once a day, on charger and Wi-Fi — your last backup may be days old |
| Needs Play services | Devices without GMS can't use this route at all |
Route 3: adb export
When you want to know exactly what moved, use adb. Pull the APK first, then handle data separately.
# 1) List third-party packages
adb shell pm list packages -3
# 2) Export the APK itself (no root needed)
adb shell pm path com.example.app
adb pull /data/app/com.example.app-xxxx/base.apk ./com.example.app.apk
# 3) Export one app's private data (prompts for a password)
adb backup -apk -shared -f backup.ab com.example.appRestore with:
adb restore backup.abCaveats that will bite you:
adb backuphas been progressively restricted; on Android 12 and later many packages yield almost nothing. Treat it as a legacy tool.- Restore requires the same package name and same signing key. This is also why installing an APK someone sent you never inherits your existing data.
-sharedpulls in Photos and Downloads too, so backup files balloon fast.
Apps that will refuse every route
For these, only the app's own transfer feature works:
- WeChat: Settings → Chats → Chat History Migration, over the same Wi-Fi. Do not rely on Google backup — it keeps only a short window and not all message types.
- Banking and payment apps: re-login plus device verification. That is the security model working, not a bug.
- Games: bind to an account (Play Games, Facebook, publisher ID). Save-file backup is not a strategy.
- Enterprise IM: the admin console may pin the device; ask IT to unbind.
An order of operations that covers the most ground
- Offload photos and downloads to cloud or PC first — keep them out of the app-data question entirely.
- Record the third-party package list (
adb shell pm list packages -3) so nothing gets forgotten. - Run the OEM transfer tool as the broad first pass. It has the highest hit rate for the least effort.
- For each app that opens logged-out or broken, go through its in-app migration feature individually.
- Compare version numbers:
adb shell dumpsys package <pkg> | grep versionName. If the new phone has a newer build than the old one, install the matching APK before restoring data — cross-version restore often fails silently. - Only after the new phone is fully verified should you wipe or recycle the old one.
To predict which bucket an app falls into before you start, check its manifest flags: aapt dump badging app.apk | grep -i backup. A false there tells you immediately to plan for a manual re-login instead of wasting an hour on adb.