Skip to content

Buyer guide

Moving off AWS IoT Core: what changes and what stays the same

5 min read · Updated 16 November 2026

Why do teams move off a cloud IoT service?

  • To run the device cloud in their own cloud account or region
  • To add LoRaWAN and gateway-connected devices to the same registry
  • To give support teams clearer diagnostics: a reason for every refused connection
  • To reduce dependence on a single cloud provider

How do AWS IoT Core concepts map to ThingsX IoT Core?

The building blocks are the same, so nothing has to be relearned:

AWS IoT CoreThingsX IoT Core
Thing and thing registryDevice in one registry (Wi-Fi, gateway children, industrial I/O, LoRaWAN)
X.509 certificatesX.509 certificates; devices keep theirs
IoT policiesLeast-privilege JSON policies, with a simulator
Device shadowDevice twin with desired and reported state and the delta
Jobs and direct commandsCommands that are stored, retried and acknowledged
Rules engine (SQL)Rules in SQL with a test bench and replayable failures

What are the steps in a migration?

  • Export your things, certificates, policies and topics
  • Map them to ThingsX IoT Core and test policies in the simulator
  • Point a small batch of devices at the new endpoint
  • Run both systems side by side and compare data
  • Move the rest of the fleet in batches
  • Retire the old setup once every device reports in

Do devices need new firmware?

No. Devices keep their certificates and connect to a new endpoint. If your firmware has the endpoint hard-coded, an over-the-air configuration change is usually all that's needed.

What about Azure IoT Hub or a self-run MQTT server?

The same approach applies: devices, credentials, access rules, twins and routing all have equivalents. The ThingsX IoT Core docs have step-by-step pages for AWS IoT Core, Azure IoT Hub and other platforms.

Questions buyers ask

What is a good alternative to AWS IoT Core?

ThingsX IoT Core covers the same building blocks (registry, certificates, policies, twins, commands and SQL rules), adds LoRaWAN and per-device diagnostics, and runs as a managed service or in your own cloud.

Can we migrate from AWS IoT Core without downtime?

Yes, by moving devices in batches while both systems run side by side, and retiring the old setup only when every device reports to the new one.

Do we lose our device certificates when we migrate?

No. Devices keep their existing X.509 certificates.