In This Article
Short answer: Restore your old texts from a Google One backup during the Android setup wizard, on a phone you have just signed into or freshly reset. If you already finished setup, there is no in-Android button to do it after the fact yet, so the working route is to back up anything new, factory reset, and pick the backup again at first boot. Skip all of this if your messages live on the carrier (Verizon Messages, T-Mobile Message+) or a SIM card; those need their own tools.
Switching phones is mostly painless now, because Google One quietly saves your SMS, MMS, and RCS history right alongside contacts and call logs. The snag is the timing. That restore window only opens during the initial setup of a new device, so the moment you breeze through onboarding without ticking the box, the option is gone. This guide walks the correct restore path on current Android 15 and Android 16 hardware, and it is honest about where the path forks.
We will cover the supported flow first, then the factory-reset workaround that most people actually end up needing, and finally the limits Google tends not to advertise. RCS history, large attachments, and dual-SIM threads each behave a little differently, and knowing that up front saves a lot of squinting at half-restored conversations.
If you are already deep in your phone’s messaging settings, a few neighbouring guides are worth keeping open:
- How to Use Android Messages on the Web (Messages.google.com Full Guide)
- How to Remove Fake Virus Messages on Android
- How to Disable Google Weather Notifications on Android
- 5 Best Tools for Restoring Old Photos on Android
- Planning a reset? Learn how to back up and export your texts before you reset so nothing slips through.
Confirm a backup actually exists
Before you wipe anything, prove the backup is real and recent. Open the Google One app, tap Storage, and find the Device backup row. The detail screen lists the most recent SMS or RCS backup with a timestamp. If that date is months old, or the row is missing entirely, a restore will not bring back your newest threads, so go to Settings, then Google, then Backup, and force a fresh run before you go any further.
Give the backup room to finish. It wants the phone on Wi-Fi, charging, and left alone, ideally for a couple of hours. On a Pixel 9 the run often wraps inside half an hour; a Samsung handset leaning on Smart Switch can take noticeably longer. The point is not the exact minutes, it is that a backup mid-upload is not a backup you can trust yet.
| Backup signal | What it tells you |
|---|---|
| Recent SMS timestamp in Google One | Safe to proceed; your latest threads are captured |
| Backup row missing or months old | Run a fresh backup first, or you will lose recent texts |
| Backup still uploading | Wait on Wi-Fi until it completes before resetting |
The official setup-wizard restore
This is the route Google actually supports, and it only appears once: on the initial setup screen labelled Copy apps and data. On a new or freshly reset phone, sign in with the same Google account that holds the backup, choose A backup from the cloud, pick the source device, and tick SMS messages along with anything else you want carried over. The wizard pulls it all in one pass.
Two caveats are worth banking before you start. First, keep it on Wi-Fi; cellular restores get throttled and stall on anything media-heavy. Second, mind the Android version. Google’s setup flow expects the new phone to be on the same Android version as the source, or a later one. Restoring a backup onto an older build can quietly drop data or refuse outright, which is the kind of failure you only notice days later when a thread is missing.
Plan your patience around the size of the backup, not a stopwatch. A texts-only restore is usually done well under an hour. A large, media-heavy backup is a different animal: per Google’s own guide to backing up and restoring an Android device, a restore can take up to 24 hours to complete. If yours is mostly photos and attachments, start it before bed rather than before a meeting. You can read Google’s own guide to backing up and restoring an Android device for the supported step-through and that timing caveat straight from the source.
| At the setup screen | Do this |
|---|---|
| Choose your source | Pick A backup from the cloud, then the right device |
| Select what carries over | Tick SMS messages along with anything else you want |
| Connection | Stay on Wi-Fi so a media restore does not throttle or stall |
| Android version | Make sure the new phone is on the same build or later |
If you already finished setup
Here is the part nobody enjoys. As things stand on the stable channel, Android does not expose a button to restore your old SMS after setup is done. If you have already sailed past Copy apps and data, the working route is the blunt one: back up anything not yet captured, then go to Settings, System, Reset options, Erase all data for a full factory reset. On reboot, the setup wizard offers the restore again, and this time you take it.
That said, do not treat the reset as gospel forever. An in-app backup and restore feature inside Google Messages, which would pull your chats back automatically on sign-in without any reset, has been in testing for a while now. It is rolling out gradually and is not generally available yet, so it is not your fix today, but it is coming. Android Authority’s rundown of the Google Messages backup and restore feature lays out how it is meant to work; you can follow Android Authority’s rundown of the Google Messages backup and restore feature if you want to track its progress.
If you can see the reset coming, you have a cleaner option than the wipe. Third-party tools such as SMS Backup and Restore (from NDot Apps) read your texts into a local XML file you control, so you can simply import them after the reset, no setup-window gamble required. The same logic applies if you would rather hold a portable copy: it is worth taking a minute to back up and export your texts before you reset, since a file in your own hands survives anything the cloud window does.
| Your route | What it costs you |
|---|---|
| Factory reset, then setup-wizard restore | A full wipe; only the Google One backup comes back |
| Local XML export before the reset | A few minutes up front, but a copy you fully control |
| Wait for the in-app Messages restore | No reset later, but it is not generally available yet |
Limits worth knowing
RCS is the big asterisk. Those chats live in Google Messages and back up on a separate track through end-to-end encrypted Messages backup, which is gated behind your device screen lock and a backup PIN. No screen lock or PIN on the source phone means no encrypted backup, which means the RCS history simply will not come back. Google’s notes on end-to-end encryption in Messages spell out the requirement; if that is your situation, read Google’s notes on end-to-end encryption in Messages before you wipe, because there is no recovering it afterward.
Two smaller gotchas round out the list. MMS attachments only restore if they were under 25 MB at the time of backup, so that one enormous video someone sent you may not survive the trip. And dual-SIM phones restore each SIM slot to whichever slot the new handset calls primary, which can scramble threads. Reassign your SIM slots in Settings before you open Messages and you will dodge the worst of the mix-up.
| Cause | What it limits |
|---|---|
| No screen lock or backup PIN on source phone | RCS history does not restore at all |
| MMS attachment over 25 MB at backup time | That attachment is dropped from the restore |
| Dual-SIM device, slots reported differently | Threads can land on the wrong SIM and scramble |
| Restore onto an older Android version | Data can silently drop or the restore can fail |
The restore, step by step
Here is the whole thing in order. Work down the list, and do not skip the backup check at the top; it is the one step that turns a clean restore into a salvage job if you get it wrong.
- Verify the backup. Open Google One, Storage, Device backup, and confirm the SMS line is recent.
- Force a fresh backup if needed. Settings, Google, Backup, Back up now, then wait for it to finish on Wi-Fi.
- Factory reset the target device. Settings, System, Reset options, Erase all data, then confirm.
- Sign in during setup. Use the same Google account, choose the recent backup, and tick SMS messages.
- Open Messages and let it settle. Threads fill in over the first half hour; do not force-stop the app while it syncs.
Common questions
| Question | Short answer |
|---|---|
| Restore SMS without a reset? | Not via Google yet; a third-party XML import is the workaround |
| Will RCS come back? | Only with end-to-end backup plus a screen lock or PIN |
| Android to iPhone? | No; use Move to iOS or a Pixel transfer cable instead |
| How long are backups kept? | Deleted after 57 days of device inactivity |
Can I restore SMS without resetting the phone? Not through Google’s own tooling, at least not yet. A third-party app like SMS Backup and Restore can import an XML file you exported earlier, and Android itself only offers the cloud restore at first boot. The in-app Messages restore that would change this is still rolling out and is not something you can rely on today.
Will my RCS messages come back? Only if end-to-end backup was switched on with a screen lock or PIN on the source phone. Without that, the RCS threads stay on the old device or sit in an encrypted blob nobody can open, so there is nothing to restore.
Does this work between Android and iPhone? No. Google’s backup format is Android only. For a cross-platform move, use Apple’s Move to iOS app when setting up a new iPhone, or Google’s transfer-cable flow when setting up a new Pixel.
How long are SMS backups kept? Google One holds your backup for as long as the device stays active. Once a device goes quiet, its backed-up data is deleted after 57 days of inactivity, so a phone left in a drawer for two months is not a safety net you can count on.
The verdict
If you have not set up the new phone yet, you are in the easy lane: sign in, pick the backup, tick SMS, and walk away for half an hour. If setup is already behind you, accept the reset-and-restore for now, and use the moment to switch on Messages end-to-end backup so the next migration is far less of an ordeal. With the in-app restore on the way, this is one of those chores that should get easier, not harder, over time.
