Skip to content

Commit e485eb7

Browse files
Merge pull request #220548 from dominicbetts/central-migration-update
IoT Central: update migration article
2 parents 8dee680 + 56af970 commit e485eb7

File tree

1 file changed

+7
-2
lines changed

1 file changed

+7
-2
lines changed

articles/iot-central/core/howto-migrate-to-iot-hub.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -28,10 +28,15 @@ You need the following prerequisites to complete the device migration steps:
2828

2929
- The source IoT Central application where your devices currently connect.
3030
- The destination IoT hub where you want to move the devices to. This [IoT hub must be linked to a DPS instance](../../iot-dps/concepts-service.md#linked-iot-hubs).
31-
- The devices that you want to migrate must implement the **DeviceMove** command. The command payload contains the *ID scope* of the destination DPS instance.
3231
- [node.js and npm](https://nodejs.org/download/) installed on the local machine where you run the migrator tool.
3332

34-
## Setup
33+
## Device requirements
34+
35+
The devices that you want to migrate must implement the **DeviceMove** command. The command payload contains the *ID scope* of the destination DPS instance. The migrator tool repository includes an example [DTDL component model](https://raw.githubusercontent.com/Azure/iotc-migrator/main/assets/deviceMigrationComponent.json) that that defines the **DeviceMove** command. You can add this component to your existing device templates.
36+
37+
The tool repository also includes [sample code](https://github.com/Azure/iotc-migrator/tree/main/device_samples) that shows you how a device should implement the **DeviceMove** command.
38+
39+
## Tool setup
3540

3641
Complete the following setup tasks to prepare for the migration:
3742

0 commit comments

Comments
 (0)