Backups, selective restore and version history
Export selected sections, restore compatible backups and recover previous public versions.
Last reviewed 24 July 2026Backups and version history solve different problems. A backup moves or preserves workspace data; version history recovers a previously published state.
Choose the sections that belong in the backup.
OrbitPage exports structured workspace data such as profile, links, theme, menus and supported settings. Selective export is useful when moving content without replacing the destination workspace's full configuration.
Media references may depend on the edition and storage environment. Keep original assets separately when they are business-critical.
Inspect the source before applying it to an existing page.
Selective restore lets the user choose which compatible sections to import. This avoids replacing a current theme when only links or a menu are needed.
OrbitPage keeps readers for older supported backup formats. New fields use defaults when an older backup did not contain them.
Published revisions provide a fast way back.
Managed publishing records immutable revision metadata and keeps a bounded history. Restoring a revision republishes the chosen state as the current page rather than mutating an old object in place.
Use history for accidental edits. Use an exported backup for migration, offline retention or a larger recovery plan.
A backup is useful only after a restore has been tested.
Export before major restructuring and after important launches. Store copies outside the same browser and service account.
For self-hosted deployments, application data, uploaded files, secrets and the surrounding server require their own infrastructure backup plan.
