Installing the on-board app is reversible. Decommissioning hands control of Maintenance, Tasks and Inventory back to the cloud so the on-board server can be switched off.
The important part is that it is not a switch but a drain. The yacht gets the chance to upload everything it still holds before anything is handed over.
Running it
Decommission sits at the bottom of Vessel Settings → On-board app and appears only while the yacht is vessel-managed. It opens the Decommission on-board app window.
1. Confirm. The window explains what happens next: the on-board app stops taking new changes and starts uploading whatever remains, and cloud-side edits stay blocked until the whole cycle finishes. Start decommission begins it.
2. Drain in progress. The cloud waits for the yacht to report that it has finished uploading, checking every 30 seconds. If the yacht is offline, this step simply waits until it reconnects.
3. Drain complete. Once the yacht confirms it has pushed everything, Complete decommission becomes available.
4. Done. Completing it revokes the on-board server's device, returns the yacht to cloud-only, and confirms the server can be shut down safely. The read-only banners disappear and the cloud app works normally again for that yacht.
Keep the window open until Complete decommission is available. The window says you can close it and come back, but once the drain has started, the tab no longer shows the Decommission button, so there is no way to reopen the window and finish from there.
What crew see aboard
Once a decommission starts, the on-board app stops accepting changes. Pages still open and records stay readable, but saving a change is refused. The app is finishing what it has, not taking more. The cloud stays read-only for the same three areas until the cycle completes, so plan the changeover for a quiet moment. There is no other place to keep editing in the meantime. Everything reopens for editing in the cloud as soon as the decommission completes.
Things that block it
- The yacht has to report in. The cloud will not complete a decommission on its own. It waits for the yacht to say it has finished. An administrator cannot skip this step, because doing so would throw away whatever was still queued.
- Stuck changes block the drain. If any change made aboard is stuck, the yacht never reports that it has finished. Resolve those first. See Sync Errors.
If the yacht's hardware has failed and will never report in, there is a separate escape route that deliberately accepts the loss of anything not yet synced. See Long Outages and Hardware Failure.
Afterwards
The yacht is cloud-only again, exactly as before, with all the work done aboard now in the cloud. The on-board app can be installed again later. That is a fresh install with a new device.