1. What device migration covers
Device migration is the move onto or off an older platform: device credentials (the identity triple), the thing model, device shadow data, and telemetry history. Tools and APIs cover bulk export and import, incremental migration, and checkpoint resume, so the move stays controlled and traceable. Customers already use it for platform cutovers and for merging instances, including large fleets and long histories.
2. What moves
Device credentials / the device triple
Identity fields such as ProductKey, DeviceName, and DeviceSecret export and import as JSON or CSV, so the device can authenticate on the new platform.
Thing model / device shadow
Thing-model mapping, shadow data (desired and reported), tags, groups, and similar metadata, with a compare before and after the move.
Telemetry / history
Historical telemetry exports for a time range and imports into the target platform’s time-series database, so the business record stays continuous.
3. A typical migration
4. How you migrate, and how you limit risk
| Method | What it does |
|---|---|
| Adapter pull | An adapter pulls the device list and data from another vendor’s platform, so the move can be automated |
| File import | Prepare JSON or CSV in the platform’s format and upload it in the console |
| Phased run | Move device metadata first. After it checks out, move historical telemetry |
| Dual-write | During the move, devices report to the old platform and the new one. Cut traffic over once the new platform is stable, so the business is less likely to stop |
| Rollback | A rollback plan returns the fleet to the source platform if the move goes wrong |
5. What to get right
Sample the data before you move it, and compare device counts and key attributes between source and target. Pre-migration and post-migration checks are there so nothing is silently dropped. SimtoLink can design the migration, write the check scripts, run the move, and prepare rollback, and help the cutover through. Contact us for a design review, script work, and on-site support.
Appendix: a migration you can operate afterward
Treat the cutover like any other production change. On a pre-production or pilot batch built like live, rehearse a connection storm, a full disk, certificate rotation, and a cross-region failure, and keep the result as an acceptance checklist. Put metrics, alert thresholds, the on-call path, and audit retention into change management, so a parameter change can be traced and rolled back without living only in someone’s memory. Quarterly, development, operations, security, and data should ask whether the metrics still explain the business risk, and bind each fix to a ticket and a release. Observability, orchestration, and audit are one asset on the SimtoLink Device Management Platform. The console, the open API, and export stay in service after launch. If the move has to be reviewed against your ITSM, IAM, data lake, or edge cluster, the SimtoLink solutions team can sit in and return implementation advice and a risk list.