In 2025, an API Client isn't a novel tool (which is why it's primed to be reinvented) so nearly all of the 1.5 million Bruno users have transitioned from another product. The vast majority of those users are migrating away from Postman due to product bloat, security risks, and extremely difficult to justify cost/ROI. Because of this, we've focused on making the migration from Postman to Bruno as painless as possible.
This post walks through how to make your move to Bruno easy and put your old tool in the rearview mirror. Of course, if you're looking for assistance with a migration - whether you have 100 or 10,000 collections - just reach out to support@usebruno.com and we're happy to help.
Export Your Data
It goes without saying, but step 1 will be exporting your data from Postman. You have two options in this regard:
Although this sounds like an extremely tedious process, it's actually not the worst idea. Most companies we work with have a huge amount of collections that are no longer relevant. Sometimes they're just outdated due to sitting outside of the core developer environment (Git), or they're often duplicates caused by the lack of ability to locate collections inside Team Workspaces that simply aren't designed for scaled usage.
Whatever the case may be, your migration provides an opportunity to clean up the inventory of collections you may have. Since you're moving to a superior storage and versioning process via native Git it's nice to start with a clean slate. However, you can always perform this cleanup later if you just want to move to Bruno as soon as possible (which is also pretty common).
It's a bit of a maze, but you'll want to hit the ellipsis next to your collection, navigate to more, and then select export:
After that, you can choose either collection format, but we'd recommend v2.1
Then all you need to do is select a place where you want the file downloaded.
You'll want to open your environment(s), select the ellipsis again, and then export.
Again, just select the destination of your save location and you're done!
Importing a Postman Data Dump is only available in Bruno Ultimate Edition
They've also made this one a bit tricky to find. You'll want to navigate to your profile by clicking on your avatar and then go to Settings:
A browser will open, and then you can select Export Data.
If you're moving to Bruno for security reasons, we'd strongly suggest coming back here after your migration and selecting 'Delete Account'. This will (hopefully) ensure that all of your request/response/secrets that have been stored in the cloud are removed.
After you've done this, you should receive an email with a JSON file including all of your collections and environments. Same thing here - select a place for it to be saved locally.
Import Your Data
Alright, now we're on to the good stuff - let's import your data to Bruno! Again, you have the same two options here:
In Bruno, click the ellipsis and select "Import Collection"
Then select "Postman Collection"
Select the JSON file you exported from Postman, where you want your Bruno collection stored, and you're done!
The Bruno collection will automatically open:
We automatically translate scripts from Postman's syntax to Bruno's, but there may be some cases where the fidelity isn't 100%. We do recommend doing a quick review of your script functionality by performing a collection run.
In Bruno, head to Environments and select Configure.
You'll be prompted to either create or import, in this example we'd select Import Environment.
Select the environment you exported, and boom. Done.
In Bruno, click the ellipsis and select "Import Collection"
Then select "Postman Data Export"
Select the zip file you previously saved. You will now be given a list of all collections that are within that zip.
After selecting import, you'll see all the collections open in Bruno and you'll have a full list of environments.
Considerations
As mentioned, Bruno will automatically attempt to convert your Postman scripts into Bruno's syntax. For the typical collection and script, you should have full parity. That said, there are instances where you may have complex, or more commonly - older, scripts that may need some manual love. The bright side is that this is a one time exercise and you'll be moving to a superior product :).
Of course, we are here to help with any issues or questions you might have - no matter how big or small. Reach out to support@usebruno.com if you need help, want to confirm anything with us, or even just say hi. Our typical response time on a ticket is under 3 hours so we'll get back to you quickly.