Migrating from a 3rd Party to LORIOT

Migrating from another provider to LORIOT can be done easily but requires some cooperative effort. 

The former provider has to provide the customer with some data that the LORIOT team will need to be able to import the devices.

The following parameters are required to migrate OTAA devices:

  • DevEUI
  • AppEUI or JoinEUI
  • AppKey also known as Application Key or Device Key
  • NwkSKey also known as Network Session Key
  • AppSKey also known as Application Session Key

These parameters are essential and will have to be delivered by the customer as LORIOT can’t access them otherwise. DevEUI, AppEUI/JoinEUI and AppKey are usually provided by the device manufacturer, NwkSKey and AppSKey on the other hand must be provided by the LoRaWAN network provider. With this information LORIOT can import the devices.

In order to migrate the gateways to LORIOT the customer must make sure that the packet forwarder used by the former provider has been removed from the hardware, for commonly used software like Semtech’s Packet Forwarder LORIOT can be provided guidance on how to proceed. Should the former provider use their own custom packet forwarding software, it is possible that their cooperation may be needed.

Subsequently, the LORIOT Gateway Binaries - our advanced packet forwarder - can be installed to connect to the LORIOT server. Our free online documentation hub provides a guide for each model that has been integrated with our Gateway Binaries. Should your gateway model not be among them, you can always use the Semtech Packet Forwarder which is also supported by LORIOT.

Migrating between LORIOT instances

As a customer grows, oftentimes they will upgrade their account from a Public Server instance to a Professional Public Server (PPS) account or move from the PPS to a LORIOT Private Network Server.

In this scenario, LORIOT can easily access all necessary information for the migration and the customer only has to communicate which resources have to be transferred from instance A to instance B.

To help us identify the resources to be moved, it’s necessary to also communicate the following information:

  • Origin user account where the resources are currently registered.
  • Destination user account where the resources are to be transferred.
  • AppID of all applications that contain the devices on the origin user account.
  • NetworkID of all networks that contain the gateways on the origin user account.

From this data, LORIOT can extract all necessary information to migrate all the resources.

It’s best practice to migrate devices and gateways as close to simultaneously as possible, this way LORIOT can preserve the frame counters of the devices with minimal packet loss, making sure the application continues working through the migration with as little interruption as possible.

Migrating from LORIOT to a 3rd party provider

Flexibility is very important to us and it’s part of our core philosophy to offer our customers as much flexibility as possible in order for them to succeed.

Some LNS providers will try to lock in their customers by making it exceedingly difficult to leave their solution, however, we at LORIOT don’t believe this is fair towards the customer.

All necessary information to migrate and register a device or gateway is freely available from our user dashboard.

On one hand, the parameters to identify the device can be easily accessed from the device’s detail page:

On the other hand, the keys required to encrypt and decrypt the payload and the communication between server and sensor can be accessed from the device’s LoRaWAN Parameters submenu:

Our documentation hub also provides a quick guide on how to remove our Gateway Binaries from a gateway.

In case additional information should be required, do not hesitate to ask LORIOT and we’ll provide you to the best of our ability.