Move your Postman workspace to HTTP Titan in one afternoon.
Export your collections, import them in one step, and pick up scripting and tests with little to no rewrite — the pm.* API works in Titan too.
Six steps, no rewrite required.
What actually happens when you move a Postman workspace over — not a marketing summary, the real steps.
- 1
Export your collections
In Postman, export each collection as a Collection v2.1 JSON file (Collection → ⋯ → Export). Environments export the same way from the Environments panel.
- 2
Import into HTTP Titan
Create a workspace, then use Import → Postman Collection and select the exported JSON. Requests, folders, headers, auth, and query params carry over as-is.
- 3
Import your environments
Repeat with the exported environment JSON. Variable names and values map directly — secret-flagged variables come in masked.
- 4
Check your auth configuration
Bearer tokens, API keys, and Basic auth import automatically into the structured Auth tab. OAuth 2.0 (client_credentials grant) needs its client ID/secret re-entered — Postman does not export secrets in plaintext.
- 5
Bring over your test scripts
Pre-request and test scripts import as-is. HTTP Titan's scripting engine includes a pm.*-compatible layer (pm.test, pm.expect, pm.environment, pm.response), so most Postman scripts run with little to no changes.
- 6
Invite your team
Add teammates to the workspace with a role (Owner/Editor/Viewer) and a shareable invite link — everyone sees the same requests, environments, and results live, no separate export/import per person.
Migrating from Postman, answered.
The questions that come up most during an actual migration.
Will my Postman test scripts break?
Most don't. HTTP Titan's scripting engine ships a pm.*-compatible layer alongside its own titan.* API, so pm.test()/pm.expect()-style scripts run with little to no changes. Scripts using Postman-specific APIs outside the pm.* surface may need small edits.
Do I lose my request history?
Postman's collection export format doesn't include send history, so that doesn't carry over — only the collections and environments themselves (requests, folders, auth, scripts, variables).
Can I migrate one collection at a time instead of the whole workspace?
Yes — import is per-collection, so teams commonly migrate one collection first to validate the workflow before moving the rest.
What about OAuth 2.0 client secrets?
Postman's export never includes secrets in plaintext, so you'll re-enter the client ID/secret for any OAuth 2.0 (client_credentials) requests after import — everything else in the Auth tab carries over automatically.
Talk to us.
Tell us about your team and what you're building. We'll get back to you.