Migrating a Customer Account to PDK.io 2.0

Integrator

Existing PDK.io 1.0 Legacy Cloud Nodes in Customer Accounts can be migrated to PDK.io 2.0, enabling the use of new features within the Customer Account.

The migration process for Cloud Nodes to PDK.io 2.0 supports migrating a single Cloud Node to a PDK.io 2.0 Customer Account.

Pre-Migration Process

Before a Cloud Node can be migrated to PDK.io 2.0, it must be running the most current firmware for the Cloud Node. A notification message will be displayed at the top of the Cloud Node Dashboard if a Cloud Node is not on the most current firmware.

As Cloud Nodes are updated in batches, selecting Prioritize ensures that the Cloud Node that needs to be migrated is prioritized for update. 

Once a Cloud Node has been prioritized for an update, to remove it from the priority update queue, select Remove Prioritization on the notification message at the top of the Customer Dashboard. This will cancel the prioritized update, moving it to normal priority.

Beginning the migration process

If a Cloud Node has the current firmware, the notification message at the top of the Customer Dashboard will prompt you to select for more information or to begin the update to PDK.io 2.0.

Selecting Update on the notification message will initiate the migration process.

If no issues are detected that could interfere with the migration of the Cloud Node, the message window will indicate this and prompt you to begin the update by selecting Next. If the Device Configuration step fails, it is commonly due to non-device identity devices being present. For information on updating these devices, please refer to Converting Legacy Devices to Device Identity.

After selecting Next, the Cloud Node will be ready to be staged for migration. Selecting Update System will stage the Customer Account, preliminarily converting the Cloud Node data to PDK.io 2.0.

Once the Cloud Node has been staged for migration, the Installation Partner can review the settings on the Cloud Node to confirm everything is correct before moving on to the next step.

While reviewing the Staged Cloud Node, a notification will appear at the top of the Customer Dashboard, allowing the Installation Partner to either revert the Cloud Node to a Legacy System or proceed with the migration by selecting Transfer Registration.

After confirming the information on the Cloud Node and the Installation Partner is ready to migrate the Cloud Node to PDK.io 2.0, select Transfer Registration. A final prompt regarding the migration will then be displayed. Select Transfer Registration to synchronize the Staged data and complete the migration of the Cloud Node to PDK.io 2.0. Once completed, the Cloud Node will no longer be in the Customer Account where it was previously located. Instead, it will be registered and synced in a new Customer Account with the old Cloud Node name.

Once completed, the Customer Account can be accessed in the same manner as a newly created PDK.io 2.0 Customer Account.