Automatic cloud backups keep BoatKit’s recoverable vessel state in your own Google Drive or OneDrive account. You choose the folder, then BoatKit writes a complete configuration archive daily or weekly. Passwords, API keys, provider tokens, and BoatKit Cloud keys are deliberately omitted.
Track, trip, and Trip Log history can be backed up separately from raw sensor history. Either history family can be excluded, fully replaced on each run, or stored as a baseline followed by smaller incremental archives. BoatKit publishes the completed manifest last, so an interrupted upload does not become the restore point.
Google Drive opens Google’s folder picker in your normal browser and grants BoatKit access to an existing folder you select. You can use that folder as the vessel root or have BoatKit create one new folder directly inside it. OneDrive likewise opens normal Microsoft sign-in in your browser, then keeps BoatKit’s folder browser within its application folder. The final selected location is already the root for that vessel; BoatKit does not add another vessel-named directory below it.
During first-run setup, BoatKit can connect to the same provider and restore the complete committed series before BoatKit Cloud pairing. You can replace the original device and recover its vessel identity, or create a separate vessel that copies the configuration and history while keeping a new identity. Separate-vessel restores disconnect the source backup folder so two vessels never write to the same series. Backed-up configuration, dashboards, integrations, maintenance records, routes, vessel history, and sensor history return; credentials must be entered or issued again.
Setup and restore are administrator operations performed through a direct local connection to the BoatKit device. See the backup and restore guide for prerequisites, archive choices, and recovery steps.