Development

Frappe Workspace Missing After bench migrate?

Alaa HaririPublished Updated 3 min read

Illustration: an app sidebar with one empty slot, and the missing workspace being put back into itIllustration: an app sidebar with one empty slot, and the missing workspace being put back into it

A workspace that disappears after bench migrate is either hidden from your user or deleted from the site. From Frappe version 16, migrate deletes public workspaces that no installed app ships as a file, and early version 16 releases deleted workspaces created in the browser too. Version 15 does not do this, and in every version a workspace is only navigation: the documents it linked to are untouched.

This guide is written by Akwad Programming, a Frappe and ERPNext company in Doha, Qatar, from the upgrades we run for clients.

Is the workspace hidden or deleted?

Open the Workspace list as an Administrator or a user with the Workspace Manager role. It is at /desk/workspace in version 16 and /app/workspace in version 15.

  • If the record is there, the workspace exists and you have a visibility problem.
  • If it is not, check the migration output. Frappe prints Deleting entity Workspace <name> for each workspace it removes.

Why can’t a user see a workspace that exists?

A workspace that exists but doesn’t show is usually blocked by its module, its roles, its private setting or the Is Hidden flag. Frappe shows a workspace only when the user may see it:

  • Module: the workspace’s module must not be blocked for that user.
  • Roles: if the workspace lists roles, the user needs at least one of them.
  • Private workspaces are visible only to the user who created them. In version 16 they have moved under My Workspaces on the new desktop screen, so users often think they have gone.
  • Is Hidden removes a workspace from navigation without deleting it.

Compare the result with an authorised account. Two users can see different navigation on the same site.

Which workspaces does bench migrate delete?

In version 16, bench migrate includes a clean-up step. Frappe lists the workspace JSON files in every installed app, then deletes each workspace in scope that has no matching file. What is in scope has changed between releases, according to the frappe/frappe source at each release tag (checked 15 November 2026; we re-check with each new Frappe release):

  • v16.0.0 to v16.4.0: every public workspace, including ones created in the browser.
  • v16.4.1 to v16.49.0: public workspaces that have both a Module and an App set.
  • v16.50.0 onwards: public workspaces marked Standard only. Workspaces created on the site are left alone.
  • Private workspaces are never part of this step.

Version 15 removes orphaned DocTypes during migrate, but not workspaces.

Version 16 also changed navigation: a persistent sidebar, a desktop screen and the move from /app to /desk. Its migration notes warn that changes made to standard workspaces such as Buying or Selling are lost. Copy them before you migrate.

How do you keep a custom workspace through migrations?

Export the workspace as a JSON file inside your own app’s module, so bench migrate finds a matching file and keeps it. To ship it in your app:

  1. Turn on developer mode on a development site.

  2. Set the Module. Set the workspace’s Module to one of your app’s modules.

  3. Save it as public. In recent version 16 releases, also mark it Standard. Frappe writes it to a file:

    your_app/your_app/<module>/workspace/<workspace_name>/<workspace_name>.json
  4. Commit the file and deploy it with the app. The next migrate finds the file and keeps the workspace.

Before migrating production, take a backup and keep the log:

bench --site your-site backup
bench --site your-site migrate 2>&1 | tee migrate.log
grep "Deleting entity Workspace" migrate.log

Run the migration on a separate test copy (staging) first, with the same app versions planned for production. Compare the Workspace list before and after.

How do you recover a deleted workspace?

Restore the last backup taken before the migration on a separate test site and take the workspace definition from there. Add it to your app as a file, or recreate it in a way the next migrate will not remove, before you migrate again. Otherwise the next migrate deletes it again.

Include workspace navigation, permissions and a sample of user roles in your deployment acceptance checks.

Sources checked on 15 November 2026

Akwad Programming builds custom Frappe apps and hosts ERPNext and Frappe sites for companies in Qatar, with upgrades tested on a separate test copy before they go live. We also moved Qatar Athletics Federation’s ERPNext server to AWS and run its upgrades. Tell us your Frappe version and what went missing.

Need help with a Frappe upgrade?

Tell us what you want to fix or build on Frappe, and we’ll suggest where to start.