Ledger and Product - going from Sandbox to Production

[armor]

I have been developing a product in my Sandbox and wanted to move it production to initial acceptance testing. I had created 2 ledgers in my Sandbox.

1. Cloud to Device, Device Scope that holds the device configuration data.
2. Device to Cloud, Device Scope that confirms the version that is on the device back to the cloud (so you can know when the device has updated to a specific version).

I created the 2 ledgers in the Production account before I deleted the instance for the specific device in the Sandbox.

There was a flashed error that couldn't be read when creating the instance of the configuration. There is now 2 instances shown in count but only one visible. The attempt to delete the instance in the Sandbox results in a partial deletion but the device remains and now the Production configuration isn't being picked up by the device recreated under the production product.

Could you help by letting me know the order I should have done this transfer and whether I need to delete the ledgers in Sandbox totally - in other words, how can this be recovered.

[rickkas7]

My guess is that having ledgers with the same name for a claimed device will cause confusion. The problem is that when you connect to a ledger from user firmware it only takes a name. However, if you have a device that is both in an organization product and claimed to a user, which ledger is now ambiguous because the name can exist in two places, the org and the sandbox. Since the device originally was associated with the sandbox, I suspect it won't release that association.

The easiest solution is probably to avoid using the same ledger name in sandbox and organization.

[armor]

Do I need to raise a support ticket to get the ledger(s) deleted so I can recreate them with different names?

[armor]

Deleted the new ledgers in production and recreated them with a different name. All working now.