Android eSIM Transfer: Carrier and EID Checks

Verify carrier transfer paths, target handset EID and IMEI numbers, and profile deletion order before moving an eSIM between Android or iOS devices.

Unbranded matte-black smartphones beside a silver laptop, metal ejector pin and notepad on a wooden desk

Check carrier transfer rules, target handset identifiers and profile deletion order before moving an active line.

In AOSP eSIM Transfer carrier integration, the entitlement server (ES) SHOULD separate the subscription transfer and subscription activation operations, which prevents carriers from deactivating the pSIM or eSIM in the source device if there is a profile download failure in the target device, so users do not have deactivated SIMs on both devices. Specifically, ManageSubscription(3:TRANSFER) SHOULD be followed by ManageSubscription(5: ACTIVATE TERMINAL ICCID) to verify the successful profile download before the ES triggers the transfer in the carrier network.

In the Android Open Source Project (AOSP) eSIM Transfer architecture, eSIM Transfer clients allow transferring eSIM profiles or converting physical SIMs to eSIM on the same device, and are compatible on source devices running Android 10 and higher and target devices running Android 14 or higher. On Google Pixel phones, if your device did not automatically detect eSIM transfer, contact your carrier to activate your eSIM, and your existing device or eSIM can still work even if your eSIM transfer is not successful.

If you have not yet verified whether your handset model and regional variant support embedded SIM profiles, start with our Android eSIM phone and carrier support check and browse the Compatibility category or our Android compatibility hub before initiating a line move.

Scroll horizontally to see all columns.

Pre-transfer check Documented platform or carrier rule Verification action
Source screen lock authorizationThe source device must be protected with a screen lock (for example, a PIN lock), and the source device screen lock verification must be used to authorize and proceed with the eSIM Transfer flow.Configure and verify the lock screen credential on the outgoing handset before starting the transfer menu.
Entitlement eligibility checkIn AOSP eSIM Transfer carrier requirements, the eligibility check (GSMA Service Entitlement Configuration §6.5.2 CheckEligibility) MUST support failure due to account issues (for example, suspended account, unpaid dues, or eSIM Transfer restrictions) and failure due to device liability (for example, enterprise, prepaid, or MVNO).Confirm account standing and plan liability restrictions with your operator when self-service transfer is declined.
Target EID binding stateFor SubjectCode[5.2.6.1] and ReasonCode[5.2.6.2] from GSMA (SGP.22 v2.2), a SubjectCode of 8.1.1 and a ReasonCode of 3.8 means the EID is bound to another device.Ask the carrier to release or rebind the profile if the target handset rejects download with this code pair.
Subsidy or carrier lock stateUnder AOSP OPERATION_DOWNLOAD, ERROR_CARRIER_LOCKED means the device is not allowed to download because the device is carrier locked (SIM locked).Verify carrier unlock completion on the destination handset before requesting a profile swap.
Carrier account transfer lockOn T-Mobile, if you are upgrading or transferring service to a new device, make sure to turn off SIM Protection before following the eSIM setup steps, or if you do not, you will receive an error.Disable account-level transfer protection in your carrier portal or app prior to initiating the swap.

Verify how GSMA TS.43 and Android handle transfer and deletion

The supported GSMA TS.43 ODSA primary-based eSIM Transfer method follows the call flows as described in Section 8.9 of GSMA TS.43. For carrier eSIM Transfer integration, AOSP recommends the TS.43 temp-token with EAP-AKA approach (CR1052 method). During the AOSP eSIM Transfer flow, the eSIM Transfer client on the source device performs the TS.43 procedures EAP-AKA, CheckEligibility, and AcquireTransferToken, and the entitlement server returns a temporary token and an expTime value indicating the lifetime of the token. In the AOSP eSIM Transfer flow, a secure channel is established between the SM-DP+ and the LPA through the ES9+ interface, and the profile is downloaded from the SM-DP+ server based on the activation code.

