Skip to main content
Transfer your personal Replit Apps to a team workspace to enable collaboration and centralized project management. This personal-to-team workflow allows you to:
  • Share apps with team members instantly
  • Centralize project management within your organization
  • Maintain deployment uptime and URLs during transfer

​
Transfer a personal app to a team workspace

App transfer moves ownership of a Replit App from your personal workspace to a team workspace. Once transferred, the app becomes accessible to team members according to workspace permissions and is managed under the team’s resources and billing. For this personal-to-team workflow, the transfer is immediate and irreversible. It maintains all deployment configurations and URLs.

​
Getting started

You must be a member of the target team workspace before transferring apps. Verify your team membership by selecting your profile or workspace selector in the upper-right corner to view available teams.
For a personal-to-team transfer:
  • Transferring a Replit App to a team workspace is irreversible
  • Published apps experience zero downtime during transfer
  • Deployment URLs remain unchanged
  • You must be a member of the team you want to transfer the app to before initiating transfer

​
How it works

1

Access your Apps

Navigate to your personal Apps by selecting the Apps tab from your Replit home page.
2

Select the app

Locate the application you want to transfer in your Apps list.
3

Open transfer options

Select the three dots (•••) menu next to the app name.
Three dots menu next to app name showing transfer options
4

Choose transfer option

Select Transfer To Organization from the dropdown menu.
5

Select destination

Choose the target team workspace from the available organizations dialog.
6

Confirm transfer

Select Transfer To Organization to confirm the action.
7

Verify completion

You’ll see a “Transfer success” notification in the bottom-right corner of the page. Refresh your Apps page to verify the app no longer appears in your personal workspace, then navigate to your team workspace to confirm the app appears there.

​
Transfer between team workspaces

You can move a project from one team workspace to another in the Projects list. This action is irreversible. The transfer runs in the background, so the confirmation only tells you that it has started.

​
Before you start

This workflow requires all of the following:
  • Both the source and destination must be team workspaces in the same billing account. You can’t use this workflow with a personal project or personal workspace.
  • You must have the Owner access level on the project.
  • You must have the Admin or Member role in the destination workspace.
Only eligible workspaces appear as destinations. If you don’t see the destination workspace, check these requirements before you try again.
1

Open the project actions

In the source workspace, open Projects, find the project, then select the three-dot menu on the project card and choose Transfer to workspace.
Project card overflow menu showing the Transfer to workspace option
2
In the transfer dialog, open the Destination Organization dropdown and choose the destination workspace.
Transfer dialog with a destination workspace selector, linked Account Secrets warning, and Transfer to Workspace button
3
Review the warning about linked Account Secrets. Then select Transfer to Workspace. The project leaves its current workspace when the transfer completes.
4

Verify the transfer

Wait for the background transfer to finish. Switch to the destination workspace. Then check Projects. Replit renames the project if the destination workspace already contains a project with the same name.

​
What transfers and what to check

  • Linked Account Secrets: These don’t transfer. Re-link them in the destination workspace. See Account Secrets.
  • Custom domains: Domains connected to the project move to the destination workspace.
  • Deployments: Replit redeploys the current build after the transfer, and the deployment keeps its public or private visibility. If the destination workspace enforces private deployments, transferring a public deployment fails. Make the deployment private or unpublish the project before you transfer it.
  • Individual collaborator access: Replit restores individual project access only for active Admins and Members of the destination workspace. Viewers and other collaborators lose individual project access.

​
Bulk transfer options

For transferring multiple applications, use CLUI commands:
  • Core to team workspace: Use org transfer-repls
  • Team to team workspace: Use org transfer-repls-org-to-org

​
Next steps

To learn more about team collaboration and workspace management, see the following resources: