If you are about to transfer Telegram chats to a new phone without losing history, the short answer is reassuring but incomplete: in most cases nothing needs to be "transferred" at all, because Telegram stores ordinary conversations on its servers and any client that signs into the same account rebuilds them from the cloud. The incomplete part matters more than the short answer. Secret Chats, locally cached media, exported archives, and session security behave differently, and those are exactly the pieces that quietly fail during a device swap. This guide therefore treats migration as a data-retention and auditability problem rather than a file-copying problem: what is the system of record, what is merely a cache, what can be reconstructed after the fact, and where the boundary lines sit when the answer is "you cannot".
Feature positioning: what actually moves when you change phones
Telegram is a cloud messenger, which means the phone is a client rather than the storage layer. Understanding that single architectural fact removes most of the anxiety around migration, but it also defines the limits. There are two very different classes of conversation inside the same app: cloud chats, which are replicated to Telegram's servers and follow your account, and Secret Chats, which are end-to-end encrypted, device-bound, and never replicated. Everything that follows in this article branches from that distinction, so it is worth holding both halves of it in mind at once: the half that reassures you, and the half that tells you where your responsibilities begin.
Cloud chats: the server is the system of record
Private chats, groups, channels, and bot conversations you have already joined live on the server side of your account. Because of that, message text, message order, sender identity, timestamps, read state, replies, forwarded content, pinned messages, scheduled messages, drafts, and chat folders all reappear on a new device after you authenticate. You are not restoring a backup; you are opening a second window onto the same dataset. In practice this is why a fresh install can look identical to the old phone within minutes on a reasonable connection, and why the order of operations for the cloud portion of your data is simply "sign in, wait for sync".
Two boundaries deserve emphasis. First, syncing is not instantaneous: a very large account with years of media-heavy history will populate progressively, and older media may only be fetched on demand when you scroll to it. Second, the cloud copy follows the account, so anything that ends the account or leaves it unattended long enough to trigger Telegram's inactivity self-destruct setting also ends the cloud history. Cloud retention is durable, but it is conditioned on the account continuing to exist — which is why the account-level checks later in this article come before any device-level step.
Secret Chats: the exception that never migrates
Secret Chats are a separate mode built for end-to-end encryption. The encryption keys are generated and held on the device that created the chat, and Telegram's servers are not a retrieval point for the content. Consequently, a Secret Chat does not appear on a second phone, does not appear on Telegram Desktop, and cannot be reconstructed after you log out or uninstall the app on the original device. As of this writing, Secret Chats remain a mobile-only feature; the desktop client does not offer them. If a conversation matters, this is the moment to decide whether it should exist in Secret Chat form at all, or whether it belongs in an ordinary cloud chat where retention is predictable.
Local cache versus cloud history: the confusion that causes most panic
A large Telegram installation can occupy several gigabytes of device storage, and the storage screen can look alarming. Almost all of that is cache: copies of media the app downloaded so it can display images and play video without re-fetching on every scroll. Clearing cache on one device does not remove anything from your account, and it does not affect what other devices see. The reverse is also true, and it is the trap: media that only ever existed inside a Secret Chat, or files you downloaded to your phone's gallery through an external flow, are outside the cloud retention guarantee. A useful mental rule is that the app's storage screen describes your device, while the chat itself describes your account. Once that rule is internalized, a "missing" photo becomes a question with a definite answer: either it is still in the cloud and will return on demand, or it was never in the cloud at all.
Tip: Before wiping an old phone, open Settings → Data and Storage → Storage Usage on it and review what the cache actually contains. If the size is dominated by auto-downloaded photos and videos from cloud chats, it is replaceable. If you know there is media from Secret Chats, that content has no server-side copy and should be saved out manually first.
Pre-migration audit: five things to confirm before you touch the new phone
A compliant migration is less about the new device and more about the old account. If you control the account and its recovery path, the device change is routine. If you do not, no amount of preparation on the new phone will help. The five checks below take a few minutes and prevent the majority of reported "I lost everything" outcomes; they are ordered so that each one removes a different class of failure.
1. Control of the phone number
Your account is anchored to a phone number, and login codes are delivered to that number or to an already-signed-in Telegram session. Moving a physical SIM card into the new phone is the simplest path and preserves everything. If the number itself is changing, use the in-app number change flow rather than creating a fresh account, because a new registration starts with an empty cloud history. A related risk worth naming: if you lose the SIM and the carrier eventually reassigns that number, whoever receives it may be able to register a Telegram account on it. That is a general carrier-recycling reality, not a Telegram-specific flaw, and it is a reason to change the number inside the app rather than abandoning it.
2. Two-step verification and the recovery email
If you enabled two-step verification, the cloud password is required during sign-in, and this is the single most common hard stop during device migration. Open Settings → Privacy and Security on the old device, confirm that two-step verification is on, and verify that the recovery email on file is one you can actually reach. If the password is unknown and the recovery email is unavailable, Telegram's reset flow can require a waiting period before the reset completes, with the exact wording and duration shown in the app itself rather than in any article. Treat that waiting period as the worst-case migration timeline and plan around it.
3. Active sessions inventory
Settings → Devices (labelled "Active Sessions" in some clients and versions) lists every device currently signed into the account, along with platform and last-active time. Before migration, this list is your audit log: it tells you whether an old tablet, a borrowed laptop, or a device you no longer own still holds a valid session. After migration, revisit the same screen and terminate anything you do not recognize. This is the cheapest access review available and it directly supports the auditability goal of a device transition.
4. The account inactivity timer
Telegram's privacy settings include an option to delete the account automatically after a chosen period of inactivity. That setting is a retention boundary disguised as a security preference. If your migration is part of a longer handover, or if the account is used rarely, check the configured interval and decide deliberately whether it still matches the risk profile. For a personal account that you sign into regularly, the timer rarely fires; for a device that is being retired and an account that may sit untouched for months, it is the difference between a dormant account and a deleted one.
5. Local-only asset inventory
Finally, list everything that exists only on the old device: Secret Chat media, files you downloaded into the phone's gallery or file manager, screenshots, Telegram Desktop export archives kept on a laptop, and any local passcode-protected data. Nothing on that list will follow you through cloud sync, and none of it can be reconstructed after the old device is wiped. Copy it out first, then proceed — this is the last step of the audit precisely because it is the only one whose cost rises sharply once the device is gone.
Operation paths by platform
The operational steps are short, but the shortest reachable path differs slightly between mobile and desktop, and the failure branches are where people get stuck. Paths below describe the current clients as of 2026; menu labels can shift between versions, so treat the wording as a guide and look for the equivalent entry if your build names it differently.
Android and iOS: signing in on the new device
Install Telegram, open it, and choose the sign-in option that asks for your existing number rather than starting a new account. Enter the number in international format and confirm the code. The shortest mobile path is: Install Telegram → "Log in with phone number" → enter number → enter the code → enter your two-step verification password (if enabled). The code normally arrives as an SMS, and if you still have a signed-in session somewhere, Telegram may also deliver it inside that session as a service message, which is faster and more reliable when roaming. After authentication, the chat list rebuilds from the cloud. On iOS you may be asked whether to allow notifications and contacts access at first launch; both are optional for history recovery and can be decided on privacy grounds independently.
Desktop: same account, different constraints
Telegram Desktop signs in through the same phone-number flow, and because it has a real keyboard and screen, it is the better place to verify that history is complete before you commit to wiping a phone. The desktop client is also where the export tool lives, which becomes important later. What desktop cannot do is substitute for the phone in every respect: Secret Chats are not available there, so a desktop migration alone will never surface them. If your goal is auditability rather than convenience, sign in on desktop first, confirm the archive, and only then retire the phone.
Changing the phone number instead of the device
If you are moving to a new number as well as a new handset, use the in-app change flow on the account you already have. On mobile the typical path is Settings → tap your phone number (or the edit control beside it) → Change Number, then enter the old number, the new number, and the code sent to the new number. Because this keeps the same account, cloud history, contacts relationships, and chat memberships stay attached. Creating a second account on the new number instead is the single most common way people "lose" history, because the new account genuinely has none. If the Change Number entry is not present in your particular client, the account may need to be updated from a mobile client rather than desktop.
Running two accounts without logging out
Where the concern is continuity rather than replacement, adding a second account is safer than transferring. Telegram supports multiple accounts in one client, switchable from the account menu. This lets you keep the old number signed in while the new one is configured and verified, and it removes the temptation to wipe the old device before you have confirmed that the new one behaves as expected. For anyone with compliance obligations, this overlap period is the equivalent of a parallel run in a system migration: the old system stays live until the new one is proven.
Failure branches and fallbacks
Three failures account for most support traffic. No login code arrives: verify the number format, check for a code already delivered inside another Telegram session, wait for the SMS retry timer, and try the voice-call option if the client offers it; roaming and carrier filtering are frequent causes. The two-step password is unknown: use the recovery email reset, and be prepared for the waiting period Telegram displays if the email is also inaccessible. The old number is gone and no session is available: this is the hard case, and the only reliable answer is to act before it happens by changing the number inside the app while you still control it. In each branch, the fallback is the same: keep the old device online and untouched until the new one demonstrably works.
What transfers automatically and what does not
The table below summarizes the practical split. The pattern to notice is that everything server-side follows the account, and everything device-side does not.
| Item | Follows the account? | Notes |
|---|---|---|
| Chat and channel message text | Yes | Rebuilt from the cloud on sign-in. |
| Media in cloud chats | Yes | Often fetched on demand rather than preloaded. |
| Chat folders, pinned and archived chats, drafts | Yes | Stored server-side alongside the account. |
| Scheduled messages | Yes | Delivered by the server when due. |
| Secret Chats and their media | No | Device-bound; gone after logout or uninstall. |
| Downloaded copies in gallery or file manager | No | Outside Telegram's storage entirely. |
| Local passcode and app-level lock | No | Reconfigure on each device. |
| Auto-download and cache preferences | No | Per-device; worth re-checking on metered connections. |
Two entries in that table are worth a second look because they surprise people. Scheduled messages are frequently assumed to be local reminders; in fact the scheduling is handled so that the message is sent even if the device is offline, which is why it survives migration. Conversely, draft text inside a Secret Chat is as device-bound as the chat itself. A quick empirical check after migration is to compare a handful of older chats for message count and date range on both devices: if the new device shows the same range, cloud sync is complete.
Media, cache, and the "my files disappeared" scenario
Most migration complaints are not about messages but about media. The mechanism is worth understanding because it determines whether a missing photo is a real loss or a display artifact. In cloud chats, Telegram downloads media to the device according to auto-download rules and keeps it in cache for a configured period. When the cache expires, the file is removed from local storage but remains on the server, and tapping the item re-downloads it. On a fresh device, the cache starts empty, so historic media appears as placeholders until you interact with it. That is expected behaviour, not data loss.
Where real loss occurs is in the two non-cloud lanes. Secret Chat media never had a server copy, so it cannot re-download and will not appear on the new device under any circumstances. Downloaded files that you moved into your phone's gallery behave like any other file on the device: they survive only if you back them up or copy them across. The shortest path to review and control this is Settings → Data and Storage → Storage Usage for cache size and per-chat breakdown, and Settings → Data and Storage → Automatic media download for the rules that decide what gets cached in the first place. Both screens are per-device, and both are commonly wiped by a factory reset, so they contribute nothing to retention planning.
Working hypothesis, reproducible: clearing cache before migration should not change message counts on any device, because it only removes local copies. Verification: clear cache on device A, then compare a specific chat's message range and total on device A and device B. Expected observation: message counts match; previously viewed media briefly shows a download placeholder on device A only.
Exporting history for audit and recordkeeping
Cloud sync gives you continuity, but it does not give you a portable, inspectable record. For compliance-oriented use cases, that distinction matters: an auditor wants a dataset the organization holds, with a stable format and a known acquisition time, rather than a live client that may change. Telegram Desktop includes an export function for this purpose, reachable through the desktop client's settings under the advanced or data section, with the option to output machine-readable JSON in addition to a browsable HTML archive. The export includes cloud chats and their media, subject to the filters you choose.
Reproducible export procedure
- Open Telegram Desktop and sign in with the account you intend to archive.
- Go to Settings, then the advanced or data-related section, and choose the export option (wording varies by version).
- Select content types and, importantly, set a size cap for media if you are archiving to limited storage. Selecting everything on a years-old account can produce an archive far larger than expected.
- Choose JSON if the archive will be processed by a script or imported into a review platform; choose HTML if it needs to be read by a person.
- Pick a destination folder outside any temporary or sync-managed directory, then start the export and let it run to completion without closing the client.
- Record the export date and the client version in your own notes, since neither is guaranteed to be embedded in a machine-readable way.
Two limitations belong in any honest description of this workflow. First, Secret Chats are outside the export entirely, consistent with their design. Second, an export is a point-in-time snapshot: messages received after it are not included, so a recurring export cadence is needed if the archive is meant to be complete. For a compact verification step, open the JSON output and check that the message count for one specific busy chat matches what the client displays; discrepancies usually indicate that a filter excluded a media type or that the export was interrupted.
Third-party archives and the principle of least privilege
Some organizations extend retention beyond the client by adding a bot to the chats it administers, so that new messages are forwarded to an archive as they arrive. This is a reasonable pattern for groups and channels the organization controls, and it follows the principle of least privilege if the bot's permissions are limited to what archiving requires and its token is stored securely. What this pattern cannot do is retroactively read a personal account's private history: a bot sees the conversations it participates in, not the account behind them. Any tool that claims otherwise is operating outside the standard platform model, and adopting it raises both security and terms-of-service questions that should be resolved with the vendor's current published terms before deployment rather than after.
Warning: Exported archives contain the full content of conversations, including personal data about third parties. Store them with the same access controls as any other regulated record set, and delete snapshots that are no longer needed. A migration is a convenient moment to review who can reach existing archives, since their location is often documented nowhere.
Security and session hygiene after the switch
Migration is a privileged moment in an account's lifecycle: you have just proved you can authenticate from a new device, which means anyone else who can do so also can. The immediate follow-up is an access review rather than a victory lap. Open Settings → Devices, confirm that the newly added device is the only unrecognized entry, and terminate anything else. If the change was precipitated by losing the old phone, terminating other sessions is not optional; it is the control that closes the exposure created by an unknown party potentially holding the device.
Two further controls are worth re-establishing explicitly, because they are per-device by design. A local passcode or biometric lock protects the app on the new handset if someone has the unlocked phone. Two-step verification protects the account itself across every device, and since it is the control most likely to have been weakened during a rushed reset, it deserves a fresh password and a recovery email you can genuinely access. Finally, revisit privacy settings that govern who can find you and who can see your number; if the migration involved changing the number, these settings determine whether your contacts pick up the new one automatically or whether it stays hidden.
Troubleshooting: symptom, likely cause, verification, resolution
The structure below maps the failures most commonly reported during a device transition. Each entry is written so that you can verify the cause yourself rather than acting on a guess.
Chat list is empty after sign-in
Likely cause: a new account was registered instead of signing into the existing one, or the sign-in used a different number than the account being migrated. Verification: open Settings and check the phone number shown for the account; compare it with the number you intended to migrate. Resolution: log out, sign in again using the correct number, and treat a fresh empty history on a correctly entered number as a signal to stop rather than to continue typing.
Login code never arrives
Likely cause: carrier-level SMS filtering, an incorrectly formatted international number, or a code already delivered to another signed-in session. Verification: check any still-signed-in Telegram client for a service message containing the code; confirm the number's country code. Resolution: request the code again after the retry timer, and use the voice-call option where the client offers it. Keep the old device online during this period so the in-session delivery path stays available.
Sign-in blocked by two-step verification
Likely cause: the cloud password is required and unknown. Verification: the client states that a password is required rather than a code. Resolution: use the recovery email reset. If the email is also inaccessible, Telegram displays a waiting period before the reset completes; plan capacity for that window instead of repeatedly retrying, and use the interval to review which sessions remain active.
Media shows as placeholders after migration
Likely cause: an empty cache on the new device plus on-demand fetching. Verification: tap one placeholder and confirm it downloads and renders. Resolution: no action is required for cloud chats; if the media is from a Secret Chat, there is no recovery path and the item was never in the cloud.
An old device still appears in the session list
Likely cause: a session that was never terminated, sometimes on a device you no longer physically have. Verification: the entry shows a platform and last-active time that you cannot account for. Resolution: terminate that session, and if several unrecognized sessions exist, terminate all others and re-authenticate only the devices you actually use.
Scenario mapping: which path fits which situation
Abstract guidance becomes usable when attached to a situation. The three profiles below are illustrative rather than drawn from any specific organization, and each one shows how the same feature set produces a different set of priorities.
Administrator of a large channel moving between handsets
Consider an administrator running a channel with a six-figure subscriber count and a steady posting rhythm. Their migration risk is not the message archive, which is entirely server-side and reappears automatically, but the operational continuity of posting and moderation. The practical sequence is to sign in on the new device, confirm the channel appears with its full message history and admin rights intact, verify that scheduled posts are still listed, and only then retire the old phone. A useful extra step is exporting the channel's administrative chat on desktop beforehand, so there is an offline record of moderation decisions if the handset is lost mid-transition.
Individual consolidating two phones into one
For a personal user combining a work handset and a personal handset, the cleanest approach is to add the second account into the client rather than attempt any form of merging. Accounts cannot be merged; they are separate identities with separate cloud histories, and treating them as one is a frequent source of confusion. Adding both accounts keeps each history intact and switchable, at the cost of remembering that notifications, caches, and local locks are configured per account and per device.
Small team with retention obligations
For a team that must be able to produce records on request, the migration is a chance to test the retention process rather than just the devices. Sign in on desktop, run a dated export of the relevant chats, store it under the same controls as other business records, and confirm that new messages continue to be captured by whatever archiving pattern the team uses. If the team relies on a bot in a controlled group, verify after the migration that the bot is still present and still receiving messages, since a device change should not affect it but a membership change will.
Applicable and non-applicable scenarios
Being explicit about where cloud migration does not solve the problem is more useful than a list of things it does. The two lists below are meant to be read as a pair: the first describes the conditions under which the standard procedure is sufficient, and the second describes the conditions under which it is not.
Where this approach fits well
- You still control the phone number and can receive codes on it or in an existing session.
- Your important conversations are ordinary cloud chats, groups, or channels.
- You have a reasonable network and can wait for media to fetch on demand.
- You are willing to keep the old device powered on until the new one is verified.
Taken together, these conditions describe the ordinary case: a personal or small-team account whose valuable content lives in cloud chats, migrated by someone who still has the credentials. In that setting, the whole procedure is a sign-in plus a verification pass, and the only real risk is impatience — wiping the old device before the new one has been checked.
Where it does not fit, and why
- Secret Chat history is in scope for retention. There is no server copy and no export path; the only mitigation is not to use Secret Chats for records you must keep.
- The phone number is already lost or reassigned. Recovery depends on an existing signed-in session or on the reset flows Telegram presents; a migration plan cannot be improvised after the fact.
- You need a single merged history from two accounts. Accounts are separate; there is no supported merge.
- You need message-level legal hold with timestamps and chain of custody. A client-side export is a snapshot, not a managed archive; this requirement belongs to a dedicated compliance system.
- The old device must be wiped immediately. Wiping first removes the easiest recovery path if anything goes wrong on the new device.
Read the second list as a set of requirements rather than as warnings: each item identifies something cloud migration structurally cannot deliver, which means the answer is a different tool or a different decision made earlier, not merely a different order of steps. The migration itself is usually the easy part; deciding in advance which category your data falls into is what determines the outcome.
Best-practice checklist and decision rules
The following rules compress the article into decisions you can apply in order. Each one exists because skipping it produces a failure mode described earlier.
Rule 1 — Verify the account before you verify the device. Confirm you can receive a login code and that you know the two-step verification password. Device preparation is worthless if authentication fails.
Rule 2 — Prefer number change over new registration. If the number is changing, use the in-app change flow so the cloud history stays attached to the same account.
Rule 3 — Overlap, do not swap. Keep the old device signed in until the new one shows the expected message ranges. Parallel running costs nothing and eliminates the irreversible step.
Rule 4 — Extract local-only assets first. Secret Chat media, gallery downloads, and desktop export archives are outside the cloud and must be copied manually before any reset.
Rule 5 — Produce a dated export if anyone will ever ask you to prove something. A snapshot with a known acquisition date is auditable; a live client is not.
Rule 6 — Do the access review on both sides of the migration. Inventory sessions before you start and terminate the unrecognized ones after you finish.
Rule 7 — Re-check per-device settings. Local passcode, auto-download rules, cache limits, and notification preferences do not travel; reconfigure them deliberately rather than discovering the defaults later.
Version differences and what to re-verify over time
Client interfaces change, and settings move between menus. The features described here are long-standing parts of the platform, but their exact labels and locations are not contractual. The parts most likely to shift are the naming of the sessions screen, the placement of the export tool within desktop settings, and the wording of the two-step verification reset flow. Rather than memorizing paths, memorize the concepts: account-based cloud storage, device-bound Secret Chats, per-device caching, and an export that produces a snapshot. Any client, current or future, will express those four ideas somewhere reachable from settings.
For policy-level questions about where data is processed and for how long, consult Telegram's own published privacy documentation at the time you need it. Those documents govern, and they are updated independently of any article, including this one.
Future Trends / Version Expectations
It is reasonable to expect the surface described here to keep shifting while the underlying model stays put. Based on empirical observation of client releases so far, settings tend to be regrouped and relabelled rather than removed, and new storage or privacy controls are usually added alongside the existing ones rather than replacing them. What has not changed is the split itself: cloud chats follow the account, Secret Chats stay on the device, and caches are rebuilt locally.
Practical implication: any procedure in this article that depends on a menu path should be treated as perishable, and any procedure that depends on the account-versus-device distinction should be treated as durable. When a future client moves something, re-derive the path from the concept rather than searching for the old label, and re-verify the two items most likely to be affected — where the sessions list is shown and where the desktop export lives. If a release ever appears to change which content follows the account, that would be a genuine architectural change, and the documentation published at that time is the appropriate source rather than any secondary summary.
Frequently Asked Questions
Do I need a backup file to move Telegram chats to a new phone?
No, for ordinary cloud chats. History is stored server-side against your account, so signing in on the new device rebuilds it. A local backup file matters only for content that has no server copy, such as Secret Chat media or files you downloaded into your phone's gallery.
Will my Secret Chats appear on the new phone?
No. Secret Chats are bound to the device where they were created, and there is no server-side copy to restore. Logging out or uninstalling the app on the original device removes them permanently, and they are also outside the desktop client's export tool.
Can I merge two Telegram accounts into one history?
There is no supported merge. Accounts are separate identities with separate cloud histories. The practical alternative is to add both accounts to the same client and switch between them, which keeps each history intact without combining them.
Why does media show as a placeholder on my new device?
The new device starts with an empty cache, so media in cloud chats is fetched on demand when you tap or scroll to it. This is normal and does not indicate data loss. Media from Secret Chats is the exception, because there is nothing in the cloud to fetch.
What should I do if I do not remember my two-step verification password?
Use the recovery email reset option offered during sign-in. If the recovery email is also inaccessible, the client displays a waiting period before the reset can complete; the exact duration is shown in the app. Plan around that window rather than retrying repeatedly.
Summary and next steps
Transferring Telegram to a new phone without losing history is, structurally, a matter of keeping the account intact and understanding which layer holds which data. Cloud chats, groups, and channels are reconstructible on any device because the server is the system of record. Secret Chats, gallery downloads, and per-device settings are not, because they never existed anywhere but the old handset. Migration therefore reduces to a short sequence: confirm your number and two-step verification, sign in and wait for the cloud to populate, extract anything device-bound, verify message ranges on both devices, then retire the old one and terminate the sessions you no longer recognize.
If auditability is part of the requirement, add one more step and treat it as the real deliverable: produce a dated export from the desktop client, store it under the same controls as other records, and note when it was taken. Do that before the old phone is wiped, not after. And if any part of your workflow depends on Secret Chats for content you may one day need to produce, the migration is the right moment to move that content into ordinary cloud chats, where retention behaves predictably and a snapshot is actually possible.