Turn chat exports back into real history, merge old Android databases, and move chats between Android and iPhone — photos, voice notes and stickers included. No subscriptions, no uploads.
pipx install wakitNo Python needed — double-click to open. Apple silicon Macs; the apps aren't signed yet, so see the first-launch step.
wakit grew out of a real migration: dozens of exported chats, an old phone's database, a WhatsApp mod, an iPhone backup — all merged into one history, then carried to a new iPhone.
“Export chat” .zip or .txt from iPhone or Android become proper messages again, with media, captions and the right sender — even exports made on the other person's phone.
Fold an old phone's msgstore.db, a WhatsApp mod or an adb backup into your current one — replies, reactions and calls included, without duplicates.
Read an ordinary unencrypted iPhone backup and merge its chats into Android, matched person by person, photos and voice notes included.
Write your Android history into an iPhone backup and restore it — no paid transfer app, no “Move to iOS” factory reset. Thumbnails, replies and stars carried over.
Favourite and recent stickers move between Android phones and from iPhone, named the way the app expects.
One command-line tool, plus wakit gui: guided steps, file pickers, dry-run and Apply buttons and a live log — in your browser, served from your own machine.
Each step is a dry run first. Check the numbers, add --apply, and wakit writes — after making a backup.
Rooted Android phone.
$ wakit device pull --out phone/ $ wakit import --db phone/msgstore.db \ --export "WhatsApp Chat - Alex.zip" --contact 15551234567 # check the counts, then add --apply --push $ wakit device install --db phone/msgstore.db
Unencrypted iPhone backup, rooted Android.
$ wakit ios-backup backup --out ~/Backups $ wakit device pull --out phone/ $ wakit from-ios --db phone/msgstore.db \ --backup ~/Backups/<device-id> --apply --push $ wakit device install --db phone/msgstore.db
Rooted Android, any iPhone — no jailbreak.
$ wakit device pull --out phone/ $ wakit device pull-media --out phone-media/ $ wakit ios-backup backup --out ~/Backups # then copy it $ wakit to-ios --db phone/msgstore.db \ --backup ~/Backups/edit/<id> --media phone-media/ --apply $ wakit ios-backup restore --backup ~/Backups/edit/<id> --yes
Old phone, mod, or adb backup.
$ wakit merge --old old/msgstore.db \ --new phone/msgstore.db --fuzzy # dry run shows what would be copied; then --apply $ wakit stickers --db phone/stickers.db \ --from old/stickers.db --from-files old/Stickers \ --files-out Stickers --apply
wakit guiEvery command and option as a form, built from the same definitions as the CLI — so the GUI never falls behind.
--apply.ios-backup check --fix repairs the records that make iPhone restores fail with error 205.| You need | For |
|---|---|
| Python 3.9+ | everything (no other Python packages) |
| adb + root | reading/writing WhatsApp on Android |
| libimobiledevice | making / restoring iPhone backups |
| unencrypted backup | anything iPhone (no jailbreak needed) |
Android: yes, root — WhatsApp keeps its database in a folder only root can reach. iPhone: no jailbreak — wakit works through a normal unencrypted backup made by Finder, iTunes, 3uTools or wakit ios-backup backup.
Yes — MIT licensed, no accounts, no limits. The official “Move to iOS” is free too, but it needs a factory-reset iPhone; wakit merges into the iPhone you have.
No. wakit is a program on your computer; the GUI is a page served by your own machine on 127.0.0.1. There is no server, no telemetry.
Android → iPhone: reactions, polls and system notices. iPhone → Android: polls, reactions and calls. Encrypted backups (.crypt14/15, encrypted iPhone backups) are not supported — turn encryption off first.
wakit only edits your own local history database; it never talks to WhatsApp's servers. It isn't affiliated with or endorsed by WhatsApp or Meta, and WhatsApp's database layout can change — always keep backups.
Developed against WhatsApp 2.26 on Android 7.1 (rooted) and iOS 27. Other versions should work; if a dry run looks wrong, open an issue with its output — never share your databases.