Transfer eSIM to a New Phone an eSIM is not the same thing as activating a new line. In this guide, “transfer eSIM” means moving an existing eSIM carrier profile (your number and plan) from one device to another via remote provisioning. You are not re-activating a dormant line, and you are not doing a fresh virtual SIM card install on a brand-new account.
That distinction matters because the exact flow depends on two variables: your wireless carrier (your service provider) and your operating system (iOS vs. Android). A method that feels effortless on one carrier-device combo can look totally different on another.
What you’ll need ready (preflight checklist)
Most transfer failures come from simple readiness gaps. Before you start, get these out of the way:
- New phone powered on and updated to the latest OS version (check device compatibility before starting)
- Access to your carrier account credentials (login, PIN, or account number)
- Ability to receive verification codes (SMS, email, or authenticator app)
- A stable Wi-Fi network connection on both devices
- Old phone nearby if possible—not always required, but helpful
Once you begin the transfer, assume the old eSIM typically deactivates the moment the new one activates. Don’t start when you need uninterrupted service.
Requirements Before You Transfer
An eSIM transfer can be smooth and fast—without compromise—but only if the fundamentals are in place. These prerequisites are the “invisible” pieces that decide whether you’re done in five minutes or stuck in a support queue.
Device Support
Compatibility gates — confirm all three before you start:
- eSIM-capable hardware. Your new phone must have an embedded SIM (eSIM) chip, not just a physical SIM tray. Check your phone’s spec sheet or Settings if you’re unsure — a device that doesn’t list eSIM support simply cannot receive a transferred profile (for example, many older models still rely on a nano-SIM).
- Multiple eSIM profile support. Most modern eSIM phones can store several profiles but limit how many can be active simultaneously. How many profiles your phone supports varies by model and region — check your device specs before assuming you can add a line without removing one.
- OS version gate for transfer tooling. This is separate from eSIM activation support. Your operating system version determines which transfer methods are available to you, and an outdated OS can cause a transfer to fail even on fully eSIM-capable hardware. For Apple devices, eSIM Quick Transfer requires both devices on iOS 18.4+. Also worth knowing: iOS 17.4+ supports adding an eSIM by long-pressing a QR code in Apple’s default Mail or Safari app and choosing “Add eSIM,” and iOS 26 allows transferring more than one phone number to a new iPhone. Run a software update check on both phones — don’t skip this step.
Cross-platform reality check:
Phone-to-phone eSIM transfers are almost always ecosystem-specific. iPhone↔iPhone and some Android↔Android flows work through on-device transfer tooling. However, iPhone→Android or Android→iPhone is a different situation. Those cross-OS moves typically can’t use built-in transfer tools and instead require carrier re-provisioning from scratch—especially when switching between devices from different smartphone manufacturer ecosystems (for example, from an Apple iPhone to Vivo).
Decision rule: If you’re switching OS families, plan on carrier app, QR code, or manual activation — not a device-to-device transfer. Skip ahead to the Carrier Support section to confirm your carrier’s self-serve options.
Carrier Support
eSIM support and eSIM transfer support are not the same capability. Many carriers handle remote provisioning perfectly, yet still require a fresh profile issuance every time you switch devices.
Carrier capability checklist:
- Supports eSIM at all — Basic eSIM activation (remote provisioning of a new profile). Most major carriers do; many MVNOs and regional carriers still don’t.
- Supports eSIM transfer / profile move (device-to-device) vs. requiring new eSIM issuance — Some carriers let you move an existing carrier profile to a new device. Others treat every device change as a brand-new eSIM issuance (which still works, but takes longer and may require support). Know which one your carrier does—for example, policies can differ widely between Verizon and Claro.
- Supports self-serve in app/website vs. requiring a support chat or call — Self-serve is faster and available 24/7. If your carrier requires agent assistance, factor in wait times.
What to look for in your carrier’s app or website: Options like “Manage SIM,” “Replace device,” “Activate eSIM,” or “Transfer eSIM.” If none appear, your carrier likely requires support contact for a profile move (sometimes shown as a Carrier Cellular Plan change or replacement).
Timing caution — read this before you start:
Initiating a transfer can immediately deactivate the eSIM profile on your old device. That means calls, texts, and data on your current number can go dark the moment the transfer kicks off—often before the new device fully comes online. If you rely on that number for 2FA codes, start only when you can afford a brief window of disruption.
Before you begin: Have an alternate contact method ready — a secondary line, a VoIP app, or confirmed email access for any account that might send a verification code during the process.
Wi-Fi and Bluetooth
On-device transfer tools (like eSIM Quick Transfer and eSIM Carrier Activation on compatible Android devices) depend on stable connectivity. Treat these as non-negotiable.
Minimum connectivity checklist:
- Both phones connected to a stable Wi-Fi network (avoid public/captive-portal Wi‑Fi)
- Bluetooth enabled on both devices
- Both devices unlocked and physically nearby throughout the transfer
Troubleshooting-prep tip: Disable any active VPN on both phones before starting — VPNs can interrupt the remote provisioning handshake and cause activation to stall or fail silently. Similarly, avoid captive-portal Wi‑Fi (hotel, airport, coffee shop networks that require a browser login) — they frequently block the provisioning traffic carriers need.
Power and state readiness — prevent mid-transfer failures:
A half-finished transfer can leave your profile stuck and require a carrier reset. Before initiating:
- Both devices charged to a comfortable level, or plugged into power
- Airplane mode OFF on both devices
- No active OS update in progress on either device — wait for updates and reboots to finish
Account Access
“Account access” sounds simple—until the transfer asks for a PIN you haven’t used in years.
Have all of these ready before you start:
- Carrier account login credentials — username/email and password for your carrier’s app or website
- Access to the email address or phone number your carrier uses for verification — OTPs (one-time passcodes) may be sent here during the process
- Device passcode for both phones
- Apple ID credentials (iPhone) or Google Account credentials (Android) — required for certain transfer steps and device verification, and on Apple devices this may be validated through your Apple Account
Critical: Verify that you can receive OTPs without relying on the line being transferred. If your carrier sends verification to the number you’re moving and that line deactivates early, you can lock yourself out mid-flow. Use email verification if available, or keep a secondary number ready.
Pre-collect these identifiers — some carriers ask for them:
Certain carriers require your new device’s EID (the eSIM identifier) and/or IMEI before they’ll issue or transfer a profile. Have these ready ahead of time. You can find them in Settings; the exact path varies by OS and device.
Plan and Feature Support
Transferring your eSIM moves your line. It doesn’t guarantee every feature will feel instantly “as it was” on the old device.
Confirm before transfer:
- Hotspot/tethering — Verify it’s enabled on your plan, not just your old device settings
- International roaming — Confirm it’s active on the account level if you’ll need it soon
- Carrier Visual Voicemail — Note whether it’s working; it sometimes needs re-registration
- Wi‑Fi Calling — Check if it’s enabled on your account; it often requires re-activation on the new phone
Verify after transfer:
- Wi‑Fi Calling — Confirm it activates on the new device (often needs a toggle or a carrier re-registration step)
- RCS / iMessage linkage — These may need re-registration after the transfer completes
- Carrier Visual Voicemail — Test that it populates correctly
Linked devices — don’t forget companion plans:
If you use a smartwatch, tablet, or another device on a companion plan, those are separate eSIM profiles and will not automatically follow your phone’s transfer. This is especially common on devices like iPad Pro or a Surface tablet with LTE/5G. After the phone transfer, re-check linked devices inside your carrier app and reactivate as needed.
Best Ways to Transfer an eSIM (2026)

