Move your SMS archive to a new Android phone
Bring your useful SMS history to a new phone with a portable HashKeep backup, then settle in with a clear handover and recovery plan.
Short answer
To move your SMS archive to a new Android phone, create a portable HashKeep Drive backup on the old phone and save its passphrase. On the new phone, choose that backup in HashKeep, enter the passphrase and restore. Your recovered records appear inside HashKeep. Keep the old phone available until you have opened the messages you wanted to bring.
Unboxing a new Android phone is the fun part. Finding the text with next week's appointment details is the part that makes it feel like your phone. A useful move carries across more than apps: it brings the records you still want to read into a place where you can find them.
If you use HashKeep, you can move your SMS archive with a portable Drive backup and its passphrase. The process has a natural order: prepare the archive on the old phone, create the portable copy, open it on the new phone and settle into your new setup. Keep the old phone available through that handover, and you can do each stage with the source still close by.
Decide where you want to find your messages
HashKeep restores messages into its own archive. You can open the app on your new phone and read those recovered records there; current restore does not put them into the Android Messages inbox. Portable passphrase-protected Drive backups support this move. Scheduled backups and device-bound local files require the original device key, so choose the portable route for a new installation. These distinctions are documented in the HashKeep privacy policy.
Portable local backups are available in Internal Testing from version 0.2.0. Create a new portable .hkv file with a passphrase, transfer the file through storage you control, then select it in HashKeep on the destination and enter its phrase. This route needs no Google Drive account. Older device-bound files still need the original key. The steps below describe the separate portable Drive route.
That gives the archive a clear role alongside the phone's setup process. Your daily messaging app handles ongoing conversations. HashKeep gives you a separate place to find the SMS records you preserved. For someone who mainly wants an old delivery reference or an appointment confirmation, recovering that readable history may be the main goal.
For the rest of the phone, use the appropriate Android or manufacturer transfer process. Google's Android backup guide explains that restore behavior varies by phone and Android version, and that app data coverage varies. Treat your HashKeep archive as its own part of the move rather than assuming a general device transfer has handled every app's records.
Start with the messages you want to bring
Open HashKeep on the original phone and spend a moment with the archive itself. Find a recent message, an older one you care about and a sender you recognise. This gives you useful reference points for the move and confirms that the records you have in mind are already in the archive you are about to back up.
Choose examples you can recognise without writing their private contents into a migration note. “Dentist appointment in September” or “last delivery confirmation” is enough as a personal reminder. A familiar date and sender often make a better reference than the total number of messages, especially when the new installation may also collect newer records.
This is also the moment to separate SMS from other history you want to move. HashKeep's current archive covers SMS, not MMS, RCS or call logs. Use the relevant service's transfer or backup process for those other records. The guide to SMS and RCS backup differences explains why a single conversation view can contain more than one message type.
Pack a portable copy on the old phone
Create a portable backup in HashKeep with a passphrase you have saved securely. Allow the upload to Google Drive to complete, then note the account and backup date. Those two details make the file easier to recognise when you use the backup chooser on the new phone.
The passphrase deserves its own labelled password-manager entry. If your manager is already available on a computer or another device, use that route to find the entry once. It is a small preparation step with a practical payoff: the new phone can be empty and you still know how to retrieve the secret you need.
Think of the portable backup as a packed box with a date on it. It contains the archive captured when that backup was made. A message received later belongs to a later snapshot. If something important arrives while you are setting up the new phone, bring it into the archive and create a newer portable backup before finishing the handover.
There is no need to turn the move into a complex filing system. A protected note identifying the Google account, the completed portable backup and the matching passphrase entry is enough to keep the pieces together. Our passphrase recovery guide gives a fuller example if you have several retained backups or older passphrases.
Open the archive on the new phone
Install HashKeep on the new Android phone and use the Google account that holds the portable backup. In the app's backup chooser, select the backup you prepared for the move. Enter its saved passphrase when prompted, then work through the restore preview and confirmation shown in the app.
The preview helps you understand what is about to be added. Some records may already be present, for example if you have imported messages into the new installation. HashKeep's restore process identifies new and duplicate records so that the operation is about bringing the archive together, rather than requiring you to begin with an artificially empty phone.
Once the restore finishes, open the familiar examples you selected earlier. Read the date, sender and body of a message you actually value. Then browse a second part of the archive, such as an older month. This is a satisfying and concrete result: the history you wanted is now readable on the device you plan to use.
If the backup you expect is missing from the chooser, start with the account and completed-backup details in your note. If the file opens with an error, use the passphrase associated with that backup's date. Working from those identifiers is more useful than guessing whether a similarly named scheduled backup is the right one.
Give the handover a clear finishing point
A move can span an afternoon or several days. Choose a point when the old phone stops being the place where you expect to gather new records. Until then, keep it available and consider whether another portable snapshot is useful. That makes the end of the handover a deliberate decision instead of an accidental gap.
For example, imagine creating a backup on Saturday morning and moving your SIM later that day. A useful booking message arrives on the old phone between those events. You can make a final portable backup after that record appears in HashKeep, then restore it on the new installation. Existing matching records are handled as duplicates during the merge, while newly included records can be added.
A clear cutoff also helps you interpret the archive later. Saturday morning's file represents one state; Saturday afternoon's file represents another. Keep the version that serves your recovery needs, and retain older versions deliberately when they contain history you still want. The newest file and the most useful historical file are not always the same thing.
Set up the new phone for the next useful message
Restoring old records and capturing future ones are separate parts of settling in. Review HashKeep's permissions and backup settings on the new phone, then use the app normally. When a harmless new SMS reaches your phone, look for the corresponding record in HashKeep so you understand how the new setup is working.
Choose local retention to match what you use the archive for. Free keeps a 30-day local window, while Pro offers longer periods up to five years. Someone who uses the archive for recent confirmations may want a different window from someone who frequently returns to older records. The retention guide explores that choice in more detail.
Give optional Delivery its own decision if you use it. A new phone is a sensible time to confirm that the email address or chat destination still fits your needs. Backup recovery and readable forwarding serve different purposes, so restoring the archive is a good milestone even if you choose to configure Delivery later.
Finally, create a portable backup from the new installation when you want a recovery copy of its current archive. Label its passphrase entry and account details as clearly as you did for the move. The new phone then becomes an ordinary working device with its own recovery arrangement, rather than the final destination of a one-time transfer.
Make space for the rest of your phone move
You can keep the SMS archive task small within a larger migration. One line in your move plan can say “HashKeep: portable backup restored and familiar records opened.” Give photos, authenticator access, messaging apps and other important data their own lines and follow the corresponding services' instructions.
This approach is particularly helpful when one item takes longer than the others. You can know that your SMS archive is ready while another app continues its own transfer. It also avoids treating a phone that looks familiar on the home screen as the only measure of success. The records you need and the accounts you use provide clearer milestones.
Once you are happy using the new phone, follow the old device manufacturer's guidance if you plan to erase, sell or recycle it. Our factory-reset preparation guide covers the archive side of that final step. Keeping preparation and erasure in that order gives you time to resolve any missing item while both devices are available.
What we are planning next
We are planning an additional choice to restore SMS into Android's system SMS inbox. That work is planned and has not been released. For now, the migration described here restores your portable backup inside HashKeep, where you can browse and read the recovered records.
Finish with something you can use
The best endpoint is simple: open the new phone, find a message you wanted to keep and read it. You have moved the archive successfully when the useful history is there, the new installation fits your routine and its recovery details have a clear home. Then you can get back to enjoying the new phone.
Sources
- HashKeep privacy policy
Checked 13 October 2026. Portable Drive backup and archive-only restore.
- Back up or restore data on your Android device
Checked 13 October 2026. Device backup is a separate workflow and app data coverage varies.