Hello @rabochyyar ,
Unfortunately, there’s no way of transferring releases from one organization to another. There is a way of recreating the release in another fleet, but it’s a bit cumbersome and hasn’t been fully tested. For that reason is not a recommended process, but here it is in case you’re fine taking the risk:
- Flash a development image of the original fleet in a new device.
- Pin that device to the release you want to copy and wait for the update to complete.
-
balena sshinto the device and runbalena images. Save the ID of all images you want to retrieve. - Run
echo balena save <imageIds> | balena ssh <deviceUuid> | docker loadto transfer all images from the device into your local docker instance. - For each image, run
docker tag <image> <project>_<service>.balena deployexpects images to be tagged according to docker-compose’s scheme, which is<project>_<service>. - Retrieve the
docker-compose.ymlused to build the release you are copying over. The file can be found in theReleasestab in the dashboard. Put the compose file in an empty directory named<project>. - Run
balena deploy <newFleet>from inside the directory created in step 5. If all works as expected, this should upload the saved images to your new fleet.
Cheers,
Nico.