Transfer a project

Two different operations sound like the same thing, and in a free workspace picking the wrong one can mean waiting 24 hours before you can put it right. 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 and comments. 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
• An archived project comes out of the Archive
• Enabled connectors are cleared
• Enabled skills are cleared
• Its email domains are removed, so it sends from its built-in address and stops receiving their mail until someone in the new workspace adds them again with new ownership records, which needs a paid plan there
• Its forwarding addresses start over with the new workspace owner's account email

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

Both workspaces' plans are applied again once the move finishes. A site that lands in a Free workspace gets the Modulify badge back, and a published one is republished so visitors see it. Its custom domains are paused there until that workspace is on a paid plan, see When your plan ends, and a site with paused custom domains that lands in a paid workspace gets them back. If the workspace it left had a site locked for being over its plan, the freed slot unlocks the most recently updated locked site.

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.

Accept a transfer

The recipient accepts from the link in the invitation email, or from Pending invitations in the sidebar. Both open a dialog titled Do you want to accept this project into your workspace? with the project's thumbnail and name.

Select Workspace decides where the project lands. It starts on the workspace you have open and lists every workspace you belong to, so a project can go straight into a team workspace instead of your own. Then choose Accept Project.

The workspace you pick needs a free slot for the project, unless it is the workspace the project is already in, since taking it over there adds nothing new. When the workspace you have open is full, you get the same Add an extra site? or Site limit reached! prompt as when you create a project. When another workspace is full, the dialog stays open with a Workspace is full message naming it, so you can pick a different one.

What moves with a transfer

The site itself goes across intact: pages, files, database, uploaded files, environment variables, custom domains, comments 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
Deploy hooks and their call log	Their URLs are secrets the previous owner may still be calling from their own systems
Folder	Folders belong to a workspace
Archive	The Archive belongs to a workspace, so an archived project arrives unarchived
Enabled connectors and skills	They are granted per workspace
Email domains, when it lands in another workspace	The new workspace has to prove it owns each one, by adding it again with a new ownership record, and the sending records can change too
Email forwarding addresses, when it lands in another workspace	They are the previous team's mailboxes, so the list starts over with the new workspace owner's account email

The recipient opens a project with a fresh chat and starts their own conversation with it. Every old deploy hook URL stops working at the handover, so the recipient adds new hooks if they want them.

Sites whose code lives in your GitHub

A site whose code was moved to your own GitHub has that code copied back to Modulify whenever it leaves the workspace, through Move to Workspace or a transfer accepted into another workspace. A transfer accepted into the same workspace keeps the code where it is.

Such a site cannot leave while its code is still being copied into GitHub, while Modulify has lost access to its repository, or once its repository was deleted on GitHub, and the move or the transfer answers why. A copy back that fails stops the transfer without using up the invitation, so the recipient can accept it again once the problem is fixed. When several projects move together and a copy fails part way, the others still move, and a Some projects stayed toast names the ones left behind. See Handing the site to someone else.

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 while an invite is still pending you wait 1 minute before sending another.

Separately, a project in a free workspace can only be moved or transferred once every 24 hours. The message reads Projects in a free workspace can only be moved or transferred once every 24 hours. 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 workspace the recipient picked and disappears from yours, and both workspaces' project counts adjust. Both workspaces' plans are applied again, the same way as after a move. The recipient sees Project transferred with the name of the workspace it is now in.

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.