Migrate from Postman to Bruno

Export

1. 1

   Step 1

   Export one collection

   In Postman, export the collection as Collection v2 or Collection v2.1 JSON. Bruno's docs tell you to start there. Do the collection your team ran this week, not the archive.

2. 2

   Step 2

   Export the environment separately

   Secrets in an environment are not the collection file. Export the environment you need, and do not commit tokens into the git repo you are about to create.

3. 3

   Step 3

   Leave the data dump for later

   Bruno's docs say a full Postman data-export zip is an Ultimate Edition import. A free move is the collection JSON, not that zip.

Import

1. 1

   Step 1

   Import the collection

   In Bruno, use Import Collection and choose the JSON file. Bruno's migration doc walks through that button.

2. 2

   Step 2

   Decide what happens to scripts

   Bruno can translate common Postman script calls, and it also has a preserve-scripts option. Run the one request that has a test. Do not assume every pm.* call still passes.

3. 3

   Step 3

   Put the folder in git

   Bruno stores the collection as files. Commit the folder next to the API, without the environment file that holds secrets.

What breaks

• Monitors, mocks, and flows

  Scheduled monitors, mock servers, and Postman Flows are not a collection import. Rebuild the one check you actually page someone for, or leave it in Postman.

• Workspace permissions

  Postman roles do not become Bruno folders. Access is whoever can read the git repo.

• Script drift

  A translated test can still fail because the response shape changed, not because the import failed. Run the collection once and read the failures.