For the TS.43 subscription transfer, the carrier backend system SHOULD be able to process a SIM swap request (triggered by an authorized ManageSubscription(3:TRANSFER SUBSCRIPTION) function) in under 5 seconds for the majority of all transactions. If the carrier backend system requires more than a few seconds to respond to the SIM swap request, the carrier and ES MUST support delayed download by polling defined in TS.43 section 7.3.2.

In AOSP EuiccManager, deleteSubscription() deletes a subscription with a subscription ID; if the subscription is currently active, it is first disabled, and the caller must have either WRITE_EMBEDDED_SUBSCRIPTIONS or carrier privileges for the target subscription. When erasing all subscriptions on a device via the AOSP system API, starting in Android 11, you should provide an EuiccCardManager#ResetOption enum value to specify whether to erase all test, operational, or both types of subscriptions.

To delete an eSIM on a Pixel phone, open your phone’s Settings app, tap Network & internet > Mobile network, select the eSIM you want to delete, and tap Erase eSIM; to require a password to delete an eSIM, open your phone’s Settings app and tap Security > Advanced > Confirm SIM deletion. On Cricket Wireless, if an eSIM deletion occurred after a hard reset of your phone, upon re-start be sure to choose Keep Your SIM or Keep Your Cellular Plan shown on your device to retain your eSIM profile rather than Delete All (or it will delete your eSIM and you might have to purchase a new one), and if you need further assistance contact Customer Support at 1-800-CRICKET (274-2538) or dial 611.

Overhead view of unbranded slate-gray and matte-black smartphones side by side with a coiled braided cable on a dark desk mat
Keep the outgoing handset active and unlocked nearby until the replacement handset finishes downloading and activating the line.

Check target EID, IMEI pairings, and eUICC error codes

For physical tray access and accessory clearance checks on your handset, review our Android device compatibility checklist.

In Android 9, profile management APIs (public and @SystemApi) are available through the class EuiccManager, while eUICC communication APIs (@SystemApi only) are available through the class EuiccCardManager. In AOSP IRadioConfig HAL v1.2, SimSlotStatus in the getSimSlotsStatus method (introduced in v1.0) includes the Embedded Identity Document (EID). For devices running Android 14 or higher, Android supports the MEP-A1 and MEP-B options for the selection of the issuer security domain root (ISD-R) and the selection of eSIM ports as specified in GSMA SGP V22 3.0. To help make sure that users do not lose service when they move eSIM profiles from one port to another, AOSP recommends that carriers provide support for fluid mapping of IMEI and SIM and multiple ICCIDs or SIMs for each eUICC identifier (EID).

Scroll horizontally to see all columns.

System API or modem state Documented AOSP behavior Troubleshooting check
Hardware EID lookup callIn AOSP EuiccManager, getEid() gets the EID identifying the eUICC hardware, may be null if the eUICC is not ready, and requires that the caller must have carrier privilege or the READ_PRIVILEGED_PHONE_STATE permission.Wait for the embedded chip state to initialize and verify carrier app permissions when EID reads empty.
SM-DP+ error extrasIn AOSP eUICC error handling, EXTRA_EMBEDDED_SUBSCRIPTION_SMDX_SUBJECT_CODE is used with EXTRA_EMBEDDED_SUBSCRIPTION_SMDX_REASON_CODE, which together provide the SubjectCode[5.2.6.1] and ReasonCode[5.2.6.2] from GSMA (SGP.22 v2.2).Read both diagnostic extras together when an activation code download fails on the target handset.
Profile install errorUnder AOSP OPERATION_EUICC_GSMA, ERROR_INSTALL_PROFILE indicates an error with eUICC while trying to install profile, for example when the profile already exists or the ICCID does not match.Check whether an existing profile for that line is already stored on the target chip or whether the carrier issued a mismatched identifier.
Default boot profile stateWhen there is no operational or test profile enabled on eSIM, the default boot profile is enabled, and the modem recognizes the eSIM with the default boot profile enabled as a valid SIM, reports the card as valid to upper layers, and does not turn off the SIM power.Distinguish an active carrier subscription from the factory boot profile when inspecting modem slot status.
Subsidy lock card stateIf the eSIM is SIM locked (subsidy locked), the modem sets the card state as CardState:RESTRICTED in the getIccCardStatusResponse method.Confirm the carrier subsidy lock is cleared when the modem reports a restricted card state.

