How to move to a new Android phone without losing data

Moving to a new Android phone can look straightforward at first, but real world transfers are often more complicated than the setup screens suggest. Apps, messages, SIM settings, news feeds, backups, and encrypted chat history may all behave differently during the move.

This guide explains a practical migration process based on real experience moving from older Android phones to new Samsung phones. It covers what to prepare first, why a direct USB C cable transfer is often the better option, why SMS messages may not transfer properly at first, how WhatsApp backup and restore can affect recent messages, how to change Samsung News to Google Discover, and what to check before converting a physical SIM into an eSIM.

Most migration issues do not mean data has been lost permanently. In many cases, the problem is that one part of the data was not exposed correctly to the transfer tool, or that a safer restore method needs to be used after setup.

Some of the options described in this guide reflect practical choices and personal preferences made during a real phone migration. That does not mean there is anything wrong with Google Messages, Samsung Messages, Google Drive, Dropbox, Samsung News, or Google Discover. In many cases, these services work perfectly well.

The purpose of this guide is to explain what happened in one real migration, why certain choices were made, and what lessons may help others avoid confusion or data loss. Where one option was chosen over another, that should usually be understood as a matter of compatibility, convenience, security preference, or user preference in that particular situation rather than a universal rule.

Before starting a phone migration, it helps to think in terms of separate data types rather than assuming everything will behave the same way. Photos, apps, call history, SMS messages, WhatsApp data, and SIM related services may each use different transfer methods or different backup systems.

A calm preparation stage often saves a great deal of time later. The safest approach is to confirm where each important type of data actually lives before beginning the move.

Before starting, it is sensible to fully charge both phones, confirm that the new phone supports the features you plan to use, check that important apps such as WhatsApp have a current backup, review whether SMS messages are visible in the phone’s current default messaging app, use a direct USB C cable if both phones support it, and allow enough time for the process. In the migration experience captured here, each phone transfer took close to six hours, which appeared to be related to the amount of data stored on the source device.

Storage can have a direct effect on how smoothly a migration works and how long it takes. If the old phone is heavily used and the new phone has limited free space, it becomes easier for transfers, restores, and app setup stages to take much longer or behave unpredictably.

Before starting, it is worth checking how much storage is already used on the old phone and how much free storage is available on the new phone. This helps set realistic expectations and can also explain why one device migration takes much longer than another.

On many Android phones, storage can usually be checked under Settings → Storage, or on some Samsung phones under Settings → Device care → Storage, which can help the user compare used space on the old phone with available space on the new one before starting the move.

It is also sensible to check how much data is being used by large apps such as WhatsApp, photo libraries, video folders, and offline downloads. That kind of review can help the user understand whether a six hour transfer is unusual or simply the result of moving a large amount of personal data.

Wireless transfer can be convenient, but for large migrations it introduces more variables. Signal stability, background interruptions, battery drain, and transfer speed can all become problems when a great deal of data is being copied.

A direct USB C cable connection is often the more dependable option because the phones maintain a direct link throughout the transfer. In this case, cable transfer was used for two separate phone migrations and appeared both faster and more reliable than relying on wireless transfer alone.

Power planning also matters. During a long transfer, one phone may charge the other through the cable. In this case, one device was kept on a wireless charger while still connected by cable to help maintain battery levels throughout the migration. That practical detail helped avoid interruption during a process that lasted many hours.

This is one of the more confusing parts of an Android phone migration. A transfer tool may be told to copy all data and apps, yet text messages still fail to appear on the new phone afterwards.

In this case, the old phone was using Google Messages for SMS. During the initial Smart Switch migration, the transfer was set to move all data and apps to the new Samsung phone, but the SMS messages did not come across properly. That did not mean Smart Switch had been set up wrongly in a simple sense. It meant that, in practice, the messages were not transferred successfully in that first migration even though the overall move was configured broadly.

There is nothing wrong with Google Messages as an app. In this case, the issue was that Smart Switch did not successfully move the SMS history during the first transfer while Google Messages was the active messaging app on the old phone.

The working solution was practical rather than theoretical. On the old phone, Samsung Messages was installed, made the default messaging app, and the existing SMS history was allowed to appear there. After that, Smart Switch was run again and used specifically to transfer the text messages. Once the messages were visible through Samsung Messages on the source phone, the transfer worked.

A direct transfer and a cloud backup do not serve exactly the same purpose. A direct transfer is often the fastest way to move working data from one device to another. A backup is a second layer of protection in case a restore is needed later.

After the SMS issue was resolved, Google backup was enabled on the new phone so that apps, settings, data, and SMS messages would also be backed up going forward. That is sensible because it reduces dependency on a single transfer event.

However, it is also important to understand the difference between a cloud platform holding synced or backed up data and having an independent backup strategy. Storing important information in Google is useful, but Google itself should still be considered part of a wider resilience plan rather than the only copy. For a broader explanation of that principle, see our cloud storage vs backup guide.

The same thinking applies to apps that maintain their own backup system. One transfer method may fail or skip part of the data, while a backup stored elsewhere can still provide a recovery route. This is an example of layered protection rather than relying on one process to do everything perfectly.

One common source of confusion is that a backup may exist, but the user may not be signed into the correct Google account when trying to restore it on the new phone. That can make it look as though the backup has disappeared when the real issue is simply account mismatch.

Before moving phones, it is worth confirming which Google account is linked to the WhatsApp backup, when the last backup completed, and whether encrypted backup is enabled. This check can prevent wasted time later when WhatsApp is opened on the new phone and asks whether to restore from backup.

