Yes, sir, I have the Fix option, but it only helped me resolve 3 collections and the environment. There are 17 collections left, as shown in the image. The Fix option no longer helps, and neither did the AI assistant.
I am also having difficulty with my collection in V12.
I’ve a message “Postman no longer supports JSON for collections and environments in Local Mode. Upgrade these files to v3 YAML format to continue working with them.” with the option to upgrade, and doing that fails without ANY indication. Everything was working before the upgrade, but now I cannot get to my collection.
If I use Postman Cloud instead of local, the same collection works. If I use Local Mode and disconnect from Git, my collection works fine. 1. I do not want to use Postman Cloud. 2. I NEED to be connected to Git.
Why is there no proper error messages for failing for convert from v2 JSON to v3 YAML? Why the hard cut over with no backwards support? This is a HUGE disruption for my team, and is setting us back.
Not to mention I had to start a WHOLE NEW WORKSPACE just to convert my API to Spec Hub?
Hey everyone,
I’m an engineer on the team that worked on V3 collections and their integration with the local filesystem.
We shipped support for importing v2.1 JSONs into local mode yesterday, and it’s now available in v12.0.4 of the desktop app. We’ve also added a few modals and popups to help ensure the required migration step is easier to notice and complete.
To make migration from v2.1 to v3 smoother, we introduced converters to automatically migrate v2.1 collections to v3. While these worked well in most of our internal testing, it’s clear from this discussion that there are some edge cases where the conversion may fail.
To help us investigate and fix these issues, I’d greatly appreciate it if you could share the collection JSONs that are failing during conversion. You’re welcome to post them in this discussion or email them to us at [email protected]. If you’re not comfortable sharing the full collection, a minimal reproducible JSON that demonstrates the issue would also be extremely helpful.
Thank you so much for your time and for helping us improve this experience 
Just to respond to this point, were you trying to migrate an already git linked API to Spec Hub?
If the API was not git linked, you would have been given the option the select an existing Workspace.
Yes, the API was already git-linked and I was forced to map the API to a new workspace to migrate it to Spec Hub.
Additionally, I cannot attach the collection or email it, as it contains proprietary information. My issue is that trying to use the “Upgrade to v3” button simply fails silently. No popups, no messages, no errors. Where can I see its execution and hopefully see some output of the failures to make a small reproduceable collection?
Hey @thoma01
You can find the error logs from the View menu.
Here’s a doc to help you guide on the process for your specific OS: https://support.postman.com/hc/en-us/articles/360025298633-How-to-get-logs-from-the-Postman-Desktop-app
Logs were no help. Error message was generic, no details about what failed the conversion. I used the AI in Postman to try converting from json to yaml. It may have got 80% of the way there, but the formatting is wrong, so Postman is not recognizing the collection in the UI. I started a new collection, and even with just 1 folder from my original collection, it breaks the formatting, and disappears from the UI.
At this rate, I will be forced to start a new collection altogether and manually recreate each folder, request, documentation, example, JUST to have the proper v3 YAML format. This is making me largely consider moving OFF of Postman entirely.
Even after solving these issues, are you going to still support export to json or is that going away? We have automation tools that do checks and we cannot upgrade these all instantaneously, and we could be ground to a halt in the meantime. We have too many Postman files to upgrade all at once and strict control processes on doing updates. This would have to go through a non-dev team. It’d be a nightmare.
In the past, you always supported the previous collection version for export and now you’re changing that approach. This is not something anyone expected.
If we have to go and update all this in a fire drill, we’re likely to just migrate away, a lot of developers, to straight curl or something.
Can you share some more information on your environment? Do you use newman or the Postman CLI to run those check? If so, these processes will continue to work unchanged, as will processes based on the json files.
There were some issues on launch around v11 git integration to v12 which have now been resolved. If you are still facing issues, any addition error messages would be helpful so we can ensure we solve your problem.
@quinton-wall we use Newman with Postman json
Hey everyone,
Just checking in that we have identified and fixed a couple of bugs that we had observed and were reported by our users. The latest set of bug fixes are available in v12.1.3.
I would recommend updating to the latest version and trying the local mode again. Let us know if you reach any blockers or face any issues. Would be happy to help out here.
From what we’ve observed, the errors in migration usually stem from the v2.1 collection JSON file having diverged from the main schema primarily through edits outside of Postman. While we are working actively to make the transformation more lenient, we’ve observed better results when fixing the v2.1 collection JSONs using LLMs before the conversion rather than getting it to create the YAML files directly. To this effect, we’ve also added convenient entry points that will detect if the 2.1 collection upgrade process to v3 failed and let you fix the 2.1 JSON files before attempting to try again.