IoT SIM vs eSIM vs iSIM for Global Deployments

The form factor question arrives late and decides early. Hardware is being finalised, a launch date exists, and somebody asks whether the design should take a plug-in SIM, an eSIM, or an iSIM. Whatever gets answered in that meeting is locked into the product for its full service life, which for most IoT hardware is five to ten years.

Most teams do not choose the wrong form factor. They choose for the first market and then discover what it costs in the fourth.

The three options

Removable SIM: 3FF, 4FF, MFF2

A physical card in a tray, or an MFF2 chip soldered to the board. MFF2 is the industrial default: it survives vibration, temperature range, and the decade in the field that a tray-mounted card does not. It is still a discrete component with its own supply chain and its own line on the bill of materials.

The profile is written before the device ships. Changing it later means a truck roll, or a person with a screwdriver, or a courier and a return.

eSIM: eUICC

Same hardware footprint as MFF2 in most designs. The difference is the software on it. An eUICC holds multiple operator profiles and switches between them over the air, so the network a device uses is a decision you make after deployment rather than before.

GSMA SGP.32, the IoT-specific remote provisioning specification, is what made this practical for constrained devices. Earlier eSIM standards assumed the consumer and M2M models, which suited phones and cars better than a battery-powered sensor on NB-IoT.

iSIM: integrated SIM

The SIM function moves into a secure enclave inside the cellular modem or system-on-chip. No separate component, no solder pad, less board space, lower power draw, and one fewer part to source.

The constraint is hardware. iSIM exists where the chipset vendor put it, so it is available on newer modules and absent from the design you shipped in 2022. It is a decision made at silicon selection, not at connectivity procurement.

Where the choice actually bites

Three deployment realities separate these options. None of them are visible in a datasheet comparison.

Permanent roaming rules

A device that ships from Norway and lives in Brazil for eight years is not roaming in any sense a regulator recognises. Several markets restrict permanent roaming outright, others cap it by duration, and enforcement varies by country and by carrier relationship. The pattern repeats across Brazil, Turkey, Canada, China, and a handful of others, and the specifics shift.

This is the strongest argument for eUICC in a multi-country fleet. When a market closes to permanent roaming, a profile switch over the air keeps the estate connected. A removable SIM with a fixed profile leaves you with a logistics project instead.

IXT supports local IMSI options in key markets to reduce permanent roaming risk, which addresses the same problem from the network side rather than the form factor side. Both approaches work. Having neither is what hurts.

Provider portability

Ask a straight question of any provider: if this relationship ends in year three, what does the exit look like? With a soldered MFF2 carrying a fixed profile, the answer involves visiting every device. With an eUICC, the answer is a provisioning campaign, assuming the profile management is not locked to the incumbent.

Portability is a contract term as much as a technical property. Establish who controls the eUICC subscription manager before signing, not afterwards.

Lifecycle cost, not unit cost

Unit price ranks iSIM cheapest, then MFF2, then eUICC. Lifecycle cost ranks differently, because one field visit to a device in another country consumes the savings from several thousand units. Price the truck roll you are trying to avoid and the comparison changes shape.

How they compare on the things that matter

Remote profile switching

• Removable SIM: no. Physical replacement.
• eSIM: yes, over the air, via SGP.32 for IoT deployments.
• iSIM: yes, using the same eUICC provisioning model in the enclave.

Board space and power

• Removable SIM: largest footprint, tray designs add a failure point.
• eSIM: same footprint as MFF2.
• iSIM: smallest, lowest power draw, no discrete component.

Hardware availability today

• Removable SIM: universal.
• eSIM: broad across current industrial modules.
• iSIM: limited to newer chipsets, so confirm against your exact module.

Retrofit onto a shipped device

• Removable SIM: possible where a tray exists, at the cost of a visit.
• eSIM: not retrofittable, but profile changes remove most of the reasons you would want to.
• iSIM: not retrofittable at all.

Decision guide

Match the option to the deployment rather than to the specification sheet.

• Choose a removable SIM for single-market deployments, short-life hardware, pilots, and any design where a device is reachable by a person without a travel budget.
•  
• Choose eSIM for multi-country fleets, long-life hardware, markets with permanent roaming exposure, and any programme where the commercial relationship with a provider has to stay changeable. For most cross-border IoT deployments this is the default.
•  
• Choose iSIM where board space, power budget, or bill-of-materials count decide the design, and the chipset already supports it. Treat it as an eSIM with better physical characteristics, because operationally that is what it is.
•  
• Do not choose on unit price alone. The cheapest option per device is the one most likely to require a field visit, and the field visit is the expensive part.

What the form factor does not decide

The form factor sets how the device connects and how easily that changes. It sets nothing about what happens to the traffic afterwards.

All three options leave device traffic on the public internet unless the network is configured otherwise. All three leave the estate flat, with every device reaching every other one, unless segmentation is applied above them. All three give you a SIM identity and no enforcement, because enforcement lives in the network and cloud.

Those are separate decisions with separate answers. IXT SecureNet keeps the traffic off the public internet.IXT Zero Trust checks every session in the network and cloud and segments the estate. IXT CMP shows the fleet in real time, which matters when other portals report on a 24 to 48 hour delay. IXT Global SIM ships in all three form factors across 600+ mobile networks in 190+ countries, so the form factor question stops being a connectivity procurement question at all.

Frequently asked questions

Which is right for a multi-country deployment?

eSIM for most, on the strength of remote profile switching. It answers permanent roaming restrictions, carrier changes, and provider exit without touching hardware. iSIM gives the same operational behaviour where the chipset supports it.

Is iSIM a replacement for eSIM?

Not commercially. iSIM integrates the same eUICC capability into the modem or SoC. It is a packaging change with real hardware benefits, on the same provisioning model.

Do I need eSIM to avoid permanent roaming problems?

No. Local IMSI options and multi-IMSI arrangements address the same restrictions at the network layer, on a removable SIM. eSIM gives more headroom because the profile itself is changeable after deployment.

Can an eSIM profile be switched without touching the device?

That is the point of it. Under SGP.32, profiles are downloaded and swapped over the air, which suits constrained IoT hardware better than the earlier consumer and M2M models.

Does eSIM lock me to one provider?

The technology does not. The contract sometimes does. Ask who controls the subscription manager and what a migration involves before you commit.

What about devices already in the field?

Form factor is fixed at manufacture, so the work happens at the network layer instead: local IMSI options, routing, segmentation, and visibility across the estate you already have.

Next step

Bring the deployment plan rather than the datasheet. Markets, device life, expected fleet size, and how reachable each unit is once installed. Those four facts settle the form factor question in about ten minutes. Ask us how it works for your deployment, or book a demo at ixt.io.