Frappe Workspace Missing After Migration: What to Check

A workspace missing after a Frappe migration does not by itself prove that the workspace or its underlying business records were deleted. Start by distinguishing a visibility issue from a missing Workspace record, then compare the deployed app and framework versions.

Start with access and visibility

Check whether the workspace is public or private and which user owns it. Review the user’s roles and module access, and compare the result using an appropriately authorised account. Frappe supports role and module restrictions, so two users may see different navigation on the same site.

Review the deployment change

Record the Frappe version, installed app versions and the deployment that introduced the change. Check the migration output and compare the custom app files with the release that worked. If the workspace belongs to a custom app, confirm that its definition is included in the deployed version and that the app is installed on the affected site.

The original version of this article described orphaned workspace cleanup as a universal rule. That is too broad: workspace handling varies by release and customisation. Verify the behaviour in the source for the exact installed version before deciding that migration removed it.

Check major-version migration notes

Frappe version 16 introduced workspace changes. Its migration notes specifically discuss public and private workspaces and the treatment of standard-workspace customisations. Review those notes when moving to version 16 instead of applying assumptions from an earlier release.

Recover safely and prevent a repeat

Preserve a current backup and the migration logs. Reproduce the issue on a staging copy, compare the workspace with a known-good backup, and restore or correct the relevant definition only after identifying the cause. Include workspace navigation, permissions and representative user roles in deployment acceptance checks.

Keep app-managed customisations in version control and document which changes are maintained through the user interface. Test the next migration using the same app versions planned for production.

References and Frappe support

Read the official workspace access guidance and version 16 migration notes.

Akwad Programming provides Frappe development in Qatar, custom app maintenance and deployment support. Tell us about the affected version and workflow.