Migrating devices from Chirpstack V3 to V4

Viewed 64

We currently have both ChirpStack V3 and V4 running in production, with each serving a subset of our devices. We need to migrate all active V3 devices to V4 in such a way that they continue to operate without requiring re-activation or re-join on V4.

So far, I’ve successfully migrated a few devices (2–3) using the ChirpStack activation APIs:

  • Retrieve the device’s activation parameters from the V3 API.
  • Create the device in V4 using the API, and then use the V4 activation API to activate it with the parameters obtained from V3.

Is this approach considered valid for migrating all devices? The official documentation only mentions migrating the database, so I want to confirm whether API-based activation cloning is supported or recommended.

Thank you.

1 Answers

Please see:

Using the above documentation and migrationt tool you should be able to migrate ChirpStack v3 devices to ChirpStack v4 with minimal downtime and without the need to re-activate these devices. However, this migration tool supports only ChirpStack v4.11.

This is a better way than using the API, as the above migration tool also migrates the MAC state of the device (obtained through exchanging mac-commands).

Is there a way to get v4.11 Chirpstack package (linux_amd64.deb specifically)? Main repo only shows lates version for me

Thank you for your response. We also have a scenario where we are moving from a single central ChirpStack instance to multiple distributed ChirpStack instances to manage our devices. In this case, we need to migrate devices from the central ChirpStack v4 deployment to the distributed v4 deployments. Would using the API to create and activate devices be the recommended approach for this migration?