Renewal comes round. The quote is worse than last time, the support has thinned out, and you start pricing the alternative. Then someone works out what it costs to move 40,000 devices that are already installed on rooftops, in basements and inside vehicles.
The conversation ends there. You sign again.
That moment is what provider portability is about. Not the contract you sign at the start, but whether you hold a real choice at the end of it.
Provider portability is the ability to move a deployed fleet to a different connectivity supplier without touching the hardware and without rebuilding everything you connected to it.
It is a property of the architecture, not a clause in the agreement. A contract that permits you to leave is worth very little when the physical fleet makes leaving impossible. Most teams find this out at renewal, which is the worst moment to find it out.
The deepest one. A soldered SIM holding one operator profile with no remote provisioning ties that device to one supplier for as long as the device exists. Changing supplier means changing hardware, which means sending an engineer to every installed unit. For a fleet in the field, that cost exceeds any saving on the connectivity itself.
Your team learned one portal. Your processes assume its groupings, its alert thresholds, its reports. The historical usage data that supports your capacity planning sits inside it. None of that travels, and rebuilding it takes months of work nobody has budgeted.
The API you wired into provisioning, billing and support. Every connectivity API models SIMs, sessions and events its own way, so migration means rewriting the integration and re-testing the workflows on top of it. Teams that built deep integrations are the most locked in, and they built the integration because the provider encouraged it.
Volume commitments, minimum terms, and per-SIM deactivation fees on a fleet of tens of thousands. These are the visible ones and the ones people negotiate. They are also the easiest to escape compared with the three above.
The GSMA eSIM standard for IoT, SGP.32, addresses the hardest of the four. It defines remote provisioning for devices with no screen and no user, so a new operator profile downloads to a soldered SIM in the field without anyone visiting it.
Earlier eSIM standards were written around consumer phones and assumed a person to accept the change. That assumption made them poorly suited to a water meter in a basement.SGP.32 removes it, and adds a management layer that handles profile changes at fleet volumes rather than one device at a time.
Ask a supplier for SGP.32 by name. Ask which of your form factors support it. And ask who holds the keys to the provisioning service, because a standard implemented in a way only your current supplier controls returns you to where you started.
Being straight about this matters more than the marketing version.
Six questions. The answers tell you more than the contract does.
A supplier confident in their service answers these directly. Hesitation on question two is the signal to pay attention to.
IXT runs a dedicated mobile core built for IoT from the ground up. One SIM covers 600+ mobile networks across 190+ countries, in physical SIM, eSIM and iSIM form, so consolidating carrier contracts does not mean adopting one carrier's fate.
The IXT CMP exposes live SIM data through an API, so your operational data sits in your systems as well as ours. That is a portability decision as much as an integration one.
Here is the part most suppliers leave out. Any provider you choose becomes a dependency. The question is not whether one exists but how expensive it is to end. What reduces that cost is standards-based provisioning, hardware that accepts a new profile remotely, and your data held somewhere you control. Choose on those, not on the promise.
No. Multi-network coverage means one supplier reaching many networks. Portability means changing supplier. A fleet reaching 600 networks through one supplier that it is unable to leave has coverage and no portability.
It solves the hardware half. The platform, the integration and the commercial terms are untouched by it.
Before hardware freeze. The SIM decision is the one that hardens, and it hardens permanently. Everything else stays negotiable for longer.
The installed fleet stays where it is until the hardware is replaced. Apply the standard to the next production run and treat the existing units as a fixed cost of the original decision. Most teams migrate in generations rather than all at once.
It sets the tone for a serious commercial conversation. A supplier that reacts badly to the question has told you something useful at no cost.
Choosing an IoT connectivity provider is two decisions wearing one name. The first is who serves you now. The second is what your options look like in three years, and that one is settled by the hardware you freeze and the standards it supports.
Most teams spend their effort on the first and inherit the second. Reverse that order.
Ask us how it works for your deployment. Book a demo at ixt.io.