The fastest method is the one your device + carrier combination actually supports. Your decision comes down to three questions:
- Are you staying within the same OS family or switching platforms (iPhone↔Android)?
- Do you still have the old phone available?
- Does your carrier allow in-OS transfer, or do they require their own tools?
With those answers, pick the matching path below.
Phone-to-Phone Transfer
Best for: Moving an eSIM between two phones of the same ecosystem when both devices are in hand and powered on.
You need: Both phones on, unlocked, and physically nearby; an active Wi‑Fi network on both; the old phone available to approve the transfer.
Typical time: A few minutes once both devices are confirmed connected.
Failure points to watch: Transfer stalls if either phone loses connectivity mid-process; the old-phone approval step is easy to miss if you set the device aside too early.
When to use a different method: If the old phone is lost, broken, or unavailable, use Carrier Activation or Carrier App/Website Transfer.
Both phones must stay powered on and near each other. Moreover, the approval happens on the old phone, not the new one. Once activation completes on the new phone, the old eSIM stops working automatically—so don’t expect to toggle back without going through the carrier again.
iPhone-to-iPhone vs Android-to-Android:
- iPhone: Version alignment is the gatekeeper. eSIM Quick Transfer requires iOS 16 or later on both devices; the capability expanded further in iOS 18.4. In 2026, iOS 26 adds multi-number transfer capability, meaning you can move more than one eSIM line in a single flow.
- Android: Bluetooth + Wi‑Fi must both be enabled at the same time. Without both, the handshake won’t complete—even if the carrier supports eSIM.
Settings Transfer
Best for: Users who want to initiate an OS-level eSIM transfer from the new phone’s Settings without a separate app.
You need: Both phones available; old phone accessible to approve the transfer request; account credentials if the carrier requires mid-flow verification.
Typical time: Minutes, assuming both devices maintain connectivity.
Failure points to watch: The new phone must detect the old phone; if discovery/pairing fails, the flow won’t progress.
When to use a different method: If your carrier doesn’t support in-OS transfer, the option may not appear or may redirect you to the carrier app.
Settings Transfer is started from the Settings app on the new phone. However, the old phone still performs the approval step, so it must be nearby, unlocked, and reachable.
Menu labels also vary by manufacturer. On a Google Pixel, the path is typically Settings → Network & internet → SIMs → Download a SIM; on Samsung Galaxy devices running One UI, look under Settings → Connections → SIM manager → Add eSIM.
Carrier App or Website Transfer
Best for: Cross-platform moves (iPhone↔Android) and any situation where OS-level transfer isn’t offered by your carrier.
You need:
- Carrier account login credentials
- Ability to receive 2FA (SMS, email, or authenticator app)
- Access to carrier account holder information (name, account PIN/passcode, or last four of SSN depending on carrier)
Typical time: 5–15 minutes for self-serve; longer if identity verification triggers a manual review.
Failure points to watch: 2FA delivered to the old SIM number won’t reach you if that line is already deactivated.
When to use a different method: If your account is flagged for identity verification or you’ve hit a self-serve transfer limit, escalate to Carrier Activation (direct support).
This is the reliable fallback for iPhone↔Android moves. Remote provisioning happens through the carrier portal, independent of what either OS offers. Keep your verification method ready—failed 2FA is one of the most common reasons a “simple transfer” becomes a long one.
QR Code Transfer
Best for: Situations where the carrier provides a new eSIM QR code directly—common for new activations, replacements, or carrier profile re-downloads.
You need: The QR code from your carrier (email, PDF, or on-screen display); a working camera or a compatible iOS/Android tap-to-add flow.
Typical time: Under 5 minutes if the code is valid and the camera scan succeeds.
Failure points to watch: Poor lighting causes scan failures; provisioning server timeouts can make a code appear invalid even when it isn’t.
When to use a different method: If the QR code expires or is single-use and fails, request a fresh code before trying Manual Activation.
Two operational details that often surprise users:
- QR codes are consumed differently depending on OS. Android usually needs a direct scan inside the eSIM setup flow. On iOS 17.4 and later, you can tap-and-hold a QR code displayed in an email or browser and choose “Add eSIM,” so you don’t need to print it or display it on another screen.
- QR codes may be single-use and time-limited. If activation doesn’t complete the first time, the code may already be consumed. In addition to saving time, requesting a fresh code can prevent repeated failures from triggering account security flags.
Safety reminder: Treat your eSIM QR code like a password. Don’t share it, post it, or upload it where others can access it.
Manual Activation
Best for: Devices without a working camera, or when QR scanning consistently fails and the carrier supports manual entry as a fallback.
You need: Carrier-provided activation details (SM-DP+ address, activation code, confirmation code).
Typical time: 5–10 minutes for entry, plus provisioning time.
Failure points to watch: Typos. One wrong character in the SM-DP+ address or activation code is enough to fail the provisioning request.
When to use a different method: If your carrier doesn’t issue manual activation codes, use Carrier App/Website Transfer or request Carrier Activation via support.
Manual activation means entering carrier-supplied values into the eSIM setup fields—no guessing and no reusing old codes. If you repeatedly enter incorrect details, you can trigger activation loops that sometimes require a carrier-side reset.
Carrier Activation
Best for: Situations self-serve methods can’t resolve, or where the carrier must initiate provisioning on their backend.
You need: Access to carrier support (phone, chat, or store); identity verification documents or account PIN ready.
Typical time: Variable—automated flows can be fast, while human-assisted provisioning depends on queue time.
Failure points to watch: Identity verification mismatch delays the process; calling from a different number than the account’s primary contact can trigger extra verification.
When to use a different method: If this is a straightforward same-OS transfer and your old phone is available, use Phone-to-Phone Transfer or Settings Transfer first.
Carrier Activation is carrier-side provisioning initiated by support staff or automated carrier activation flows, not a self-serve portal action. It’s the right path when:
- Transfer limits have been hit and self-serve blocks further attempts
- The old phone is missing, stolen, or broken and cannot approve anything
- Identity verification is required before the carrier will release the profile
Transfer Limits & Retries
Carriers and operating systems can both cap how often an eSIM can be moved in a set time window. Some platforms allow up to 5 transfers before requiring support intervention. If you hit a wall, don’t brute-force retries—each failed attempt may count against your limit and reduce your options.
Transfer an eSIM Without the Old Phone