Before starting the move, it is worth confirming on the old phone which Google account is linked to the WhatsApp backup, and then signing into that same Google account on the new phone before opening WhatsApp and attempting the restore.

If the backup is important, it is also sensible to confirm that the backup has completed properly before beginning the move rather than assuming that it is current.

WhatsApp is a good example of why a phone migration is not just one task. Even when the rest of the phone moves successfully, chat history may still depend on WhatsApp’s own transfer and backup process.

In one of the phone moves, WhatsApp reported that its data would not be transferred in the normal migration. The WhatsApp account on the old phone was already backing up to Google Drive, but the backup did not yet have two step verification enabled and the backup data was not encrypted. The backup size was also large, at around 22 GB.

There is nothing inherently wrong with using Google Drive for this purpose. The more important point is that the account, backup method, and security settings should be understood before the migration begins.

To protect that data more properly before completing the move, two steps were taken on the old phone. First, two step verification was enabled for WhatsApp. Second, encrypted backup was enabled. A fresh full backup was then completed. Only after that was the phone migration continued without trying to move the WhatsApp data as part of the main device transfer.

Once WhatsApp was opened on the new phone, it offered two routes. It suggested either transferring data directly from the old phone or restoring from backup. The direct transfer was not ideal in this case because there was a wish to preserve a few recent messages from the last hours, so the safer choice was to restore from the newly completed encrypted backup instead.

Because WhatsApp often contains sensitive personal or business conversations, backup settings should not be treated as a minor detail. Enabling two step verification and encrypted backup before a migration can significantly improve protection. For a broader explanation of WhatsApp related risks and good practice, see our WhatsApp security guide.

A migration can expose weaknesses that were already present before the new phone was even switched on. In this case, the WhatsApp backup existed, but it had not yet been hardened with two step verification and encrypted backup.

That does not mean the previous arrangement was unusual. It does show why migration is a good time to improve security. A backup that contains a large personal or business message history should be treated carefully. Enabling stronger protection before the move reduces the chance that a rushed restore process relies on a less protected copy of important data.

Not every migration issue is about data loss. Sometimes the new phone works properly, but the familiar user experience is different from the old device.

A simple example is the left hand screen on many Samsung phones. After moving to the new device, that panel may show Samsung News when the user actually wants Google Discover. This is not a fault, but it can still be part of the post migration adjustment process.

This is largely a preference setting rather than a fault. Some users prefer Samsung News, while others prefer Google Discover because it feels more familiar.

On a Samsung phone, this can usually be changed by pressing and holding an empty area on the Home screen, swiping to the left hand panel, and switching the feed from Samsung News to Google Discover.

Moving from a physical SIM to an eSIM can make the new phone setup cleaner, but it needs planning. The most important point is that converting the service to eSIM will normally disconnect the physical SIM from the network.

That means the new phone must genuinely support eSIM and the activation process must be ready to complete. In the migration described here, the old phones had physical SIM cards, which were converted into eSIMs and then activated on the new phones by scanning QR codes.

The practical warning is simple. Once the number is moved across, the old physical SIM will no longer continue working in the usual way. If the new phone cannot use eSIM properly, mobile network access will be disrupted and a visit to the mobile service provider may then be required to correct it.

People often assume something is wrong because phone migration takes longer than expected. In reality, large data moves can be slow even when everything is working correctly.

Normal behaviour during a full migration can include hours of transfer time where large amounts of data are involved, repeated app optimisation or verification stages after the first copy completes, temporary gaps where some apps or messages appear later than others, battery drain even when the phones are connected, and one category of data needing separate attention after the main migration.

A long process does not automatically mean failure. What matters more is whether the phones are still progressing, whether the essential data categories are appearing, and whether any missing data has an alternative recovery route such as a backup restore.

Some situations should not be handled casually because they affect access to important services or raise the risk of data loss.

Additional help may be needed when SMS messages are missing on the new phone and are no longer visible on the old phone, WhatsApp backup cannot be completed or restored, eSIM activation fails and the physical SIM has already been disconnected, the new phone does not support the same mobile features expected from the old one, or a business user depends on recent messages, authentication codes, or app based history for work.

When asking for support, it helps to provide the phone models involved, the messaging app in use on the old phone, whether the transfer was done by cable or wirelessly, whether WhatsApp was restored from backup or direct transfer, and whether the mobile number has already been converted from physical SIM to eSIM.

A good migration usually starts well before the new phone is unboxed. The best protection is not one single tool, but several sensible preparations working together.

Before the next move, it is worth keeping Google backup enabled for the phone, reviewing whether app specific backups such as WhatsApp are current and properly protected, using encrypted backup where the app supports it, confirming which app is currently the default for SMS and whether the messages are visible there, preferring a direct cable transfer for large migrations, beginning with fully charged phones and planning for a long transfer window, checking eSIM compatibility before moving a live mobile number, and reviewing post migration settings such as the home screen news feed, default apps, and authentication prompts.

This is not a permanent checklist. Android, Samsung, Google, WhatsApp, and mobile network providers all change their behaviour over time. The safer approach is to review the current process before each migration rather than assuming the same steps will always work in the same way.

This guide forms part of a broader layered security approach. For structured guidance on security and resilience planning, see our Security and Resilience page.

For information about practical implementation and ongoing support, you can review our IT services and local IT support coverage across London, Hertfordshire, and Essex.

Return to all guides

Author
Elías Sánchez
IT Support Consultant
Evening Computing
London, United Kingdom

This guide was prepared by Elías Sánchez with research and drafting assistance from AI tools. All technical content has been reviewed and adapted for clarity and accuracy.

Last reviewed
15 March 2026