Overview
If you need to move a bridge from one Iris studio or organization to another, whether for a new production setup or restructuring your teams, this article guides you through safely unlinking and migrating a bridge device using the Iris UI.
Step-by-Step Guide
1. Confirm Intent to Migrate
Migration is not automatically reversible.
Ensure the target studio or organization is already created. If not, be sure to create it during the following steps.
2. Open the Iris App and UI
Launch the Iris app on a machine connected to the same subnet as the Bridge machine you wish to migrate. This can be the same machine, or a different machine.
In your Iris Studio, click the Bridges icon (top right corner).
3. Check Current Bridge Assignment
The current organization and studio will be shown. If it is communicating well and as expected, there will be a green dot next to the bridge name.
Make sure the bridge is active and responsive before proceeding.
4. Unlink the Bridge
Select the bridge and click Unlink.
Confirm the action when prompted. The bridge will be unassigned.
5. Switch to the New Studio or Organization
In the Iris UI, switch to the desired organization and studio.
Go to the Bridges window and click Search for Devices.
6. Link the Bridge Again
Iris will detect the unlinked bridge as well as other bridges that are running on the network.
Click Link Bridge next to the bridge name.
If previously linked, you'll be prompted to confirm the reassignment.
Click Link Bridge with this Studio (red button).
7. Complete the Migration
The Iris app will restart.
The bridge will now be linked to the new studio/organization.
How It Works and What to Expect
A bridge can only be linked to one studio at a time.
Linking to a new studio severs the old connection.
System metrics and settings will reset for the new environment.
Tips, Limitations, and Best Practices
Always check network connectivity before unlinking or linking.
Do not perform migrations during live production.
Restart the Iris app manually if it does not do so automatically.
Document the bridge’s previous setup if needed.
FAQs
Can I link a bridge to two studios?
No, a bridge can only be assigned to one studio at a time.
Will unlinking delete my settings?
Studio-specific settings may be reset; local configurations may persist.
Is there a backup option before unlinking?
Not currently; we recommend noting key configurations manually.
Can I migrate a bridge across organizations?
Yes. As a note, you’ll need to confirm the unlinking explicitly.
Does the bridge need to be on the same network during migration?
Yes, it must be discoverable on the same subnet.
Will I lose control access during migration?
Yes, the bridge is unlinked during the process.
What if my bridge doesn’t show up after unlinking?
Ensure it's powered on, the app is open, and it is connected to the correct network environment.
Use Cases
Moving a bridge to a new project studio.
Consolidating multiple studios under one organization.
Cleaning up bridge assignments across a large team.
Reassigning hardware due to operational shifts.
Decommissioning an old studio and transferring its bridge.
Conclusion
Migrating a bridge requires a clean unlink and re-link process. Be deliberate and confirm all actions to ensure your bridge is assigned correctly.
