Migrate · How-to
From Azure IoT Hub and other platforms
Map device twins, direct methods and routing to IoT Core, and import devices through the API.
Updated 11 Nov 20262 min read
All ThingsX IoT Core pages
- What ThingsX IoT Core does
- Quick start: connect your first device
- Key concepts
- Security and access
- Connect Wi-Fi and IoT devices
- BLE gateways, shelf labels and child devices
- LoRaWAN sensors and gateways
- Industrial I/O modules
- Device twins and state
- Send commands to devices
- Rules: react to device messages
- SDK and REST API
- Monitor your fleet and support customers
- Moving from another IoT platform
- From AWS IoT Core
- From Azure IoT Hub and other platforms
- Device can't connect
- Devices keep disconnecting or reconnecting
- Data isn't arriving or a rule doesn't fire
- Frequently asked questions
- Topics and limits reference
Azure IoT Hub
| Azure IoT Hub | ThingsX IoT Core |
|---|---|
| Device identity | Thing (the device ID becomes the thing name and client ID) |
| X.509 authentication (thumbprint or CA) | Certificate, registered and pinned by fingerprint: no re-flashing |
| Symmetric key (SAS) | Password credential; the device's connection settings change |
| Device twin: desired and reported properties | Twin: desired and reported state, with delta |
| Direct methods, cloud-to-device messages | Commands with acknowledgement |
| Message routing and endpoints | Rules with HTTP, queue and republish actions |
| Device Provisioning Service | Bulk registration through the API, or Get started for small fleets |
| Device-to-cloud topics | IoT Core telemetry and event topics |
Steps
- Export your device list and twins with your usual tooling (for example the Azure CLI) to CSV or JSON.
- Register devices through
POST /v1/onboarding/quick-connectorPOST /v1/things, and register each existing device certificate withPOST /v1/certificates/registerso devices keep it. - Update device firmware or configuration for the new endpoint, root CA and topics. Devices on symmetric keys need their new password credential.
- Re-create routes as rules and test each on the bench.
Your own MQTT server
If your devices already talk MQTT to a server you run yourself:
- Keep your topic layout for the move by republishing with rules, then move devices to the IoT Core topics over time.
- Register existing client certificates so devices keep them, or issue password credentials if you used usernames.
- Replace access-control files with policies; check them with the policy simulator before switching.
Other cloud IoT services
The same pattern works for any platform: export the device list and credentials, register them, map state and messages to twins and commands, and re-create routing as rules. Talk to us and we help plan it.
Was this page helpful?
Can't find what you need? Contact support or read about ThingsX IoT Core.