Postman Lost My Collections

How to fix it

Try these in order — the most common fix is first.

1. 1. Check workspaces and account

   1. Switch via Workspaces in the header and confirm you are signed into the right account
   Did this fix it? Yes No

2. 2. Recover deleted collections

   1. Open the Trash / recover collection option; recovery lasts 1 day on Free, 30 days on Solo, 90 days on Team
   Did this fix it? Yes No

3. 3. Migrate local data

   1. Settings > Data > Scratch Pad Data > Migrate Data if the option exists, or import exported files
   Did this fix it? Yes No

4. 4. Export regularly

   1. Export collections to JSON or Git so a sync bug or downgrade cannot remove your only copy
   Did this fix it? Yes No

Symptoms

Collections or environments vanish after an update, sign-out, plan downgrade or when switching accounts.

Why it happens

• Signed into a different account or workspace
• Data was in the Scratch Pad or lightweight client and not migrated
• Collection deleted (recovery window by plan)
• Team downgraded to Free and lost shared workspace access

This guide also covers

• postman lost collections
• postman collections disappeared
• postman data lost after update

Other Postman errors

• Postman Could Not Get Response Error
• Postman Error: connect ECONNREFUSED
• Postman SSL Error: Self Signed Certificate
• Postman CORS Error in Web App
• Postman Scratch Pad Removed: Login Required to Save
• Postman Collection Runner Limit: You've Exhausted All Available Runs
• Postman Collections Not Syncing
• Postman Slow and High Memory or CPU Usage