Transfer a project or team to a different account
Who can use this feature
Available on all paid plans
People on the Professional, Organization, or Enterprise plans can receive a project
People on the Organization or Enterprise plans can receive a team
Figma lets you transfer projects or teams to an organization. For example: If you work at an agency, you can transfer assets to a client after work has completed.
Note: The easiest way to move files between different accounts is to move them into a project and then transfer the project by following the instructions below.
If you or the recipient is on the free Starter plan—or you just have one or two files to move—you can also transfer files between accounts by saving a local copy and then importing it in another account.
There are three options for transferring work to a different account:
What's included in a project or team transfer?
Project or team transfers include the following resources:
Resource | Included |
---|---|
Files |
✓ |
Prototypes |
✓ |
Comments |
Yes, except when transferring a copy |
File version history |
Yes, except when transferring a copy |
Branches |
Yes, except when transferring a copy. When transferring a project from an organization to a Professional team, all branches show the last known state before the transfer. Creating new branches isn’t available on the Professional plan. |
Components in files where the library is included in the transfer |
✓ |
Components in files where the library is not included in the transfer |
Components will show the last known state before the transfer and will not receive updates afterwards |
Shared fonts |
X |
Private plugins |
X |
Published Community resources |
X |
Note: You can keep accessing files and prototypes at their original links after the transfer is complete. Projects and teams will get new links in the destination organization.
Transfer a project
When you transfer a project, all its files will move to the recipient’s team or organization.
When accepting the transfer, the recipient can choose whether to keep or remove access for everyone from the sending team or organization.
There are three steps to transfer a project:
- The recipient chooses a location for the project
- The sender makes a transfer request
- The recipient accepts the transfer request
1. Choose a location for the project
Before you can move a project, the recipient needs to choose a location for it.
An admin at the receiving team or organization will need to provide the sender with a destination URL. This tells Figma where the resources should go. To get this URL:
- Log into your Professional team in a web browser.
- From the file browser, click All projects in the sidebar.
- Copy the entire URL in your browser address bar.
- Share this URL with the admin transferring the project.
- Log into your Figma team or organization in a web browser.
- Navigate to the team the project will move into. You can always move the project to a different team later.
- Copy the entire URL in your browser address bar.
- Share this URL with the admin transferring the project.
2. Send a transfer request
- In the file browser, navigate to the project you want to transfer.
- Click the down arrow next to the project name and select Transfer.
- Review the information in the modal and press Next.
- Enter the destination URL and email address of your contact at the other company and press Request transfer.
Note: Transferring a project permanently moves it to the recipient’s team or organization. They may choose to remove your access when accepting the transfer—or at any time after the transfer is complete.
The admins at the receiving team or organization will receive an email to accept the transfer. You'll receive and email confirmation once the transfer is complete.
Caution: If you transfer a file that contains a published library, other files in your team or organization won’t receive updates from this library after the transfer is complete. We recommend keeping libraries and their files together.
3. Accept a transfer request
When someone sends your company a transfer request, Figma emails all admins of your plan asking them to review and accept the transfer.
- On the Professional plan, these are team admins.
- On the Organization or Enterprise plans, these are organization admins.
You’ll need to decide whether people from the sending party should keep their access to the resources and get added to your team or organization. You can choose to either Remove collaborators, or Keep all existing collaborators.
Remove collaborators
Everyone will lose access to the project except the admin who accepts the transfer and the designated contact person.
This option won’t create any new accounts in your team or organization, which means you can avoid paying for seats for people outside your company.
Keep all existing collaborators
Members from the sending party with a role on the project will get an account in your team or organization. This may add more paid seats to your subscription.
You can avoid paying for any seats from the sending party by making sure your default seat type is set to viewer-restricted or by manually adjusting everyone’s seats after the transfer is complete.
After you accept, you can find the project by navigating to its parent team in the file browser.
Caution: When you accept a transfer request, it takes around 5 minutes to move the project between companies. Members of the project won’t be able to use certain features of Figma during this time, like sharing the project or accessing some of its files. We recommend accepting the transfer at a time that will cause minimal disruption to members of the project or team.
Additional considerations for admins on the Enterprise plan:
- If there are guests in the project being transferred and you have restricted guest access, these guests won’t transfer with the project even if you choose to Keep all existing collaborators.
Send a copy of a project
When you send a copy of a project, all its files will move to the recipient’s team or organization. Only people on the receiving team or organization will have access to this copy. Any file branches, comments, and version history won't be transferred—these will stay with your original files.
There are three steps to transfer a project:
- The recipient chooses a location for the project
- The sender makes a transfer request
- The recipient accepts the transfer request
1. Choose a location for the project
Before you can move the project, the recipient needs to choose a location for it.
An admin at the receiving team or organization will need to provide the sender with a destination URL. This tells Figma where the resources should go. To get this URL:
- Log into your Professional team in a web browser.
- From the file browser, click All projects in the sidebar.
- Copy the entire URL in your browser address bar.
- Share this URL with the admin transferring the project.
- Log into your Figma team or organization in a web browser.
- Navigate to the team the project will move into. You can always move the project to a different team later.
- Copy the entire URL in your browser address bar.
- Share this URL with the admin transferring the project.
2. Send a transfer request
- In the file browser, navigate to the project you want to transfer.
- Click the down arrow next to the project name and select Send a copy.
- Review the information in the modal and press Next.
- Enter the destination URL and email address of your contact at the other organization and press Send.
Note: If you’re transferring a project to a company on the Organization or Enterprise plan, your contact must be an organization admin.
We’ll send an email to your contact so they can accept the transfer, and we’ll send you an email once the transfer is complete.
3. Accept a transfer request
When someone sends you a transfer request, Figma will send you an email asking you to review and accept the transfer.
It takes around 5 minutes to move the project between companies. Members of the project won’t be able to use certain features of Figma during this time, like sharing the project or accessing some of its files. We recommend accepting the transfer at a time that will cause minimal disruption to members of the project.
Once the transfer is complete, you can find the project by navigating to it in the file browser.
Transfer a team
When you transfer a team, all its projects and files will move to the recipient’s organization.
When accepting the transfer, the recipient can choose whether to keep or remove access for everyone from the sending team or organization.
There are three steps to transfer a team:
- The recipient provides a URL for the destination organization
- The sender makes a transfer request
- The recipient accepts the transfer request
1. Get the URL for the destination organization
Before you can move a team, the recipient needs to choose a location for it.
An admin at the receiving organization will need to provide the sender with a destination URL. This tells Figma where the resources should go.
- Log in to your organization in a web browser.
- From the file browser, click All teams or All workspaces.
- Copy the entire URL in your browser address bar.
- Send this URL to the admin sending the team.
Note: Any team you transfer between two Figma organizations will keep its access settings, whether that's open to anyone in the organization, or Only those invited.
2. Send a transfer request
Note: If you are on the Professional plan and transfer your paid team, the receiving organization will get a pro-rated credit for any remaining time on your plan. This credit gets applied at the organization's first renewal after the transfer is complete. For example: Let's say you transfer your team halfway through a monthly billing period. When the transfer is complete, we'll give the receiving organization a credit to cover the second half of that month.
- In the file browser, click All Projects in the left sidebar.
- Click the down arrow next to the team name and select View settings.
- In the Transfer section, click Transfer team to an external organization.
- Review the information in the modal and press Next.
- Enter the destination URL and email address of your contact at the other organization and press Request transfer.
- From the file browser, click Admin in the left sidebar.
- Click the Teams tab and select to the team you’d like to transfer.
- Click Transfer team.
- Review the information in the modal and press Next.
- Enter the destination URL and email address of your contact at the other organization and press Request transfer.
We’ll email your contact and other organization admins in the receiving organization so they can accept the transfer. You will receive an email when the transfer is complete.
Caution: If you transfer a file that contains a published library, other files in your organization won’t receive updates from this library after the transfer is complete. We recommend keeping libraries and their files together.
3. Accept a transfer request
When someone sends a request to transfer a team, Figma will email the designated contact and all organization admins asking them to review and accept the transfer.
Everyone from the sending party with a role on the team will get an account in your organization. This may add more paid seats to your subscription.
You can avoid paying for any seats from the sending party by making sure your default seat type is set to viewer-restricted or by manually adjusting everyone’s seats after the transfer is complete.
After you accept, you can find the team by navigating to it in the file browser.
Caution: When you accept a transfer request, it takes around 5 minutes to move the team between companies. Members of the team won’t be able to use certain features of Figma during this time, like sharing projects or accessing some of the files in the team. We recommend accepting the transfer at a time that will cause minimal disruption to members of the team.
Additional considerations for admins on the Enterprise plan:
- If there are guests in the team being transferred and you have restricted guest access, these guests won’t transfer with the team.
- If you have workspaces enabled, you will need to manually assign the team to a workspace after the transfer is complete.