Use cases / Migration
Migration and consolidation.
Each device generation brought its own app and cloud; support costs a little more each time, for a foundation that isn’t fully yours.
- App 2016 · cloud A
- App 2019 · cloud B
- App 2022 · cloud C
Your platform, in your cloud
| Batch | Devices | State |
|---|---|---|
| Pilot batch | 250 | moved |
| Batch 1 | 4,800 | in progress |
| Batch 2 | 6,100 | queued |
| Batch 3 | 3,900 | queued |
Old platform runs alongside until the last batch · rollback ready for every batch
For manufacturers with multi-cloud silos.
For you if…
- You have been making connected devices for several generations.
- Your apps and clouds come from different teams or suppliers.
- You also need to monitor other brands’ devices.
What you get
- The scoping report, yours even if you stop there
- One platform, in your cloud
- The whole fleet’s data, carried over
- Other brands’ devices too, in the same tool
A typical project.
Example-
2 weeks
Scoping
Scoping puts what exists on one page and sets the pilot batch.
-
4 to 6 weeks later
Pilot batch
A first slice of the fleet moves over, tracked device by device.
-
Then
The next batches
At the pace the pilot proved, until the old clouds are switched off.
-
At the end
What you own
The code in your repository, documentation and access credentials.
How we migrate without downtime.
Your users keep their app, their devices and their history. What changes happens behind the scenes.
- 01No data lost
Accounts, settings and history follow each device, batch after batch.
- 02No disruption
The same app on the stores, updated rather than replaced.