If your old phone is sold, traded in, broken, lost, or simply unavailable, device-to-device eSIM transfer flows usually stop immediately. Most of them require on-device approval from the old phone.
What you’re doing instead is a re-issue (also called reprovision): the carrier provisions a new profile to the new device via remote provisioning. Using that terminology with support (“replacement eSIM” / “reprovision my eSIM to my new device”) tends to get you routed faster.
Old Phone Unavailable
What you need before you start (unique to this scenario):
- Your carrier account login credentials (username + password)
- A backup verification method that works even when your old line is inactive — a backup email address, an authenticator app, or an alternate phone number enrolled in your account
- Wi-Fi network access on your new phone (required for remote provisioning before your new line is active)
Decision path — pick your branch:
(a) Old phone sold, traded in, returned, or left at home — but the line is still active:
Phone-to-phone transfer can’t be completed without approval in most flows. Log into your carrier app or portal and look for “Manage eSIM,” “Switch Device,” or “Reprovision.”
(b) Old phone is active and you can still access your carrier account:
Use the carrier app or website to reprovision. You’ll usually receive a QR code or a push-based activation link to your email. Scan the QR code on your new phone over Wi-Fi to download the new carrier profile.
(c) Old phone is active and you cannot access your carrier account:
Call carrier support. Without account access, you’ll need identity verification. Often, visiting a carrier store with a government-issued ID is the fastest path.
What happens to your old eSIM during reprovisioning:
Once the carrier activates the new eSIM profile, the old profile is deprovisioned. Some carriers do it instantly; others take a few minutes. Either way, the old device losing signal mid-process is expected.
Transfer limit note: eSIM transfers are typically capped — Google, for example, limits Pixel eSIM transfers to a set number (often up to 5 transfers per device). If you’re blocked because you’ve hit that ceiling, you cannot approve a new transfer from the old device anyway, so requesting a carrier re-issue or reprovision — or asking support for an override — is the correct path.
Old Phone Broken or Lost
When the device is compromised, security comes first. Contain the risk, then restore service.
Containment first — follow these steps in order:
- Suspend your line immediately. Log into your carrier account online (or call support) and suspend the lost or broken line.
- Secure your account credentials. Reset your carrier account password right away. Use a strong, unique password and enable two-factor authentication if it isn’t already active.
- Lock down your account with a PIN or transfer protection. If your carrier offers a port-out protection PIN, SIM-swap protection, or account security PIN, enable it.
- Request a replacement eSIM on your new phone. Use the carrier portal or support and ask for a re-issue/reprovision.
- Confirm the old profile is deactivated. Ask support to confirm the old eSIM carrier profile is fully deprovisioned.
Can’t receive SMS verification because your number is offline?
This is common after suspension. Look for alternate verification:
- Email verification
- Security questions
- In-store government ID verification
- Pre-set account PIN
If self-serve can’t proceed, ask support exactly which identity verification methods are accepted for eSIM re-issue without SMS access.
Service restoration expectations after re-issuing your eSIM:
| What may temporarily fail | What to do immediately |
| Voice calls not connecting | Toggle airplane mode off/on, then restart the new phone |
| SMS messages not arriving | Confirm the correct line is set as active for messaging in settings |
| Mobile data not working | Verify the new eSIM line is set as the default for cellular data |
| Activation appears stuck | Ensure you’re connected to a Wi-Fi network during the initial provisioning process |
Minor disruption right after activation is normal. If service doesn’t stabilize within 15 minutes, contact your wireless carrier—the carrier profile may not have fully propagated.
Device-Specific eSIM Transfer Guides

