What "Telegram Chat Transfer" Actually Means on a New Phone
Telegram chat transfer on a new phone sounds like a contradiction once you understand the architecture: there is very little to transfer. Telegram is built cloud-first, meaning your message history, chat list, folders, drafts, and most account-level preferences live on Telegram's servers and are addressed to your account rather than to a specific handset. Sign in with the same phone number on a new device, complete the verification step, and the conversation list generally reappears on its own — often without the old phone being powered on at all.
That is why the migration experience feels so different from messengers that keep history in a local database and rely on a backup file. In those apps, losing the old device without a backup means losing the history. In Telegram, the history was never really on the device in the first place; the device holds a working copy, not the master record. The same reasoning explains why one account can stay open on several devices at once without drifting out of sync: each client renders the same server-side state and refreshes it as needed. Understanding this single fact resolves most of the confusion that surrounds migration questions, including the persistent one about why photos appear blurred immediately after switching and only download when tapped.
What genuinely remains device-bound is a short list, and it is worth memorising because it defines the boundary of any transfer: Secret Chats (end-to-end encrypted conversations that are deliberately not stored on Telegram's servers and are tied to the specific device pair that created them), the app passcode or biometric lock, the local media cache, and a handful of per-device behaviours such as notification handling and automatic download rules. Everything else — including pinned chats, chat folders, archived chats, scheduled messages, and read state — follows the account. The practical test is straightforward: if a piece of content or a setting has no server-side counterpart, it is device-bound and will not move with you.
Three similarly named things that are not this
Before going further, it helps to separate the term from three neighbours it is often confused with. First, there is group or channel ownership transfer, which is a permissions action inside a group's member list and has nothing to do with devices. Second, there is importing chats from another messenger, where Telegram reads a local export produced by a different app — a one-way, lossy process. Third, there is exporting your Telegram data into an archive on desktop, which produces a snapshot file rather than moving the live account. The rest of this article focuses on the device-to-device case, and refers to the other two only where they intersect with it.
Tip: Because Telegram ships updates frequently and locates menu entries slightly differently between platforms and builds, every path in this article is written as a shortest reachable route rather than as a fixed map. If a label differs in your client, the surrounding screen is almost always the same one.
Cloud Restore vs. Local Transfer vs. Archive: A Working Comparison
There are effectively four routes people take when moving to a new phone, and they are not alternatives so much as layers. Most users only ever need the first. The second is an optional accelerator that appears in some clients. The third is a desktop-only fallback for archiving. The fourth handles data coming from a different messenger entirely. Keeping them separate in your head is what prevents most migration-day mistakes, because each route answers a different question.
| Route | What moves | Character of the operation | Key limit |
|---|---|---|---|
| Cloud re-login | Chats, folders, drafts, pins, read state | Automatic, incremental, no old device required | Media downloads on demand; Secret Chats absent |
| Local-network handover | Cached chat data copied device to device | Optional prompt during setup; both devices needed | Not offered on every platform or build |
| Desktop export archive | Messages and media as files in a folder | Manual, read-only snapshot | Not restorable into another account |
| Cross-app import | History from another messenger | One-way, time-limited, lossy | Platform-restricted |
The practical consequence of this table is that the question "how do I transfer my chats" usually has a boring answer: install the app, sign in, wait. The interesting questions are the exceptions — what happens to a 40 GB media cache, what happens to a Secret Chat with a colleague, and what happens when the initial sync on a slow connection appears to stall. Those are the cases the remaining sections address, and each of them maps onto exactly one of the four routes above.
Before You Start: Prerequisites and What Will Not Follow You
A successful switch is mostly about preparation on the old device, done while you still have it. The single most important item is the second factor: if you enabled Two-Step Verification (an additional password required at sign-in), you will need that password on the new phone. Telegram does not email it to you, and the recovery email you set up is the only supported fallback if you forget it. Accounts that have lost both the password and the recovery email have historically taken a long time to recover, which is a strong argument for confirming the recovery email is current before you begin.
Second, check Settings → Devices on the old phone. This screen lists active sessions and is where you can confirm that the new login has actually registered, and where you can terminate sessions you no longer want. Doing a review here before the switch also tells you whether anything unexpected — an old tablet, a web session on a shared computer — still has access. If you are selling or handing on the old device afterwards, ending those sessions is part of the migration, not an afterthought.
Warning: Secret Chats cannot be transferred, backed up, or restored. Closing a Secret Chat, or wiping the device that holds it, ends it permanently. If a conversation matters, move anything you need to keep into Saved Messages or a normal chat before switching hardware. This is a designed property of end-to-end encrypted device-bound chats, not a bug in the transfer process.
Third, decide how much local cache you actually want to carry forward. On Android and iOS the app keeps downloaded media on disk up to a configured limit, and that cache is not part of your account. Deleting the app on the old phone removes it, and leaving the app installed keeps it. Neither choice affects what the cloud holds, but the new device will start its own cache from empty unless a local handover copies it. For most people this decision is trivial: the cache rebuilds itself on demand, so the only real consideration is how much storage you are willing to commit on the new handset.
The Default Path: Signing In and Letting the Cloud Do the Work
The standard route is short enough to describe in a sentence: install Telegram from your platform's app store, enter the phone number associated with the account, receive the login code, and — if prompted — enter your Two-Step Verification password. On a good connection the chat list populates in seconds and message history fills in as you open conversations. There is no export step, no pairing step, and no need to keep the old phone nearby.
Two details are worth knowing because they cause most of the early confusion. First, chat lists sync fast while message bodies and media sync lazily: the client requests history as you scroll, which is why opening a three-year-old conversation on a new phone briefly shows a loading state. Second, drafts, pins, folder assignments, and read markers are account-level and therefore arrive already in place, which can be mildly disorienting the first time — a message you started typing on your laptop yesterday is waiting in the same conversation on the new handset.
Android shortest path
On Android, install the app, launch it, choose Start Messaging, enter the number in international format, and confirm the code. The code typically arrives inside Telegram itself on any other still-signed-in device, with SMS as a fallback. If Two-Step Verification is active, the password prompt follows. Afterwards, the two screens that matter for migration are Settings → Devices (session control) and Settings → Data and Storage (where automatic download rules and cache limits live). On recent Android builds, the related chat preferences sit under Settings → Chats, though the label may render as Chat Settings or Chats and Media depending on the installed build, so read the surrounding options rather than the exact wording.
iOS shortest path
On iOS the flow is the same but the entry points differ: launch Telegram, tap through the introduction, enter the number, and confirm the code, which again usually arrives as a Telegram service message on another signed-in device. Cache control lives under Settings → Data and Storage, where you will find the storage/cache screen and the automatic download rules; the passcode and Face ID lock live under Settings → Privacy and Security. iOS does not offer the desktop-style data export described later, which is a genuine platform difference rather than a hidden setting.
Desktop and web shortest path
On desktop, you have two options. The first is the phone-number sign-in, identical in principle to mobile. The second is QR linking: the desktop client displays a QR code, and on the phone you open Settings → Devices → Link Desktop Device and scan it. QR linking is convenient because it skips code entry, but it still creates a normal session that appears in the Devices list and can be revoked from there. Telegram Web behaves like desktop in this respect and, by design, is not the right place to keep your only copy of anything.
The Local-Network Handover Option — and How to Tell Whether You Have It
Some Telegram clients have offered an additional shortcut: rather than re-downloading cached chat data from the cloud, the new device pulls it directly from the old one over the local network. Prompts and labels along the lines of transferring or moving chats have appeared in Android builds during initial setup, and the option depends on both devices being on the same Wi-Fi network at the same time. Because naming and availability vary between platforms, app versions, and regions, treat this as an optional accelerator rather than a step you can count on.
The honest way to discover whether your client offers it is empirical: complete a fresh install and sign-in on the new device and watch the first-run screens. If a transfer prompt appears, it will normally name the source device and ask for confirmation on both ends. If no prompt appears, the client has simply skipped the option and the ordinary cloud restore is already running — nothing is broken, and no data is at risk. A reproducible check: after sign-in, open Settings → Devices on the old phone and confirm the new session is listed there; then compare the visible chat count on both devices after a couple of minutes. A near-identical list on both ends indicates the cloud restore has completed its first pass.
When the option is available, the benefit is bandwidth, not completeness. A user with a large media cache and a metered mobile plan may prefer the local handover because it avoids re-downloading gigabytes over cellular. But it is not a substitute for the account-level sync, and it does not bring Secret Chats across, because those exist only on the device that created them. Treat the local handover as a cache-copy convenience layered on top of a cloud account, never as the reason the chats appear.
Media, Cache, and Why Nothing Looks Missing on Day One
The most common post-switch complaint is that photos and videos look like low-resolution placeholders. This is expected behaviour rather than data loss: the client renders the small preview immediately and fetches the full file when you tap it, subject to your automatic download rules and your storage limit. A conversation can look complete while most of its media is still sitting in the cloud, waiting to be requested. In other words, the new device is not missing your data; it simply has not asked for it yet.
Two settings shape this experience. The first is the automatic download rules under Settings → Data and Storage, which decide whether photos, videos, files, and voice messages download automatically over mobile data, Wi-Fi, or both. The second is the cache size and retention policy on the same screen, which caps how much Telegram may keep on disk and for how long. A sensible migration-day configuration is to allow automatic downloads over Wi-Fi only, keep the cache limit modest, and let the on-demand behaviour handle the rest — this keeps the new device responsive without emptying a data plan.
To see the current footprint, open the storage or cache screen inside Data and Storage. It breaks local usage down by category, typically photos, videos, files, music, and other, and offers a clear-cache action per category. This screen is a useful diagnostic: if a user reports that a new phone "used 30 GB overnight", the answer usually sits here, and the fix is a cache limit rather than a reinstall. Note that clearing cache does not delete anything from the account — the files come back on demand, which is precisely the property that makes aggressive cache clearing safe.
Tip: If your plan is limited, set automatic downloads to Wi-Fi only before the first big scroll through an old group. Empirical observation across devices: most accidental data usage after a phone switch comes from automatic downloads triggered by unbounded scrolling, not from the initial sync itself, which is comparatively light.
When You Want a Physical Copy: The Desktop Export Route
Sometimes the goal is not to move an account but to keep an offline copy — for compliance, for a departing team member's handover, or simply because you want a readable archive that does not depend on any account staying active. Telegram Desktop offers this through its data export: the entry sits under Settings → Advanced → Export Telegram data. The dialogue lets you choose which chat types to include and whether to export media, and it produces an HTML and JSON folder you can browse offline.
This is a snapshot, not a migration. The archive cannot be imported back into Telegram to reconstitute an account, and it will not include the contents of Secret Chats, because the server-side export never had access to them. Media is exported as ordinary files, so the folder grows quickly: a user with several years of active group participation and no size filter may find the output running to tens of gigabytes, which is worth planning disk space for before starting.
A concrete scenario helps here. Imagine an operator who runs a customer-facing channel and wants a local record of a two-year campaign before rotating to a new number. Exporting from desktop gives them a searchable archive they can hand to a colleague, while the live account keeps running on the cloud. Doing this in addition to the normal sign-in — rather than instead of it — covers both needs: continuity on the account and durability on disk. There is no supported path in which the export replaces the account.
Bringing History In From Another Messenger
The opposite direction — pulling history from a different app into Telegram — is a genuinely different workflow, historically available on Android and typically found in the chat-related sections of Settings rather than in data storage. The mechanism is straightforward in concept: Telegram reads a local export file or the other app's local database, then writes those messages into your own Telegram chats on that device, timestamped as they originally were.
The boundaries are strict and worth stating plainly. The import is one-way and lossy: attachments may not survive intact, group membership is not recreated, and the result lives in your own account rather than recreating the other person's identity. It is also a per-device operation tied to the importing platform, so an import completed on one handset does not propagate to another the way ordinary chats do. If your actual goal is device migration, this section does not apply; if your goal is consolidating two messengers onto one app, it does.
Device-Bound Items: Secret Chats, Passcodes, and Bots
Three categories of item behave differently enough to deserve their own treatment. Secret Chats are, by design, not stored in the cloud and not available on other devices; a new phone will show no trace of them, and there is no supported export. Local app locks — the passcode on mobile, the equivalent on desktop — are per-installation and must be set up again; they are not part of your account and are not restored by any transfer mechanism. Bot conversations are a subtler case: the message history with a bot is ordinary cloud chat and does appear on a new device, but the bot's own state, such as a session identifier or a wizard mid-flow, is stored on the bot's server and cannot be migrated by you. After a switch, the practical remedy for a stuck bot flow is to send the bot's start command again, which on most bots resets the conversation.
A fourth item, easy to overlook, is chat ownership. If you are the owner of a group or channel, nothing changes about that on a new phone — ownership is an account attribute, not a device attribute. What can be involved is the deliberate transfer of ownership to another person, which is a members-list action inside the group and should not be conflated with switching hardware. Performing an ownership transfer as part of a phone change is a common and avoidable mistake.
A Decision Tree for Choosing Your Route
The following sequence resolves nearly every real migration case in a few questions. Read it top to bottom and stop at the first branch that matches.
- Are you keeping the same phone number? If yes, proceed to the next question. If no, use the change-number flow first — found by tapping your number area in Settings — so the account, chats, and contacts follow the new number, then continue.
- Is your only goal to keep using Telegram on new hardware? Then the default path is sufficient: install, sign in, verify. Nothing else is required.
- Are you on a metered connection with a very large local cache and both devices available on one Wi-Fi network? Then check whether your client offers a local handover during setup and use it as an accelerator.
- Do you need a durable offline copy for compliance or handover? Add a desktop export on top of the normal sign-in.
- Are you consolidating history from a different messenger? That is the import workflow, and it is independent of device migration.
- Do you rely on Secret Chats with a specific contact? Accept that they end, and move whatever must be preserved into a normal chat beforehand.
The reason this tree is short is that Telegram's default is unusually forgiving. Most migration advice for other platforms exists to prevent data loss; here, the default path protects against it automatically, and the branches only exist to optimise bandwidth, produce archives, or handle the deliberately non-syncing cases.
Troubleshooting: Symptom, Cause, Verification, Fix
When something does go wrong, the fastest route is to separate account-level symptoms from device-level ones. Account-level problems affect every device you sign into; device-level problems affect only the new handset and usually resolve with a settings change or a reinstall. The cases below are ordered roughly by how often they are reported.
Chats appear, but an old conversation looks empty near the top
This is almost always lazy loading rather than a gap. Verification: scroll upward in the conversation; the client should fetch older messages as you approach the boundary. If scrolling produces nothing after a reasonable wait on a working connection, sign out and back in to re-trigger the initial history request. Note that messages deleted at the account level are gone everywhere, and a chat that was cleared on another device will look cleared here too — that is synchronisation working correctly, not a failed transfer.
Media shows a placeholder that never resolves
Check the automatic download rules first; a configuration that disables downloads over the current network type will leave files waiting indefinitely until tapped. Verification: tap the item and watch whether it downloads manually. If manual download also fails, check available storage — a device near capacity can block caching. If a single file never downloads on any device while others in the same chat do, the original upload may have expired or been removed, and no setting will restore it.
The new device is not listed under Devices
Open Settings → Devices on the account and refresh the screen before concluding anything. In observed cases the list updates after a short delay and after the new client establishes its connection. If the session genuinely never appears, the sign-in likely did not complete — check whether the code was entered on a stale screen, or whether Two-Step Verification was abandoned midway.
A Secret Chat is missing and cannot be found
This is expected and irreversible. There is no recovery path, no hidden menu, and no support workflow that restores it. Verification is trivial: check the old device, where the chat will still exist if the app has not been removed. Resolution is procedural — recreate the Secret Chat from the new device with the same contact if both parties agree, and move any important material into Saved Messages in advance next time.
Login is refused or loops back to the number screen
The most common cause is a forgotten Two-Step Verification password, in which case the recovery email set on the account is the supported route. A second cause is too many code requests in a short window, which can trigger a temporary cool-down; waiting and retrying is the appropriate response rather than repeatedly requesting codes.
Verification and Observation Methods You Can Repeat
Because Telegram's behaviour is easy to confuse with data loss, it helps to have a small checklist you can run after any migration and compare against expectations. The following checks are qualitative by design — exact timings depend on connection, device, and account size — but they produce a clear yes-or-no signal.
- Chat-list parity: compare the visible chat list on old and new devices after a few minutes. They should be effectively identical, including folder assignments and archived items.
- Draft propagation: type a partial message on one device without sending it, then check the same conversation on the other. If the draft appears, account-level synchronisation is working.
- Read-state propagation: open an unread chat on the new phone and confirm the badge clears on the old one.
- Session visibility: confirm the new device is listed under Devices on the old phone, and revoke any session you no longer recognise.
- Cache accounting: check the storage breakdown before and after a day of browsing to see how much the new device is retaining, then adjust the cache limit accordingly.
Run these five checks once, and you will know more about your own migration than any general guide can tell you, because the decisive variables — your connection, your cache settings, and your account size — are local to you.
Applicable and Non-Applicable Scenarios
The default cloud path is a good fit for individual users, small teams, and most channel operators, because it requires no preparation beyond remembering the second-factor password. It is also a good fit for people replacing a lost or broken device, since it never requires the old hardware to be present.
It is a poorer fit in a few specific situations. Teams with regulatory obligations that require a locally retained, auditable record should add a desktop export, because account continuity is not evidence. Users who depend on Secret Chats for sensitive conversations should plan the transition explicitly, since the mechanism does not survive hardware changes by design. And anyone expecting a byte-for-byte clone of the old device — identical cache contents, identical local settings, identical notification behaviour — will be disappointed, because that is not what account-level synchronisation promises.
Best-Practice Checklist for Switch Day
A short, ordered routine avoids almost every problem described above. Confirm the Two-Step Verification password and recovery email are known and current. Review active sessions and end anything stale. Move any content from Secret Chats into Saved Messages if it must survive. Set automatic media downloads to Wi-Fi only on the new device before the first long scroll. Sign in on the new device, complete verification, and give the chat list a few minutes to settle before judging it. Then run the five verification checks, and finally remove the app from the old device once you are satisfied — or keep it, and simply end its session from the Devices screen.
Security and Privacy Boundaries Worth Restating
Three points deserve emphasis because they are frequently misunderstood. First, cloud storage is not the same as public storage: chat contents are protected in transit and at rest on Telegram's infrastructure, but they are available to any authorised session on your account — which is exactly why session hygiene under Devices matters more than any transfer setting. Second, the phrase "my chats are backed up" is misleading in this context; there is no user-managed backup file for a Telegram account, only server-side storage and an optional desktop export for your own records. Third, the strongest security property in the app, end-to-end encryption in Secret Chats, is inseparable from the fact that those chats do not migrate. The convenience and the guarantee come from the same design decision, and no configuration changes it.
Frequently Asked Questions
Do I need to keep my old phone switched on to get my chats on a new one?
No. Chat history is stored on Telegram's servers against your account, so signing in with the same phone number brings the chat list back without the old device being present. The only exception is the optional local-network handover that some clients offer during setup, which by definition requires both devices on the same network at the same time. If that option is not available to you, the ordinary cloud restore does the whole job.
Why do photos and videos look blurred until I tap them after switching phones?
Because the new device starts with an empty local cache. Telegram shows a small preview immediately and downloads the full file on demand, subject to the automatic download rules and cache limit you set under Data and Storage. Nothing is missing; the media is retrieved from the cloud when requested. Setting automatic downloads to Wi-Fi only is the usual way to avoid unexpected data usage while the cache refills.
Are Secret Chats moved to the new phone?
No, and there is no supported way to make them move. Secret Chats are end-to-end encrypted and bound to the devices that created them, so they are absent from the cloud and therefore absent on a new handset. If the content matters, copy or forward it into Saved Messages or a normal chat before you switch hardware, because once the originating device is gone the conversation cannot be recovered.
Can I restore the desktop export archive into another Telegram account?
No. Export Telegram data, found under Settings → Advanced on Telegram Desktop, produces a read-only snapshot in HTML and JSON along with media files. It is designed for offline reading and handover, not for re-import into an account, and it will not contain Secret Chat contents because the server never held them. Treat it as an archive that complements your account rather than a replacement for it.
What happens if I change my phone number as well as my phone?
Change the number inside the app first, using the entry in Settings that opens when you tap your phone number, so the account and its chats follow the new number. Contacts will see the new number once they have your details refreshed, and your history is unaffected because it belongs to the account rather than to the number. Signing in on new hardware afterwards is then just the ordinary login process.
The Short Version
Telegram chat transfer on a new phone is mostly a matter of signing in and letting the account catch up. The chat list, folders, pins, drafts, and read state come from the cloud within moments of a successful login; media arrives on demand as you open conversations; and the only things that genuinely fail to follow are the ones designed not to, namely Secret Chats, the local passcode, and the cached files themselves. Optional extras exist for specific needs — a local-network handover when your client offers it, a desktop export when you need a durable offline copy, and a one-way import when the history lives in a different messenger.
The action worth taking today, before any hardware change, is preparation on the old device: verify that you know your Two-Step Verification password and that the recovery email is current, review the session list, and move anything irreplaceable out of Secret Chats. That five-minute routine eliminates the majority of migration failures people actually report. Everything after it is a login.
