Yes, in many cases, but the process depends on the phone, operating system, carrier and eSIM provider rather than being one universal step. Compatible iPhones and Pixel phones support built-in eSIM transfer under specific conditions, but a prepaid travel eSIM often has to go through its own provider’s app or support process instead.
Can an eSIM be transferred to a new phone?
Yes, often, but there is no single answer that covers every combination of device, carrier and provider. Google currently supports SIM and eSIM transfer to compatible Pixel phones, during setup or afterwards through the SIM settings menu. For automatic transfer specifically, Google lists Android 12 or later, an up-to-date version of Google Play Services and a configured screen lock among the requirements.
Apple similarly supports eSIM Quick Transfer between compatible iPhones for participating carriers.
Neither of those built-in features guarantees that a prepaid travel eSIM will move the same way. That is the part travelers usually get wrong.
Why travel eSIMs behave differently from a normal plan
A standard mobile subscription is typically tied to a carrier account and a phone number. A travel eSIM is often a prepaid profile instead, governed by the rules of the app that sold it.
That provider decides whether the profile can be reinstalled, moved to a new device, or has to be replaced outright. Device-level transfer support is not enough on its own if the provider’s backend does not allow it.
Key takeaways
- Built-in phone transfer features (Apple, Google) do not automatically cover prepaid travel eSIMs.
- The travel eSIM provider, not the phone maker, usually decides whether a profile can move to a new device.
- Saily currently allows its eSIM to be reinstalled on another device using the same account email.
- Do not delete the old profile until the new device confirms a working connection.
iPhone to iPhone transfer
For supported carriers, Apple provides eSIM Quick Transfer. On the new iPhone, the eSIM can be added and transferred from a nearby iPhone. Once the number has successfully moved, Apple states it stops working on the previous iPhone.
A prepaid travel eSIM is a different case. Saily currently allows its eSIM to be reinstalled and used on another device when the same account email is used, which is a provider-level process rather than the phone-to-phone Quick Transfer feature. Check the travel provider’s own instructions before assuming the built-in iPhone feature applies.
Android to iPhone, and other cross-platform moves
Support here is improving but is not universal. Apple states that with iOS 26, selected carriers and compatible Android devices support direct Android-to-iPhone eSIM transfer. Combinations outside that supported list still require the carrier or provider to activate the eSIM manually on the new phone.
Google likewise supports eSIM transfer on compatible Pixel devices, but directs users back to the carrier when the automatic process is not available.
| Move | What usually applies |
|---|---|
| iPhone to iPhone, participating carrier | Apple’s eSIM Quick Transfer |
| Pixel to Pixel, Android 12+ | Google’s automatic SIM/eSIM transfer |
| Android to iPhone (iOS 26) | Direct transfer, selected carriers and devices only |
| Prepaid travel eSIM, any device combo | Provider’s own app or support process, e.g. Saily reinstall via account email |
Do not delete the old eSIM first
This is the rule most worth remembering. Some travel eSIMs cannot be downloaded repeatedly using the original installation credentials, often a one-time QR code. Removing the old profile before confirming transfer support can turn a simple migration into a replacement purchase or a support ticket.
Check the provider’s transfer instructions first. Saily documents a process where its eSIM is removed from the old device and then installed on the new device through the account, which is a specific, provider-defined workflow that should not be assumed to apply to every travel eSIM.
Before you erase the old phone: confirm mobile data actually works on the new phone. A transfer that looks complete in settings does not always mean the connection is live.
Before switching phones
Check eSIM support on the new phone
Confirm the model and region variant actually supports eSIM.
Open the travel eSIM provider’s account
Look for transfer, reinstall or new-device instructions specific to that provider.
Check whether the current package is still active
An expired package changes what is worth transferring in the first place.
Keep the old phone available
Some transfers require confirmation on both devices during the process.
Test mobile data on the new phone first
Confirm the connection works before resetting or selling the old device.
If the profile itself cannot be transferred, a travel eSIM from Saily can set up a replacement mobile-data option on the new device without waiting on a carrier support call.
FAQ
01Can I transfer a travel eSIM to a new phone the same way as my regular number?
Not always. A regular carrier number is often eligible for Apple’s or Google’s built-in transfer features. A prepaid travel eSIM is usually governed by the provider’s own rules instead, so check that provider’s app or support instructions.
02What happens if I delete the eSIM before transferring it?
It can turn a simple migration into a bigger problem. Some travel eSIMs cannot be reinstalled from the original QR code once removed, so confirm transfer support before deleting anything.
03Does transferring an eSIM work between Android and iPhone?
With iOS 26, Apple supports direct Android-to-iPhone transfer for selected carriers and compatible devices. Outside that supported combination, the carrier or provider needs to activate the eSIM manually on the new phone.
04Can Saily’s eSIM move to a new device?
Saily currently allows its eSIM to be reinstalled and used on another device when the same account email is used, following the removal and reinstall steps documented in its app.
05What should I do if automatic eSIM transfer fails?
Do not repeatedly delete and reinstall profiles at random. Google recommends contacting the carrier when transfer fails persistently, and the same applies to a travel provider that controls the profile.
