Collection Export
- Open Postman and select the collection you want to migrate.
- Click the
···menu, then chooseView more actions. - Click on
Export.


- In the dialog, select either
Collection v2orCollection v2.1, then clickExport.

- The collection downloads as a JSON file. Follow Importing Collections to bring it into Bruno.
Export Data Dump
You can export a data dump of all your collections and environments in Postman, then import that dump into Bruno.Export a data dump from Postman
To export a data dump ↗:- Select the settings icon in the header, then select
Settings. - Open the Data tab, then select
Request Data Export. - Select
Export Data, then choose the data types you want (collections, environments, or both). - Select
Request Data Export.
Import the data dump into Bruno
- Open the import menu and select
Import Collections. - Select the zip file where the export was saved.
- Review the list of collections. All are selected by default; uncheck any you want to omit.
- Choose a location for the collections and press
Import.

Bruno automatically translates common Postman script APIs (such as
pm.test, pm.environment, pm.globals, pm.collectionVariables, and pm.response) to their Bruno equivalents during import.See the Scripts Translator page for the full list of supported translations.npm packages used by Postman scripts
When you import a Postman collection, Bruno scans the scripts forpm.require() and require() calls and groups any external packages it finds into an Install packages prompt. You’ll see a dialog-box below after the import completes whenever the collection references packages that need attention.


require() at runtime.
If npm isn’t on your PATH, the install step fails with a clear error. Install Node.js/npm, then either retry from the prompt or run the suggested command manually.
Bulk imports queue one prompt per imported collection so you can review each one in turn.
Environment Import and Export
Environments in API clients are sets of variables that allow you to run requests against different server configurations (development, staging, production) without changing your request URLs.Exporting Environment from Postman
- Open Postman and locate the Environments section in the sidebar
- Find the environment you want to export
- Click on the three dots (…) next to the environment name
- Select Export from the dropdown menu

- Choose a location to save the JSON file and click Save
Importing Environment into Bruno
Importing Your First Environment
- Open Bruno
- Click on the Environments icon in the top-right corner
- Click on Configure environments
- You’ll see options to Create environment and Import environment

- Click on Import environment

- Select the Postman environment JSON file you exported
- The environment will be imported with all its variables
Adding to Existing Environments
- Open Bruno
- Click on the Environments icon in the top-right corner
- Click on Configure environments
- Look for the Import button at the left sidebar
- Click on Import environment

- Select the Postman environment JSON file you exported

- The environment will be added to your existing environments
Note - Bruno environment names and variables must only contain alphanumeric characters, ”-”, ”_”, ”.” and cannot start with a digit. Non-conforming characters (such as ”/”) will be converted to ”-”.
Postman allows variable values to be numbers, booleans, or objects, but Bruno stores all variable values as strings. During import, non-string values are automatically converted — for example,
5000 becomes "5000", true becomes "true", and objects are serialized as JSON strings.Preserve Postman Scripts
By default, Bruno translates Postman script APIs (such aspm.test and pm.environment) to their Bruno equivalents during import and export.
If you have complex scripting setups and want Bruno to leave scripts untouched, enable Preserve scripts. When this option is on:
- Scripts are kept verbatim as
pm.*during import. - Collection structure, requests, variables, and settings are still converted as usual during import.
- Scripts are converted to Bruno script APIs during export.
Enable Preserve scripts on import
- Click the + icon in the top-left sidebar and select Import Collection.
- Choose your Postman collection file and continue to the import dialog.
- Click Options, then expand Show Advanced Options.
- Turn on the Preserve scripts toggle (off by default).
- Click Import.
