Move a Local Project to Cloud

Move a local project to Cloud when its Brain should become shared. The first migration creates and adopts a new Cloud Project in the chosen Workspace, then binds the existing local project to its Cloud Brain for ongoing sync.

Before you migrate

1. Make sure the local Brain is in a state you are comfortable sharing.
2. Review the target Workspace, its members, and the intended Project visibility.
3. Confirm that you are allowed to create or manage Projects in that Workspace.
4. Keep a normal backup or Git history for the local project before any large change.

Choose the target

In the desktop app, first switch to the destination Workspace. Migration uses the currently selected Workspace and creates a new Cloud Project there; it does not attach the local project to an existing Cloud Project. Only Workspace owners and admins can perform this migration.

MindMux shows the target explicitly so you can avoid placing the project in a similarly named but incorrect Workspace. Do not rely on repository names to make this choice.

Review the transfer

Migration copies the structured project knowledge into the newly attached Cloud Brain. Review the resulting Pages and root pages in the Cloud app before inviting collaborators or relying on remote access.

Local files and local operational state are not interchangeable with Cloud service state. In particular, session logs, task runtime data, and local-only configuration should not be assumed to become shared knowledge merely because a Brain was migrated.

Work after migration

After migration, the desktop project's local Brain and its attached Cloud Brain are synchronized. Use the Cloud Project for browser work and remote MCP clients, and use the desktop app when filesystem workflows matter. If the product reports a sync conflict, review both versions and choose the explicit keep-local or keep-cloud resolution instead of editing around it.

If your team changes the source of truth again, use the product's connection or migration flow and communicate the decision to collaborators.

Common checks

• Can every intended collaborator open the Project, and nobody else?
• Are key root pages and active Pages present in the Cloud Project?
• Do wiki links resolve as expected?
• Has the team agreed where future edits should happen?

For the distinction between the two models, see Local and Cloud Brains.