To use a mobile network, a phone needs an IMEI (International Mobile Equipment Identity) number, and to use an eSIM, a phone also needs an EID (Embedded Identity Document) number; when you set up a new SIM on a Pixel phone, you may need to give your carrier your phone’s IMEI 1, IMEI 2, or EID numbers. Pixel phones that can use both eSIM and SIM cards have 2 IMEI numbers, one for each kind of SIM, and if you have 2 IMEI numbers, IMEI 1 is usually paired with the first SIM you set up with your phone (to confirm, check with your mobile carrier).

To find your Pixel phone’s EID number, check your phone’s box or open your phone’s Settings app, tap About phone > SIM status, and find EID. To find your Pixel phone’s EID QR code, open your Settings app, tap Network & internet, next to Mobile network tap Add > Download a SIM instead?, and tap Next > Activating in a store?.

Unbranded matte-black smartphone beside a plain white retail box, pulled-out metallic nano-SIM tray, ejector pin and pen on an oak workbench
Locate the hardware identifiers from the device settings menu or original packaging before contacting carrier support.

Compare Android-to-Android and iPhone-to-Android transfer paths

In iOS 26.3 and iPadOS 26.3, you can transfer your data and eSIM from your iPhone or iPad to an Android device using the built-in camera or Settings app. On an iPhone or iPad, when you tap Cellular and tap Transfer eSIM under Transfer to Android, once you select a number and complete the transfer process, the number will no longer work on your iPhone or iPad.

Scroll horizontally to see all columns.

Transfer workflow Documented OS, device, and carrier requirements Preparation step
Google Pixel automatic transferTo use automatic transfer on Google Pixel phones, both your new and current devices must have Android 12 or later, the current version of Google Play Services, and a set up screen lock.Update system services and enable screen locks on both Pixel handsets before starting onboarding.
Google Pixel Settings transferTo transfer an eSIM from Settings on a Google Pixel phone, open your device's Settings app and tap Network & internet > SIMs > Add SIM > Transfer SIM from another device.Use the Settings menu path when moving a line after initial handset setup is already finished.
Apple iPhone or iPad to AndroidTo use the Apple iPhone or iPad to Android transfer feature, you need a compatible version of Android 17, and to transfer an eSIM in the USA, you need a supported carrier (AT&T, FirstNet, T-Mobile, Verizon).Verify both operating system builds and carrier eligibility before starting cross-platform migration.
Samsung Galaxy Instant Transfer (Android)On Samsung's US Galaxy support page, the USA network carriers that may allow eSIM Instant Transfer are AT&T, Boost Mobile, Cricket, FirstNet, Mint Mobile, Spectrum Mobile, T-Mobile, U.S Cellular, Verizon, and Xfinity Mobile.Contact your network operator directly if your carrier or plan type does not appear on that carrier list.
Samsung Galaxy Instant Transfer (from iOS)On Samsung's US Galaxy support page, the US network carriers that may allow eSIM Instant Transfer from an iOS device are AT&T, FirstNet, T-Mobile, and Verizon.Use the operator mobile app or activation portal when switching from iOS on an unlisted US operator.
T-Mobile iPhone to Google Pixel post-setupOn T-Mobile, transferring an existing SIM from an Apple iPhone to a Google phone after initial setup requires a current Apple iPhone 11 or newer running iOS 26 or higher, a new Google Pixel 9 series or newer, both connected to Wi-Fi with PIN / Password enabled.Place both devices close together on Wi-Fi with screen lock enabled before launching the transfer prompt.
Silver flat-edged smartphone and charcoal-black smartphone angled toward each other on a wooden desk in front of a white home Wi-Fi router
Connect both the outgoing and incoming handsets to stable wireless internet before starting a cross-platform line transfer.

