SIM to eSIM Migration Guide

Step-by-step guide for operators and users migrating to eSIM.

| 5 min read

SIM to eSIM Migration Guide

The transition from removable SIMSIMApplicationSmart card for mobile network authentication.Click to view → cards to embedded eSIMeSIMApplicationProgrammable embedded SIM chip.Click to view → technology is one of the most significant shifts in mobile hardware since the smartphone era began. For device manufacturers, mobile network operators, and enterprise IT teams managing fleet devices, understanding the migration path — its technical requirements, business implications, and practical steps — is essential to executing a smooth transition.

The Evolution of SIM Technology

The SIM card was standardised by ETSI in 1991 as a portable credential store for GSM authentication. Over three decades it shrank from a credit-card-sized plug-in SIM to the nano-SIM used in modern smartphones — but the fundamental model remained: a physical card holding a single operator's credentials, swapped manually when changing carriers.

Generation Form Factor Size Year Key Change
Full-size SIM 85.6 × 54 mm Same as credit card 1991 Original GSM
Mini-SIM (2FF) 25 × 15 mm Small plastic carrier 1996 Dominant until 2010
Micro-SIM (3FF) 15 × 12 mm iPad/iPhone 4 2010 Thinner devices
Nano-SIM (4FF) 12.3 × 8.8 mm iPhone 5 onward 2012 Smallest removable
eSIM (MFF2) 6 × 5 mm (soldered) IoT / no tray 2016 No physical swap
iSIMiSIMApplicationSIM integrated into device SoC.Click to view → Integrated in SoC Wearables 2018 Zero footprint

The iSIM represents the logical endpoint — the SIM function is a dedicated security domain within the application processor, eliminating even the discrete eSIM chip. This guide focuses on the transition from physical SIM to eSIM, as iSIM remains a minority deployment.

eSIM Benefits for Operators and Enterprises

Benefit Operator Perspective Enterprise/Consumer Perspective
Remote provisioning Reduce physical SIM logistics No store visit for carrier change
Multi-profile Sell secondary profiles on competitor devices Separate work/personal on one device
Soldered reliability Fewer warranty claims (no broken tray) Device survives harsh environments
Smaller device Enable watch, earphone, ring form factors Thinner, lighter products
Faster market entry Software-defined product launch Immediate connectivity on unboxing
M2M scale Manage millions of devices via SM-SRSM-SRProvisioningSecure routing entity for M2M eSIM profile management.Click to view → Fleet provisioning without field visits

RSP (Remote SIM Provisioning) is the core enabler. GSMA SGP.22 governs consumer devices; SGP.02 governs M2M. Both use an OTA channel to deliver encrypted operator profiles to the eUICCeUICCProvisioningReprogrammable SIM chip supporting remote profile switching.Click to view → chip.

eSIM Ecosystem Readiness Assessment

Before migrating, audit your current environment across five dimensions:

  1. Device compatibility — Does the hardware include a certified eUICC? Use the esim-checker to validate EIDEIDIdentityNational ID with embedded chip.Click to view → (eUICC Identifier) presence and SGP standard support.
  2. Operator support — Does your primary MNO offer eSIM activation? Not all markets have full GSMA RSPRSPApplicationOver-the-air SIM profile management.Click to view → infrastructure.
  3. MDM integration — Enterprise MDM platforms (Jamf, Microsoft Intune, VMware Workspace ONE) must support eSIM profile push for zero-touch provisioning.
  4. Roaming policy — Multi-profile eSIM changes roaming economics; negotiate data roaming agreements before migration.
  5. Legacy device tail — Physical SIM devices may remain in service for 3-7 years; dual-mode (physical + eSIM) transition plans are common.

Migration Checklist

Phase 1: Planning

  • [ ] Inventory all device models and confirm eUICC support via EID audit
  • [ ] Identify MNO SM-DP+ endpoints and confirm GSMA certification
  • [ ] Map MDM platform eSIM management capabilities (profile push, LPALPAProvisioningDevice-side app for managing eSIM profile operations.Click to view → API)
  • [ ] Define profile naming convention and multi-profile policy
  • [ ] Assess iSIM roadmap for next hardware generation

Phase 2: Pilot

  • [ ] Deploy eSIM on 50–100 devices across all device models
  • [ ] Test profile download, enable, disable, and delete via MDM
  • [ ] Validate OTAOTAPersonalizationRemote card management via mobile network.Click to view → delivery in all target geographies
  • [ ] Measure tap-to-connect latency vs. physical SIM baseline
  • [ ] Test fallback scenarios (SM-DS unavailable, SM-DP+ timeout)

Phase 3: Rollout

  • [ ] Configure SM-DP+ bulk profile pre-provisioning for zero-touch activation
  • [ ] Update helpdesk runbooks (eSIM troubleshooting differs from physical SIM)
  • [ ] Communicate to end users: QR code activation vs. push activation flow
  • [ ] Monitor SM-DP+ Proof of Receipt rates (target >99.5%)
  • [ ] Disable physical SIM slots via MDM policy on migrated devices

Phase 4: Steady State

  • [ ] Automate OTA profile refresh on contract renewal
  • [ ] Implement certificate expiry monitoring for eUICC certificates
  • [ ] Schedule quarterly SM-DP+ capacity and latency reviews
  • [ ] Track GSMA SGP specification updates (SGP.32 for IoT is emerging)

Common Migration Pitfalls

Pitfall Impact Mitigation
EID not captured at procurement Cannot remotely provision Mandate EID in device purchase specs
SM-DS not configured Device never finds pending profile Verify SM-DS endpoint in LPA configuration
MDM lacks eSIM API Manual activation required at scale Require eSIM MDM support in RFP
Single-profile assumption in code Enterprise app breaks with profile switch Update app to handle SIM change events
Roaming profile conflicts Users stranded abroad Pre-load roaming profile before travel

For M2M and IoT-specific migration patterns, see the Smart Cards in IoT Guide and the eSIM Remote Provisioning Guide. For SIM card fundamentals, consult the SIM Glossary entry and iSIM reference.

Pertanyaan yang Sering Diajukan

Our guides cover a range of experience levels. Getting Started guides introduce smart card fundamentals. Security guides address Common Criteria certification and key management. Programming guides target developers working with APDU commands, JavaCard applets, and GlobalPlatform card management.