Baisalya · Guides
DevDesk · Backup & recovery

Back up DevDesk before reinstalling: what to export and reconnect

A practical recovery walkthrough: export DevDesk data, back up project folders separately, reinstall, reconnect workspaces and verify what must be restored by hand.

A DevDesk recovery kit does not contain every file on the device. DevDesk-managed records and the project folders you open in DevDesk are separate things. This fictional example uses a project called Orchard Notes to show what to save before reinstalling and how to check the result afterward. The current Backup and restore manual is the source for the exact controls.

Separate app data from project files

The Reinstall Recovery Kit exports supported independent DevDesk data plus a safe catalog that helps you reconnect recorded workspaces. It does not copy external project folders, Git repositories or exported files. Protected secret values, Android folder permissions, execution trust and AI connector access keys are not included either.

Keep separatelyWhat it preserves
Reinstall Recovery KitSupported DevDesk records and workspace names and location hints.
Project-folder backupMarkdown, project files, Git history and other files stored outside DevDesk.
Credential recovery methodWhere you will securely obtain protected API secrets again; do not put them in the kit or a README.
Permission planWhich folders need to be selected and authorized again after reinstall.

Before uninstalling

  1. Open Settings > Data backup and choose Export Reinstall Recovery Kit.
  2. Save the JSON file somewhere outside DevDesk's private storage, then confirm the file exists and has the expected date.
  3. Back up the Orchard Notes folder separately with a normal file copy or Git. Open the copy and check that project.devdesk and important project files are present.
  4. Check DevDesk's Recovery readiness card and pre-uninstall checklist. Note any workspaces that still need an independent folder backup.

For example, the recovery kit might remember the workspace name and a readable path hint. It cannot preserve the folder bytes at that path. If the project folder was only on the device and was not copied separately, the recovery kit cannot recreate it.

After reinstalling DevDesk

  1. Import the recovery kit and read its preview before choosing Replace or Merge.
  2. Reopen a few important DevDesk tools and check that their supported state is present.
  3. Open Reconnect Recorded Workspaces. Review each saved name and location hint, then select Reconnect a workspace and choose its actual folder.
  4. Repeat for every recorded workspace. On Android, grant the system folder permission again; on Windows, select the folder again.
  5. Re-enter protected secrets and re-approve workspace execution trust only when required.

Check the recovery, not just the import message

An import completing means the supported data was accepted; it does not prove that every project path or external secret is ready. Use a short verification pass:

  • Open Orchard Notes and inspect a known note or project task.
  • Open the external project folder and verify a few expected files, then open project.devdesk.
  • Check Saved API workspaces and confirm protected values are re-entered through the supported secret controls.
  • Try the exact workspace actions you need and confirm permissions or trust prompts appear as expected.

If a workspace name appears but its folder is unavailable, use the saved location hint to find your separate folder copy and reconnect it. Do not create a new empty folder with the same name and assume it is the original project.

Know the limits of older kits

Version 3 recovery kits include the workspace reconnection catalog. Older supported backups can restore independent records but may not include a workspace list, so those folders must be reconnected manually. The reconnection list comes from the latest imported kit, even when you merge independent records. Keep the kit you intend to use and review the import preview before confirming.

Treat exported backup JSON as private. It can contain ordinary confidential workspace information even though protected secrets are excluded. For full details, see the Backup and restore manual and Developer workspaces guide. This fictional walkthrough describes the current documented workflow; it is not a report of a customer recovery.