eSIM menus look deceptively similar across devices, yet the labels and prerequisites vary just enough to cause missed options. Use the tap paths below as your “no guessing” map—and if something isn’t where it should be, the troubleshooting tables tell you what that usually means.
iPhone
Tap Path (Home Screen → eSIM Active)
- Open the Settings app → tap Cellular (or Mobile Service in some regions).
- Tap Add eSIM.
- Choose Transfer from Nearby iPhone to use eSIM Quick Transfer, or choose Use QR Code / Enter Details Manually if transferring from a non-Apple device or your carrier sent an activation code.
- Follow the on-screen prompts on both iPhones; confirm the plan name appears under Cellular Plans.
- When prompted, set the new line as your default or keep it as a secondary line.
Prerequisites / What Must Be True
- eSIM Quick Transfer requires both iPhones to be running iOS 18.4+ and placed within Bluetooth range of each other.
- Both devices need access to a Wi-Fi network during the transfer handshake.
- Bluetooth must be enabled on both phones — even if you’re not pairing them manually.
- You must be signed in to the same Apple ID on the receiving iPhone, or ready to approve the transfer from the old device.
- Camera access is required if you’re scanning a QR code carrier profile instead of using Quick Transfer (make sure the Camera app is permitted if the scanner won’t open).
- iOS 17.4+ adds a handy shortcut: tap and hold a QR code in the default Mail app or Safari browser and choose “Add eSIM” — no need to navigate back to Settings first.
Multiple Lines / Dual SIM Callout
If you manage more than one line, go to Settings → Cellular → Cellular Plans and label each line clearly (“Personal,” “Work”). With iOS 26, more than one phone number can be transferred to a new iPhone in a single flow, so confirm each plan name appears correctly before you decommission anything on the old phone.
Time / Disruption Expectation
Your old iPhone will lose cellular service for the transferred line as soon as the receiving device begins remote provisioning. Expect a brief “Activating” status on the new phone.
If You Don’t See the Transfer Option
| Missing Element | Likely Cause | Next Step |
| No “Transfer from Nearby iPhone” option | Either device is below iOS 18.4 | Update both phones via Settings → General → Software Update, then retry |
| No “Add eSIM” button at all | Carrier hasn’t enabled eSIM or device is carrier-locked | Contact your carrier or use their app/website to initiate activation |
| QR code scan isn’t working | Camera permission denied or poor lighting | Enable camera access in Settings → Privacy → Camera → Settings |
| Transfer starts but stalls | Wi-Fi or Bluetooth dropped mid-flow | Re-enable both radios and restart the process from Add eSIM |
Cross-Platform Note
- If you’re moving from an Android device to iPhone, eSIM Quick Transfer won’t work — use your carrier’s app, carrier website, or the QR code path instead.
- iPhone-to-Android follows the same rule: cross-platform remote provisioning depends on the carrier portal, not OS-level handoffs.
Samsung
Tap Path (Home Screen → eSIM Active)
- Open the Settings app → tap Connections.
- Tap SIM manager → tap Add eSIM.
- Select Transfer SIM from another device.
- Follow the pairing prompts on both Samsung Galaxy devices; confirm the carrier profile loads correctly.
- Verify the plan name and number appear under SIM manager before dismissing the setup screen.
Prerequisites / What Must Be True
- Both devices should be Samsung Galaxy models with eSIM hardware (check your model’s spec sheet if unsure).
- The receiving device must have Wi-Fi connected throughout — the carrier profile download depends on it.
- Bluetooth must be active on both phones for device-to-device discovery.
- Both devices should be physically nearby during the initial pairing step.
- Check that your Samsung Galaxy is running a carrier-approved Android version; some carriers restrict eSIM transfer to specific OS builds — update via Settings → Software update if prompted.
Multiple Lines / Dual SIM Callout
Samsung Galaxy devices often support dual SIM (physical + eSIM). Before starting, go to Settings → Connections → SIM manager and confirm which line is which. During installation, verify you’re activating the intended carrier profile so your primary number doesn’t end up on the wrong slot.
Time / Disruption Expectation
The old device’s line typically goes dark as soon as Transfer SIM from another device initiates remote provisioning. The receiving Samsung Galaxy will show “Activating”, usually resolving within one to three minutes.
If You Don’t See the Transfer Option
| Missing Element | Likely Cause | Next Step |
| No “Transfer SIM from another device” under Add eSIM | Carrier doesn’t support the transfer API | Use the carrier’s app or website to generate a QR code, then scan under Add eSIM → Scan QR code |
| “Add eSIM” option missing entirely | Device may be carrier-locked or running an older One UI build | Update via Settings → Software update; if locked, contact carrier |
| Transfer fails mid-way | Bluetooth or Wi-Fi dropped | Re-enable both radios, restart SIM manager, and try again |
| Carrier profile won’t download | Network or provisioning server issue | Try on a different Wi-Fi network; call carrier if issue persists |
Cross-Platform Note
- Samsung Galaxy ↔ iPhone transfers bypass device-to-device menus. Use your carrier app, carrier website, or QR code activation.
Google Pixel
Tap Path (Home Screen → eSIM Active)
- Open the Settings app → tap Network & internet.
- Tap SIMs → tap Add SIM.
- Select Transfer SIM from another device.
- Follow the on-screen steps to pair with the source device and download the carrier profile.
- Confirm the plan name and number appear under SIMs before exiting.
Prerequisites / What Must Be True
- Both devices need a Wi-Fi network connection — Pixel downloads the carrier profile over Wi‑Fi.
- Bluetooth must be enabled on both phones for device discovery.
- The source device should be nearby and unlocked when you initiate the transfer.
- Camera access is required if you fall back to scanning a QR code for activation.
- Confirm your Pixel is running a recent Android build; eSIM transfer availability can depend on the Android version your carrier has certified.
Time / Disruption Expectation
After you select Transfer SIM from another device, the source phone’s line can enter a brief suspended state during remote provisioning. Your Pixel will show an activating status that usually clears within a minute or two.
If You Don’t See the Transfer Option
| Missing Element | Likely Cause | Next Step |
| No “Transfer SIM from another device” under Add SIM | Android version or carrier may not support it | Update via Settings → System → System update; if unavailable, use QR code or carrier app |
| No “Add SIM” option | eSIM not supported on this Pixel model or carrier locked | Verify device compatibility on the Pixel spec page; contact carrier |
| Transfer option grays out or fails | Transfer limit reached | See Limits callout below |
Limits: Google Pixel’s eSIM transfer feature supports the move usually up to 5 times for a given eSIM. If you’ve hit that ceiling, you’ll need to contact your carrier directly to re-provision the line via QR code or manual activation rather than device-to-device transfer.
Other Android Devices
Tap Path (Home Screen → eSIM Active)
Android skins vary, but the flow is usually consistent:
- Open the Settings app → look for Network & internet, Connections, or Mobile network (label depends on manufacturer skin).
- Find SIM or SIM management → tap Add eSIM or Add mobile plan.
- Choose Transfer SIM from another device if available, or select Scan QR code / Enter activation code.
- Follow the prompts to download the carrier profile.
- Confirm the new line appears and is active before restarting or removing the old SIM.
Prerequisites / What Must Be True
- A Wi-Fi network connection is required for the carrier profile download.
- Bluetooth should be active if you’re attempting a device-to-device transfer (not all Androids support this natively).
- Camera access is needed for QR code scanning — check permissions if the scanner doesn’t launch.
- Confirm eSIM hardware is present and that your carrier supports remote provisioning for your exact model.
- Some budget or regional models are eSIM-capable in hardware but not carrier-certified; your carrier’s website is often the fastest compatibility check.
Time / Disruption Expectation
Most users see “Activating” or “Downloading” for one to three minutes. Service on the source device is typically suspended as soon as the carrier accepts the remote provisioning request.
If You Don’t See the Transfer Option
| Missing Element | Likely Cause | Next Step |
| No device-to-device transfer option | Manufacturer UI doesn’t include it | Use QR code: go to Add eSIM → Scan QR code and use the code from your carrier app or website |
| No “Add eSIM” option at all | Device may lack eSIM hardware or be carrier-locked | Check manufacturer specs; contact carrier to confirm device compatibility |
| QR code scan fails | Camera permission or lighting issue | Grant camera access in Settings → Apps → [Your Camera/Settings app] → Permissions |
| Plan downloads but doesn’t activate | Carrier provisioning delay | Wait 5 minutes, toggle Airplane mode off/on; call carrier if still inactive |
Cross-Platform Note
- Moving from any Android device to iPhone or from iPhone to Android relies on carrier-side remote provisioning. Use your carrier app, carrier website, or QR code activation—not device-to-device transfer menus.
If you’re on an older Apple iPhone that first popularized eSIM support (like iPhone XS, iPhone XS Max, or iPhone XR) or a newer model like iPhone 14 or iPhone 14 Pro, the same general rules apply—but your exact steps may differ depending on whether your carrier pushes activation via the App Store carrier app or issues a QR code instead.
Building Autonomous AI & Data Agents with Python
Hands-on engineering course with ReAct agents, MCP tool integrations, and LangChain/CrewAI production patterns.