Transferring Airtable bases between workspaces
Last updated: October 19, 2026
This article details how to move bases between workspaces and the associated permissions.
Plan availability | All plan types with options to restrict for paid plan workspaces |
Permissions |
|
Platform(s) | Web/Browser, Mac app, and Windows app |
Check out our Transferring workspaces, bases, and interfaces ownership article if you’re planning to leave your company or organization.
What should I consider before moving a base from one workspace to another?
Moving bases from one workspace to another can change which collaborators have access and the permission levels of users with access.
Moving bases between workspaces impacts:
Workspace collaborators from the original workspace, who have also been added to the new workspace, can access the moved base at their permission level.
Workspace collaborators from the original workspace who are not members of the new workspace will lose base access.
Base collaborators with access to the base moved from one workspace to another but are not workspace collaborators retain access to the moved base at their same permission level.
Base collaborators who originally had access to the base moved from one workspace to another—who also have access to the new workspace as workspace collaborators—are no longer base collaborators and are updated to workspace collaborators at their specified permission level.
Moving bases from one workspace to another
Open your Airtable home screen.
Locate the base you want to move to a new workspace.
Click the ... icon to the right of your base’s name.
Click Move base.
Click the ˅ under the “Choose workspace” section, then select your preferred workspace.
Click Move base.
A new page opens, confirming your base’s new workspace.
Workspace sharing permissions
We recommend contacting workspace owners to have them help move bases to your preferred workspace(s) .
Owners can move bases between workspaces if they are owners of both workspaces.
Creators can move bases between workspaces, if there are no workspace restrictions enabled.
For workspaces that do have sharing restrictions, creators can move bases between workspaces only if:
Restrict adding new collaborators is disabled for Team, Business, and Enterprise Scale workspaces.
Prevent creation of new share links is disabled for Business and Enterprise Scale workspaces.
If the “Prevent creation of new share links” setting is enabled, and any views in the base have a share link, creators can’t move the base to the destination workspace on Enterprise Scale workspaces.
Troubleshooting moving a base
The "Move base" option doesn't appear - The Move base option is only available from a base's menu on your Airtable home screen. Depending on how the base appears on your home screen, the option may be labeled Move instead of Move base. If you don't see it, check the following:
Make sure you're on your Airtable home screen and logged in under the correct account. The option isn't available from inside an open base.
Make sure you're using the base's menu (the ... icon to the right of the base's name). The menu next to a workspace's name manages the workspace itself, and the base's sharing options manage who has access. Neither includes an option to move a base.
Check your permissions in the base's current workspace. You need Creator or Owner permissions to move a base. Editors, Commenters, and Read-only collaborators can't move bases.
Check the current workspace's sharing restrictions. If the workspace has any sharing restrictions turned on, only workspace owners can move bases out of it. Ask a workspace owner to move the base for you.
Finish any guided tutorial in progress in the base. The option is hidden until the tutorial is complete.
The destination workspace isn't listed, or the move is blocked - The "Choose workspace" dropdown only lists workspaces where you have Creator or Owner permissions. If the workspace you want isn't listed, ask an owner of that workspace to give you Creator permissions or to move the base for you. If you aren't an owner of the destination workspace, its sharing restrictions can also block the move:
If the destination workspace restricts adding new collaborators, you can't move in a base that has base collaborators or pending base invites. Remove them first, or ask a destination workspace owner to move the base.
If the destination workspace restricts creating new share links, you can't move in a base that has active shared view links. Shared forms don't block the move. Remove the other share links first, or ask a destination workspace owner to move the base.
FAQs
Does moving a source base to a different workspace break its sync connection to a base in another workspace?
No. Moving a source base to a different workspace will not break existing syncs. Airtable syncs are built on shared view links that are tied to the base's ID, and a base retains its ID when moved between workspaces.
Things to consider before moving bases:
Collaborator access: If the person who originally configured the sync has access only at the workspace level (not the base level), moving the source base out of that workspace will remove their access — which could cause the sync to stop functioning. Ensure that user has base-level access to the source base, or is a member of the destination workspace, before moving.
Sync activity display: Collaborators in the destination base's workspace who don't have access to the new workspace where the source base now lives may see incomplete information in the Sync activity panel. The sync itself will continue to run; this is a display-only limitation.
Do my syncs break If I move a sync source base to a different workspace within the same organization?
No. Moving a source base between workspaces in the same organization does not break existing syncs. Airtable syncs are built on shared view links tied to the base's ID, and a base keeps its ID when moved, so the connections persist. The main thing to manage is collaborator access: if the user who set up a sync had access only at the workspace level (not base level), moving the base out of that workspace can remove their access and stop the sync. Before moving, ensure that user has base-level access to the source base, or is a member of the destination workspace.
How does moving a base affect API usage and integrations?
API call usage is counted per workspace. After you move a base, its API calls count toward the destination workspace's monthly allowance, including calls made to the base earlier in the month, before the move. Usage totals in workspace settings can take up to a day to reflect the move.
API limits are enforced using the plan of the workspace the base is in now. If you move a base into a Free plan workspace that's over its monthly API allowance, API requests to the moved base can be blocked until the monthly counter resets.
A base keeps its base ID when it moves, so integrations that connect to the base by its ID keep working, as long as the account or token the integration uses still has access to the base in its new workspace.
Learn more in our Managing API call limits in Airtable article.