Migrating from Postman to PreMan in Under 5 Minutes

If you've got a Postman workspace you want out of, this is the shortest path that doesn't lose anything. Budget about five minutes if your collection is under a few hundred requests.

1. Export your Postman collection

In Postman, right-click your collection. Pick Export. Choose Collection v2.1 format. Save the JSON file.

If you have environments, repeat the export from the Environments tab. You'll get one JSON per environment.

2. Open PreMan

Sign in or create an account. The first run drops you in a new workspace.

3. Import

Click Import in the top-right. Drag both files in. PreMan reads Postman's v2.1 schema natively, which means:

• Folder structure preserved
• Pre-request scripts converted
• Auth blocks (Bearer, Basic, OAuth2, API Key) carried over
• Variables remapped to PreMan environments
• Tests/post-response scripts imported (with notes on any unsupported APIs)

4. Verify auth

The one thing that doesn't survive an export is your secrets. API keys and OAuth tokens were stored locally in Postman; they're not in the JSON. Open each environment and refill the values. PreMan stores them encrypted at rest and never pushes them to the request log.

5. Run a request

Pick any GET. Hit Send. If you see the same response you saw in Postman, you're done.

What to do next

Your collection runs identically. The new things worth trying:

• Add an MCP server. Same workspace as your REST endpoints.
• Share a single request as a URL. Anyone on your team can rerun it.
• Hook PreMan into CI. Same collection runs as a pre-deploy gate.

Common gotchas

• Custom Postman scripts using pm.sendRequest import as warnings. Convert them to PreMan's flow.fetch (drop-in API).
• Visualize endpoints built with pm.visualizer don't carry over yet. Add them as PreMan dashboards instead.
• Newman CI configs need a one-liner change: swap newman run for preman run.

→ Start your import in PreMan