If Google Maps Timeline is missing on a new phone, preserve the old phone and check the correct Google Account and available Timeline backup before clearing anything. Timeline is now managed on your device, and moving phones is not necessarily the same as signing into Maps and seeing all earlier history. An available encrypted backup may provide an import route.
That distinction changes the troubleshooting order. Clearing app data, reinstalling Maps or factory-resetting the old device can remove information you may still need. Start by finding out where the history exists and whether an appropriate backup is available.
This guide uses Google’s Timeline management instructions. Interface labels and supported features can differ by platform and app version. Follow the matching instructions for your phone; do not assume an older desktop Location History tutorial describes the current system.
Check whether the history is missing or simply in another place
Open Maps on the new phone and confirm the account selected in the profile menu. Many people use a personal account, a secondary account and a work account on the same device. Seeing your saved places or familiar profile photo does not necessarily establish that you selected the account used for Timeline.
Review a specific past day rather than judging the entire history from today’s empty view. Choose a day you remember clearly, such as a trip or a commute, and compare that same date on the old phone if available. Keep the comparison focused on identical dates and accounts.
Also separate Timeline from search history, saved places, photos and navigation directions. These features can contain related information, but one is not a complete substitute for another. A saved restaurant appearing on the new phone does not prove that the old phone’s detailed Timeline data transferred.
Why a phone change can expose a storage difference
Google’s current model stores Timeline information on the device, with an optional encrypted backup that can help move or recover data. A Google Account login and a device backup are therefore different parts of the process. Do not assume that every past visit exists in a universally synchronized web view.
If the old phone still displays the missing history, that is a valuable observation. Preserve the device and review its Timeline backup settings before doing destructive troubleshooting elsewhere. The phone showing the data is evidence of a potential source, not proof that another phone has already received a copy.
If neither device shows the history, investigate the account, earlier settings and available backups. Avoid promising yourself recovery before verifying that a usable copy exists. Data that was never backed up, or that was deleted under the chosen settings, may not be recoverable.
A quick decision table
| What you find | What it suggests | Next action |
|---|---|---|
| Old phone has history; new phone does not. | Data may remain on the old device. | Preserve it and review backup/import options. |
| History appears under another account. | Account selection was part of the issue. | Compare the same account on both devices. |
| A relevant device backup is listed. | An import path may be available. | Follow Google’s current backup instructions. |
| No device or backup contains the dates. | There may be no recoverable copy. | Check prior settings without assuming restoration is possible. |
This is a triage table, not a guarantee. A listed backup still needs to be the right source, and its date matters. A recent new-phone backup containing little history is not automatically a replacement for a useful old-phone backup.
Preserve the old phone first
- Keep it charged and securely in your possession.
- Confirm that the desired Timeline dates are visible.
- Record which Google Account is selected.
- Review the Timeline backup status and device information.
- Follow the official backup process if available and appropriate.
- Do not erase the device until the new phone’s history has been checked.
Do not send screenshots of precise home, work or travel locations to a public forum. A simple private note saying which dates are present is enough for your own comparison. If support needs an image, minimize unrelated location details and use an established support channel.
If you are trading in the old device, separate the trade-in deadline from your recovery checks. A hurried factory reset can eliminate a useful source. Make a deliberate decision about preserving data before completing the handover requirements.
Find and review the available Timeline backup
Google’s instructions describe reviewing Timeline backup through the relevant Timeline controls. In the supported Android interface, an available backup can be selected from the backup area, with an import option associated with the device. Check the current instructions rather than relying on the exact placement of an old screenshot.
Read the device name and backup date carefully. Several similarly named phones may be listed after upgrades, replacements or resets. Choose based on the source you actually used, not merely whichever entry appears first.
Keep a record of the source device and the dates you expect to recover. This makes the final comparison meaningful. Importing something without knowing what it contains can create a misleading feeling of completion when important months remain absent.
Import cautiously and verify representative dates
Follow Google’s supported import process for the selected backup. Keep a stable connection and follow any visible guidance about completion. Do not repeatedly start unrelated imports because the first screen does not immediately show every expected date.
After the operation, check a small set of representative dates: one recent day, one older day and a memorable trip. Compare the same dates with the source where possible. This is more reliable than checking only the current month.
If the results differ, note exactly what is missing. “January is present but the June trip is absent” is a useful observation. “Everything disappeared” is less helpful when some history has restored. Avoid deleting the source while a discrepancy remains unexplained.
Distinguish historical recovery from future recording
Turning on an appropriate setting today does not recreate locations that were never recorded in the past. Likewise, importing old data does not establish that the new phone will record future visits under the settings you intend.
Review the current phone’s Timeline and location settings separately, including the permissions and options Google documents for your platform. Choose them according to your privacy preferences. Do not enable broad tracking merely because an unrelated guide presents it as a universal fix.
Once configured, check whether a future ordinary day appears as expected. That is a test of the new device’s ongoing behavior. Keep it separate from the question of whether historical data was preserved and imported successfully.
Auto-delete and manual deletion need their own review
A missing older period can reflect a chosen retention setting rather than a transfer failure. Review the Timeline auto-delete settings and any deletion actions you remember taking. Do not assume that a phone upgrade caused a gap simply because you noticed it afterward.
If data was deliberately deleted or aged out under the applicable settings, a new login may not bring it back. Check Google’s current documentation about the effect of deletion and backup. Avoid treating an export or a device backup as an automatic undo button for every past action.
Write down the difference between “not displayed on this device,” “not included in this backup” and “deleted.” These describe different levels of certainty. Use the most accurate description supported by the evidence you have.
Common actions that risk making the problem worse
| Tempting action | Why to pause | Better first step |
|---|---|---|
| Clear Maps app data. | Timeline may rely on local device information. | Locate and preserve the source history first. |
| Factory-reset the old phone. | It may contain the remaining usable copy. | Verify backup and new-phone results before handover. |
| Delete an unfamiliar backup. | It may be the source you need. | Read its device and date details. |
| Enable every tracking option. | It changes privacy settings without proving recovery. | Separate future recording from historical restoration. |
None of these cautions means a reset is never appropriate. It means destructive maintenance should follow an understanding of the storage and recovery situation. Do not sacrifice the likely source while trying to improve the appearance of the destination.
What if the old phone is lost or broken?
Look for a relevant existing Timeline backup through the supported account and device interface. If one is available, follow the official recovery instructions. If none exists, do not assume that an ordinary Google sign-in or a generic phone restore can reconstruct every visit.
If the phone is physically damaged and the data matters, preserve it rather than experimenting with resets. A repair provider can discuss options for the hardware, but nobody should promise access to encrypted information without the required account and device conditions.
If the phone was stolen, securing the device and account remains important. Do not postpone necessary security steps solely to protect a hypothetical recovery route. Follow the device provider’s lost-phone guidance and treat recovery of personal travel history as a separate concern.
Exports are useful records, not guaranteed imports
An export can help preserve information in a readable or archived form when supported. However, downloading a file does not prove that Maps can later import it as fully functioning Timeline history. Check the documented purpose of the export before relying on it for a migration.
Keep exported location information private and store it securely. Such files can reveal home addresses, routines and travel patterns. Do not upload them to a random “Timeline repair” website that requests the entire archive in exchange for an unverified recovery promise.
For personal recordkeeping, you may be able to reconstruct part of a trip from your own receipts, calendar or photos. Label that as a reconstruction. It is not the same as recovered Timeline data and should not be presented as an exact technical record.
Prepare a useful support question
Describe the phone platforms, the Google Account context without exposing secrets, whether the old device still has the data, and whether a backup appears. Include the date range missing and which recovery step you already tried.
For example: “My old Android phone displays Timeline for March through September. The replacement phone uses the same account but does not show those months. A backup from the old device is listed. After following the import instructions, March appears but the later trip does not.” Use your actual facts.
That question is narrow enough to investigate. A public post containing a complete travel map, account email and precise daily routine supplies more private information than most troubleshooting needs.
Before declaring the move complete
Verify historical dates, review future-recording preferences and keep the old source until you are satisfied with the result. If some history cannot be recovered, document that limit rather than endlessly cycling through resets.
A successful migration is more than seeing a familiar account avatar. It means the specific history you wanted is available where expected, the new device follows your chosen privacy settings, and the old device can be retired without losing the only remaining copy.
For a family helping with an upgrade, let the account owner make the privacy choices. Another person’s preference for continuous location history should not become the default without discussion. Explain what is being backed up, which device contains the history and when the old device will be erased. That makes the migration understandable as well as technically careful.
Frequently asked questions
Why is Timeline missing after I changed phones?
Timeline is managed on the device, and signing into Maps does not necessarily move all historical device data. Check the selected account, the old phone and any relevant encrypted backup.
Should I clear Maps data to restore Timeline?
Preserve and identify the source first. Clearing app data or resetting a device can remove information you may still need for recovery.
Can turning Timeline on recover old visits?
Turning it on now does not recreate locations that were never recorded. Historical recovery and future recording are separate tasks.
Is a downloaded export guaranteed to import into Maps?
No. Check the documented export and import capabilities. An archive can be useful for records without being a supported full Timeline restoration file.
Can Google always recover data without a backup?
Do not assume so. If the old device and an appropriate backup do not contain the history, there may be no recoverable copy.
Sources and reporting notes
Official guidance checked October 26, 2026. Google Maps: manage Timeline. Examples, worksheets and checklists are USRPTV editorial analysis. Featured image: AI-generated conceptual illustration, not a screenshot or documentary photograph.
