Team migration is required when you merge one or more Postman teams into a single (typically company-authorized) account. There are several reasons for having a company-authorized Postman account (or team) including security, the ability for a company to better oversee its intellectual property, and to give users the benefit of a robust paid plan.
Team migration can occur in different ways depending on your needs and preferred outcomes.
You can choose either centralized or distributed migration to export your team data.
As a precautionary measure prior to migrating data, Admins and team members are strongly encouraged to perform a JSON data dump backup through a bulk export.
Centralized migration must be performed by a Team Admin.
With centralized migration, you will export a large JSON file of collections, environments, globals, and header presets.
You can bulk export your personal workspaces and the workspaces of any teams you have joined.
Choose centralized migration if the following conditions apply:
Don't choose centralized migration if your organization relies on the following:
See performing centralized migration to choose this option.
You can carry out distributed migration with any type of Postman account.
You can export your personal workspace and shared workspaces for any teams you have joined, or you can choose to export data from a specific workspace. See exporting data for more information.
If you have an account and aren't part of a team yet, but want to keep an independent workspace after joining one, see Joining a team. When migrating company data to an authorized team, you can export specific data or export a dump of all data.
If you have an account and want to deactivate it and join an authorized team, you can accept the team invite and choose to transfer your personal Postman data to your new team.
Choose distributed migration if the following conditions apply:
Recreating mocks, monitors, and documentation on the new team may be carried out by those who are responsible for maintaining it.
Don't choose distributed migration if your organization is unable to do the following:
See performing distributed migration to choose this option.
Data from team workspaces you haven't joined won't be present in the export.
By default, the person who imports a collection or environment is automatically assigned the Editor role (learn more about roles). Everyone else on the team will be assigned as Viewer.
All collections included in the data dump will be imported into your selected workspace.
By default, the person who imports a collection or environment is automatically assigned the Editor role (learn more about roles). Everyone else on the team will be assigned as a Viewer.
If you change your team email to a non-company domain email (for example, Gmail or Yahoo), your original team will continue indefinitely. You can keep an account with your current data and use a work email for a work account. Keeping both accounts in use can help when you migrate data.
Keep in mind items that will need to be recreated (such as monitors and mocks).
I'm on a free account, what happens to my personal collections when I join a team?
If you're an individual Postman user and join a team, you can choose to transfer your personal workspaces and the data within them to the team or keep them separate. In certain cases, your personal workspaces and the data within them automatically transfer when you join a team:
For more information, see Joining a team.
If you experience any issues when joining a new team, contact Postman support.
Can I be on two teams at once?
Yes, each account can be on multiple Postman teams at a time.
Will my monitors / mocks transfer over?
No, you will need to recreate any monitors and mocks in your new team.
What data is exported in a large JSON file data-dump?
All collections in your personal workspace and any workspaces that you have joined, in addition to environments, globals, and header presets, are included when you export a data-dump.
What data doesn't get exported?
You will need to reassign roles (workspace, collection, and environment level), recreate workspaces, recreate monitors, recreate mocks, re-import API schemas, and republish documentation from your new team pages.
What happens to published documentation from my previous team?
Your documentation links will break since the previous team is no longer active. New documentation URLs will need to be generated when collections are republished from your new team pages. If you are publishing to a custom domain, unpublish and remove the domain from your previous team to add it to your new team and republish.
What happens to the previous team once everyone leaves?
If it's a free team, the team is deleted after the last team member leaves the team. Previous users of the deleted team will no longer have access to the team's workspaces, including personal workspaces, or any elements in them. Users can export their Postman data prior to leaving the team to ensure it stays with them.
If it's a paid team, you must contact Postman support to cancel the plan subscription before you can leave the team.
After learning how to migrate data between teams, you can learn how to manage team roles and set up SSO:
Last modified: 2020/10/02