Transfer a project

Two different operations sound like the same thing, and picking the wrong one wastes a day. Move to Workspace moves a project between workspaces you already belong to. Transfer hands it to another person, who has to accept.

Before you begin

Transferring needs the Transfer projects permission in the workspace, and moving needs Move projects in both the workspace it leaves and the one it enters. Without them the menu items are disabled and the tooltip says which permission is missing.

The destination has to have room. If the target workspace's plan has no free site slot, the move is refused with a message asking its owner to upgrade.

Move to another of your workspaces

Choose Move to Workspace from the project's card menu. A dialog titled Move to Workspace asks you to Select Workspace from the ones you belong to, then Move.

The item is disabled when you belong to only one workspace, with the tooltip You have no other workspaces to move this project to.

Selecting several projects first and using Move to workspace on the selection bar moves them together.

A move keeps the project's chat history. It does clear a few things that only make sense in the old workspace:

• The project leaves its folder and lands in the destination's main projects list
• Enabled connectors are cleared
• Enabled skills are cleared

You become the project's creator in the new workspace.

Transfer to another person

Choose Transfer from the card menu. A dialog titled Transfer Project asks for the recipient's Email, then Transfer.

Modulify emails them an invitation. The invite is good for 7 days.

Nothing has moved yet. Until the recipient accepts, the project stays exactly where it is, and its card shows a Transfer pending badge in the bottom left. Clicking that badge, or Manage Transfer in the card menu, reopens the dialog with the invited address locked and a Cancel Invitation button in place of Transfer.

Selecting several projects and using Transfer on the selection bar invites the same person to take all of them.

What moves with a transfer

The site itself goes across intact: pages, files, database, uploaded files, environment variables, custom domain and publish history.

Some things are deliberately left behind, because they belong to the old owner rather than to the site:

Cleared on transfer	Why
Chat history and sessions	The conversation is the previous owner's working record
Chat attachments	Uploaded alongside those messages
Webhooks and their delivery history	They point at the previous owner's systems
Folder	Folders belong to a workspace
Enabled connectors and skills	They are granted per workspace

The recipient opens a project with a fresh chat and starts their own conversation with it.

Waiting periods

Transfers are rate limited, and the message always tells you exactly how long is left.

You can invite the same recipient once every 3 minutes, and send a new invite while one is still pending once a minute.

Separately, a project in a free workspace can only be moved or transferred once a day. The message reads Projects in a free workspace can only be moved or transferred once a day. followed by the remaining wait. Paid workspaces have no such limit.

After it completes

The sender gets an email confirming the transfer. The project appears in the recipient's workspace and disappears from yours, and both workspaces' project counts adjust.

If you had the project open when the transfer completed, the page reloads so you are not left editing something you no longer own.

Next

• Folders covers moving a whole folder between workspaces.
• Sharing and cloning is the option when you want them to have a copy rather than the original.