Travel eSIM Transfer Index: Can You Move It to a New Phone or Reinstall It?
Four of the ten travel eSIM providers in this fixed sample publish a self-service way to move an installed profile to another phone: eSim Travel, Saily, Ubigi, and Roamless. Five publish self-service reinstallation on the same phone. Those groups are not identical because reinstalling and transferring are different provider decisions.
Every documented self-service phone change in the sample starts with removing the profile from the old device. That makes access to the old phone important. Ubigi and Roamless also publish a support route when the old device is lost or unavailable. The checked eSim Travel and Saily pages do not state what happens in that case.
Roaming eSIM is classified as support first, not as a transfer winner. Its public support page tells travelers to keep the profile installed because some packages cannot be installed again unless support confirms a replacement. Roaming eSIM also publishes 24/7 help and keeps one-tap, QR, and manual installation details in My eSIMs. That is a useful prevention and support advantage, but it is not evidence that every package can move.
Download the provider-policy CSV or open the complete JSON dataset. The first-party policies were checked on August 7, 2026.
Which transfer rule applies to your phone change?
| What happened | What to check before acting |
|---|---|
| You are upgrading and still have the old phone | Look for a provider-specific transfer flow. Do not rely only on the iPhone or Android transfer button. |
| You deleted the profile from the same phone | Check whether the provider permits another download on that exact device and whether the original QR still works. |
| The phone was lost, stolen, or broken | Look for a documented support replacement. A flow that begins with deleting the old profile is no longer self-service. |
| You plan to factory-reset the phone | Confirm whether the reset will preserve eSIMs and whether this profile can be issued again if it does not. |
| You are switching between iPhone and Android | Use the provider's instructions. Device-to-device tools can be limited by platform, manufacturer, and issuer support. |
| You are already abroad | Make sure the new phone has WiFi and that account access does not depend on a code sent to the unavailable phone. |
| The eSIM is not connecting | Work through settings first. Deletion is not a normal connection refresh and may remove the only usable profile. |
The main finding: only 4 of 10 sampled providers publish self-service new-phone transfer steps. Five allow self-service reinstall on the same phone, four make eligibility conditional or support-led, and one says no.
The safest default: turn the line off instead of deleting it until the exact provider and plan policy has been checked.
Explore the ten-provider CSV
Check the published rule before you remove a profile
Switch between same-phone reinstall and new-phone transfer. Every row links to the first-party policy used for classification.
Loading the provider-policy CSV...
What the ten-provider transfer audit found
- Four providers publish self-service phone changes. The documented paths belong to eSim Travel, Saily, Ubigi, and Roamless.
- All four start with the old device. Their instructions require the existing profile to be removed before another installation begins.
- Five providers publish self-service same-phone reinstall. eSim Travel, Holafly, Saily, Ubigi, and Roamless provide a customer-operated path.
- Holafly proves why the columns must stay separate. It permits up to four total installations on the exact same phone but says the profile cannot move to another phone.
- Airalo and Nomad are conditional for same-phone recovery. Their public wording allows for plan or supplier differences but does not create a general reinstall right.
- MobiMatter is provider-dependent. It sells plans from several underlying issuers, so transfer and reinstall rules vary with the selected product.
- GigSky publishes a firm no-transfer result. A new phone needs a new plan and profile, and unused data remains with the old one.
- Roamless gives the clearest balance statement. It says credits, active plans, and rewards remain in the account during its documented move.
- A phone feature is not a provider policy. Apple and Google both make carrier support a condition of their eSIM transfer instructions.
- Roaming eSIM takes the preventive route. It tells travelers not to delete while troubleshooting and to ask support before relying on a replacement.
Reinstall, transfer, replacement, and reset are four different events
The word “transfer” hides several technical and commercial decisions. A useful answer starts by naming the event.
Same-phone reinstall
The eSIM profile has been removed, but the traveler is using the same handset. A provider may let the phone download the same profile again, generate a new profile, or reject the request because the original installation credential was single-use.
Holafly, for example, permits up to four total installations on the first phone. That allowance does not follow the traveler to a second device.
Planned move to another phone
The old phone still works and the traveler wants the remaining plan on a new handset. The four self-service providers in this audit begin by deleting the profile from the old device. The next step happens in the provider's app or account, not by copying the eSIM file.
This order matters. Two active copies would create a security and billing problem, so providers normally require the old profile to become unusable before the replacement can connect.
Replacement after loss or breakage
The old phone cannot complete a deletion step. The provider may need to disable the old profile and issue another one. Ubigi and Roamless document that support route. Nomad describes a case-by-case new eSIM or a refund of unused data in Nomad Points. GigSky directs the traveler to buy a new plan.
Silence is not approval. When the checked source does not state an outcome for a lost phone, the dataset records that gap instead of assuming a replacement will be free or available.
Factory reset
A reset can preserve or erase eSIM profiles depending on the option chosen during the reset and the device software. Even when the traveler intends to keep the profile, the study treats recovery as a provider question. A backup of photos and apps is not proof that an eSIM installation credential can be reused.
A profile, a data plan, and a QR code are related but not interchangeable. The profile sits on the phone, the plan holds the service entitlement, and the QR or app link authorizes a download. Providers decide whether another download is allowed.
Which providers let you move or reinstall a travel eSIM?
| Provider | Same phone | New phone | Does its self-service move require the old phone? |
|---|---|---|---|
| Roaming eSIM | Support first | Support first | Not stated |
| Airalo | Conditional | No | Not applicable |
| 🏆 eSim Travel | Self-service | Self-service | Yes |
| Holafly | Self-service | No | Not applicable |
| 🏆 Saily | Self-service | Self-service | Yes |
| Nomad | Conditional | No | Not applicable |
| 🏆 Ubigi | Self-service | Self-service | Yes |
| 🏆 Roamless | Self-service | Self-service | Yes |
| MobiMatter | Provider-dependent | Provider-dependent | Provider-dependent |
| GigSky | No | No | Not applicable |
“Self-service” means the first-party source gives the customer a documented path without asking support to approve or perform it. It does not guarantee success on every phone. “Conditional” means only some profiles qualify. “Support first” means the public policy does not promise a reusable profile. “Provider-dependent” preserves the marketplace operator's different rules instead of forcing a single answer.
Roaming eSIM: support first, with clear preventive guidance
The Roaming eSIM support hub tells travelers to keep the profile installed during troubleshooting. It states that some profiles cannot be installed again unless support confirms a replacement is available. My eSIMs provides one-tap, QR, and manual installation details, but the public page does not promise that an already-used credential will work again.
That evidence produces a support first classification for both columns. It would be inaccurate to label Roaming eSIM transferable merely because installation details are visible.
✅ Roaming eSIM's evidence-backed safety edge: the public troubleshooting flow puts the do-not-delete instruction before the connection checks, then provides 24/7 and WhatsApp support for order-specific help. This can prevent a recoverable settings problem from becoming a deleted-profile problem.
Airalo: some same-phone recovery, no new-phone transfer
Airalo's reinstall help page says reinstall is typically unavailable. Its app may offer a reinstall or replacement after checking a deleted eSIM, depending on the specific plan. If no option appears, the traveler needs support or another purchase.
Its new-device help page states that an installed profile cannot move to another phone. The audit therefore records conditional same-phone reinstall and no new-phone transfer.
🏆 eSim Travel: an app-generated installation link for another phone
The eSim Travel Google Play listing says QR codes can be reinstalled. In a public App Store developer response, the company tells a user to remove the profile from the previous device, open Settings in the app, choose “Get link for install eSIM,” and continue on the new phone.
That is a documented self-service path. The checked sources do not state the lost-device outcome or make a separate promise about the remaining balance, so those fields stay unscored.
Holafly: four installations on the first phone, no transfer
Holafly's reinstall policy permits up to four total installations on the exact same phone. The original QR or manual activation details can be used for that recovery.
Its transfer page says a Holafly profile cannot move to a different device. Same-phone flexibility therefore earns a self-service reinstall result but not a transfer result.
🏆 Saily: delete, open the app, and share the new QR
Saily publishes separate iOS transfer steps and Android transfer steps. The flow removes the current profile, opens Install eSIM in the Saily app, chooses Share eSIM to other person, and scans the displayed QR on the other device.
The old phone is part of that documented sequence. The checked transfer page links to support but does not promise an outcome if the original device is already unavailable.
Nomad: generally single-use, with narrow exceptions and a loss remedy
Nomad's QR reuse explainer says its travel eSIMs cannot move between devices. Its broader use-case guide notes that some supplier-issued profiles can occasionally be reinstalled, including a limited another-device exception for one supplier category.
The general classification remains no transfer and conditional reinstall. For a lost phone, Nomad's loss policy describes a case-by-case new eSIM or an unused-data refund in Nomad Points.
🏆 Ubigi: account-based reinstall, with a five-use cap
Ubigi's iPhone and iPad guide tells the traveler to delete the old profile, sign into Ubigi on the new device, and use Install your eSIM. The reinstall limit is five after deletion.
Ubigi also says to contact customer service when the first phone is lost, broken, or otherwise unavailable. Its repair guidance says the original QR may reinstall the profile on the returned phone, with provider support available if that fails.
🏆 Roamless: self-service transfer with the clearest balance promise
The Roamless transfer policy tells users not to use the generic iOS transfer control. Instead, they should delete the old profile, sign into the Roamless app on the new phone, then choose Data and Install eSIM.
Roamless explicitly says credits, active data plans, and rewards remain available through this process. It also documents a support-issued new profile when the old device cannot be accessed. That combination makes its transfer outcome the most fully described in the sample.
MobiMatter: the exact marketplace product decides
MobiMatter's transfer policy divides its marketplace plans into direct transfer, replacement-required, and single-device groups. The correct answer comes from the product description or troubleshooting wizard.
Its delete and rescan policy gives the safe general answer: do not delete without guidance. Some issuers permit a limited reinstall, while others permanently invalidate the profile.
GigSky: a new device needs a new plan
GigSky's new-phone policy says its profiles are single-device and cannot be transferred, copied, or reused. A traveler should buy a new plan on the new phone and select New eSIM Device at checkout.
The page also says unused data remains tied to the old profile and that GigSky cannot manually re-provision it. Its Android setup guide warns users not to delete without contacting support.
Why the provider rule matters more than the transfer button
Apple's iPhone eSIM setup guide includes Quick Transfer, carrier activation, QR, app, link, and manual methods. It says Quick Transfer works when the carrier supports it. Google's Pixel transfer guide makes the same distinction and directs users to the carrier when automatic transfer is unavailable.
Travel eSIM providers often use an app-managed replacement flow instead of the operating system's nearby-phone transfer. Roamless explicitly tells customers not to use the iOS transfer option. Saily generates a QR through its app. Ubigi asks the customer to delete the old profile and reinstall from the account.
The practical rule is simple: the visible phone menu shows a technical route that may be available. The provider decides whether this profile and plan are eligible to use it.
Moving between iPhone and Android adds another dependency
Apple and Google now document some cross-platform transfer support, but both make issuer participation part of the process. A travel eSIM that cannot be transferred under the provider policy does not become portable because both phones expose a transfer menu.
For the four self-service providers in this sample, use the provider's own instructions. If the documentation only covers one operating system, ask whether the same account flow works on the intended destination phone before deleting the old profile.
WiFi and account recovery are part of the move
The new device normally needs an internet connection to download a profile. A hotel, airport, or trusted personal hotspot can supply it. Account access also matters. If a login code goes only to the lost phone, the provider may need to verify the customer another way before issuing anything.
Keep the order number, account email, device model, and screenshots of any error available. Do not publish or send an eSIM QR code in a public forum.
What should you do before changing phones?
- Open the exact provider policy. A general article about eSIM transfer cannot override the product's issuer rule.
- Check whether the trip plan is still active. An expired profile may have a different reinstall or top-up path from a live plan.
- Keep the old phone working. Charge it, connect both devices to WiFi, and do not reset it first.
- Confirm the new phone is compatible and unlocked. Our eSIM compatibility guide explains the device checks.
- Save order and account details. Keep the order number, account email, and provider instructions available on another device.
- Use the provider's sequence. Some require old-profile deletion before the install button appears. Others say not to delete at all.
- Test mobile data on the new phone. Confirm the line, data roaming, APN, and supported network before resetting the old handset.
- Keep the old phone until the new profile works. A completed data copy does not prove the mobile plan moved.
If the eSIM is only failing to connect, use our eSIM not working abroad checklist before considering deletion. The data roaming guide covers the setting that many travel plans require. For a future trip on the same installed profile, the travel eSIM top-up index explains which sampled providers publish top-up paths without another installation.
What if the phone is lost, stolen, or broken abroad?
The self-service count drops when the old phone is unavailable because every documented transfer winner in this sample starts by removing its old profile. Treat the recovery as a support case unless the provider publishes a separate lost-device flow.
- Ubigi: contact customer service when the old profile cannot be deleted.
- Roamless: support can assign a new profile when the previous device is unavailable.
- Nomad: a new eSIM or unused-data refund in points may be available case by case.
- GigSky: buy a separate plan for the new device; the existing profile is not re-provisioned.
- Roaming eSIM: contact 24/7 support with the order details; the public policy does not promise the same result for every package.
- Airalo, eSim Travel, Holafly, Saily, and MobiMatter: follow the exact plan or support path because the checked pages do not establish one universal lost-device outcome.
A new travel data plan can restore internet access, but it does not recover the home mobile number used for calls, SMS, or bank verification. Keep recovery codes for important accounts somewhere other than the phone. A travel eSIM is usually a data product, not a replacement for the identity attached to the regular SIM.
How Roaming eSIM helps beyond a transfer news story
A news story can report that phones support eSIM transfer or that one provider introduced a new flow. It cannot check the current package, preserve the order details, or stop a traveler from deleting a profile during a failed connection attempt.
Roaming eSIM has a practical edge at that point. A traveler can keep the regular SIM in the phone, arrange a country or regional data plan before the trip, open the order in My eSIMs, and access one-tap, QR, and manual installation details. The support hub provides a visible do-not-delete instruction, 24/7 help, and WhatsApp contact for order-specific questions.
That is not a claim that Roaming eSIM wins the transfer column. The public rule remains support first. It is a claim about a verifiable safety and support path that applies before a risky deletion. The study remains valid even when another provider offers a more flexible transfer policy or a cheaper plan.
If the plan is unusable and you are considering a claim instead of a reinstall, the Travel eSIM Refund Index compares unused, installed, incompatible-device, technical-failure, and partial-use policy outcomes across ten providers.
Roaming eSIM's useful edge is prevention plus help: keep the installed profile, check the order, and contact support before a reset or phone change. That is more actionable than learning after deletion that a QR was single-use.
The ten transfer questions travelers ask most often
Public Reddit threads show that travelers do not ask only “Can I transfer it?” They ask about the device condition, timing, platform, data balance, and QR code. We normalized ten recurring questions from public threads without treating votes as survey results.
- Can I move an installed travel eSIM to a new phone? The provider and exact profile decide.
- Can I delete and reinstall the same profile on the same phone? Five providers in this sample publish a self-service path, but the limits differ.
- Will a factory reset erase the profile? It can, depending on the reset choice. Recovery still depends on the provider.
- What happens if the phone is lost, stolen, or broken? The usual old-device deletion step is unavailable, so a separate support or replacement route is needed.
- Can I transfer while already abroad? Possibly, but the new phone needs WiFi and the account must be recoverable without the old device.
- Does the old phone need to work and stay nearby? All four documented self-service paths in this audit require access to the old profile first.
- Does the iPhone or Android transfer button guarantee success? No. Apple and Google both make carrier or issuer support a condition.
- Can I move between iPhone and Android? Only when the provider and both device platforms support the required flow.
- Will remaining data and validity survive? Roamless states that they do in its flow. Other providers give different or less complete statements.
- Should I turn the eSIM off instead of deleting it after the trip? Yes, when the plan may be reused or topped up and the provider has not told you to remove it.
The direct threads are retained in the JSON dataset with the competitive review and normalized provider rows.
What the leading search results explain, and what was missing
We reviewed ten prominent pages across searches for transferring a travel eSIM, reinstalling a deleted profile, reusing a QR code, moving to a new iPhone or Android phone, and recovering after a reset.
| Page reviewed | What it does well | Gap this study addresses |
|---|---|---|
| Nomad QR reuse guide | Explains single-use credentials and Nomad's own transfer rule | One provider, without a fixed comparison dataset |
| Apple iPhone eSIM setup | Documents several activation and transfer methods | Device controls, not travel provider eligibility |
| NexaEsim transfer guide | Covers iPhone, Android, one-time codes, and support | Centers one provider and general scenarios |
| eSIMCircle reuse guide | Separates QR reuse, top-ups, profiles, and transfer | No reproducible named-provider audit |
| eSIM.net replacement QR guide | Gives product-specific replacement eligibility, fees, and timing | One marketplace, without alternative-provider comparison |
| Google Pixel transfer guide | Documents setup and settings-based transfer | Makes carrier support a condition but does not audit travel providers |
| Orange Travel QR policy | Gives a concise one-device rule | One provider only |
| TravelKon reinstall guide | Detailed deleted-profile troubleshooting on both platforms | No current fixed-provider policy matrix |
| Yoho Mobile QR reuse guide | Clearly explains its one-time QR and deactivate-first advice | Does not show how other provider rules differ |
| Gigs deleted-eSIM guide | Explains issuing a new profile while retaining a subscription | Platform capability, not a consumer travel eSIM comparison |
The content gap is not a lack of setup instructions. Apple, Google, and several providers explain their own workflows well. The missing piece is a current comparison that applies the same definitions to multiple travel eSIM providers and keeps same-phone reinstall, new-phone transfer, factory reset, and unavailable-device recovery separate.
How we audited travel eSIM transfer policies
Why these ten providers were compared
The sample contains Roaming eSIM plus the first nine other apps returned by Apple's United States Search API for the exact query “travel esim” when the original research sample was set. The same fixed group is used in our privacy, top-up, and network-disclosure studies. Reusing it prevents us from selecting providers after seeing which ones produce an appealing result.
The sample is not a market-share ranking and does not claim to include every travel eSIM seller. It creates a stable set for comparing published policies over time.
Source hierarchy
Provider classifications rely on public first-party help centers, websites, app-store listings, and developer responses. Apple and Google sources explain device controls but do not decide provider outcomes. Reddit threads informed the traveler-question set only. They did not determine a policy classification.
When a provider's public wording varied by plan or supplier, the study recorded “conditional” or “provider-dependent.” When a source did not state what happens after loss, we wrote “not stated” rather than assuming either recovery or failure.
How each transfer outcome was classified
- Self-service: a published customer-operated path without support approval or intervention.
- Conditional: only some profiles, plans, or suppliers qualify.
- Support first: no blanket promise is published, and the traveler is directed to support before deletion.
- Provider-dependent: a marketplace answer changes with the underlying issuer.
- No: the provider explicitly says the installed profile cannot move or reinstall in that scenario.
The “old phone” field asks whether the provider's documented self-service transfer begins with access to and deletion of the existing profile. It does not mean support can never recover an account after loss.
Reproduce the published files
The normalized source file is scripts/research/data/travel-esim-transfer-index-source.json. The generator is scripts/research/generate-travel-esim-transfer-index.mjs. From the project root, run npm run research:transfer-index.
The command validates the ten-provider sample, classification values, first-party HTTPS sources, ten competitive pages, and ten demand questions. It then rebuilds the CSV, JSON, checksums, and three WebP charts. Each provider row carries a SHA-256 checksum over the normalized policy evidence used for that row.
Limits of the study
- We audited public policy wording; we did not buy and move ten live profiles.
- Transfer eligibility can change by plan, underlying issuer, phone model, operating system, account state, and country.
- A successful reinstall does not prove the same public IP route, local carrier, speed, or priority on the new device.
- A support path is not a promise of a free replacement or a particular response time unless the provider states it.
- App-store developer responses are first-party statements but are less durable than a dedicated help-center policy.
- A fixed ten-provider sample supports comparison, not a claim about every travel eSIM provider.
- Public Reddit threads are qualitative demand signals, not a representative poll.
What should travelers remember?
Do not ask only whether an eSIM is “transferable.” Ask whether the exact plan supports same-phone reinstall, a planned new-phone move, and recovery when the old phone is gone. Those are different outcomes.
In this sample, four providers publish a self-service phone-change path and five publish self-service same-phone reinstall. Every self-service transfer winner requires access to the old profile first. A generic iPhone or Android transfer control cannot override the issuer's rule.
For Roaming eSIM, the public answer is to keep the profile installed and contact support before deleting or resetting. That conservative classification follows the evidence and gives the traveler the safest practical next step.