Match carrier app rules on Verizon and T-Mobile

When you use the My Verizon app to move an existing mobile number to a different eSIM-enabled smartphone or feature phone, you will not need the device IMEI number or SIM ICCID number, there is no need to search and scan a QR Code, and your service is activated instantly over Wi-Fi. When moving a line in the My Verizon app, you need your old phone for authentication if there is only one line on your account, and after you move your number to the new device, service is deactivated on the old phone.

On T-Mobile, for other devices, open the T-Life app, then choose SIM transfer or activation > Get Started, enter the IMEI number for the device you are transferring your eSIM to, enter the EID, if prompted respond to the interactive SMS (iSMS) to confirm the change, and connect to Wi-Fi and scan the QR code. In the T-Mobile Prepaid eSIM app, if you upgraded your phone and want to transfer your eSIM line of service to your new phone (other than switching from one iPhone to another via Quick Start or through device settings), you will need to call 1-877-778-2106 with your Prepaid eSIM phone number or OrderID and your account PIN code.

Frequently asked questions

What does GSMA SGP.22 SubjectCode 8.1.1 with ReasonCode 3.8 indicate during an eSIM download?

In AOSP eUICC error handling for SubjectCode[5.2.6.1] and ReasonCode[5.2.6.2] from GSMA (SGP.22 v2.2), a SubjectCode of 8.1.1 and a ReasonCode of 3.8 means the EID is bound to another device.

Do you need the target phone IMEI, ICCID, or a QR code when moving a line in the My Verizon app?

When you use the My Verizon app to move an existing mobile number to a different eSIM-enabled smartphone or feature phone, you will not need the device IMEI number or SIM ICCID number, there is no need to search and scan a QR Code, and your service is activated instantly over Wi-Fi.

How do you transfer a T-Mobile Prepaid eSIM app line when upgrading to an Android phone?

For a line set up in the T-Mobile Prepaid eSIM app, if you upgraded your phone and are not switching from one iPhone to another via Quick Start or device settings, you will need to call 1-877-778-2106 with your Prepaid eSIM phone number or OrderID and the account PIN code you set up in the T-Mobile Prepaid eSIM App.

Record both devices’ identifiers and your carrier transfer policy

Complete this pre-transfer verification record before erasing any profile on your outgoing phone:

  • Outgoing handset status: current screen lock setup, active cellular connection for receiving authentication texts, and installed operating system version.
  • Target handset identifiers: Embedded Identity Document value from settings or retail packaging, plus primary and secondary equipment identity numbers.
  • Unlock and protection state: carrier subsidy unlock status on the target handset and account-level transfer protection status on the carrier line.
  • Selected transfer channel: device-to-device setup wizard, post-setup settings menu, carrier mobile app, or operator customer support call with account credentials.
  • Deletion confirmation gate: verification that the replacement phone places calls and carries mobile data before removing the old profile.

Sources

  • Android Open Source Project (AOSP) — eSIM Transfer carrier integration
  • Android Open Source Project (AOSP) — eUICC APIs
  • Android Open Source Project (AOSP) — Handle eUICC API errors
  • Android Open Source Project (AOSP) — Modem requirements for eSIM support
  • Android Open Source Project (AOSP) — Multiple enabled profiles
  • Google Pixel Phone Help — Transfer a SIM to a new phone
  • Google Pixel Phone Help — Find your IMEI and other Pixel phone ID numbers
  • Google Pixel Phone Help — How to use dual SIMs on your Google Pixel phone
  • Apple Support — Transfer an eSIM and data from your iPhone or iPad to an Android device
  • Samsung US Support — SIM cards for your Galaxy phone or tablet
  • Verizon Support — Move your current Verizon mobile line to an eSIM device FAQs
  • T-Mobile Support — SIM card & eSIM
  • T-Mobile Support — T-Mobile Prepaid eSIM app
  • Cricket Wireless Support — Transfer my number to a new phone using eSIM