Migration steps
1
Export your Postman collection
In Postman, open your collection. Click the ⋯ menu → Export → Collection v2.1 → Export. Save the .json file to your computer. Repeat for each collection you want to migrate.
2
Create a Cruss account (optional)
Go to cruss.io/signup and create a free account. You can also use Cruss as a guest without an account — your collections will be stored locally in your browser. For team access, an account is required.
3
Create a workspace
After signing in, you are automatically in your personal workspace. To create a team workspace, click "New workspace" from the workspace selector at the top of the sidebar. Invite your team — there are no member limits.
4
Import your Postman collection
In the Cruss sidebar, right-click any collection (or the workspace root) and choose "Import from Postman". Paste the contents of your exported .json file. All requests, headers, body configs, and auth settings are imported automatically.
5
Recreate your environments
Postman environments export separately. In Cruss, open the environment selector (top bar) → "+ New" → add your environment name and variable key-value pairs. The same {{variableName}} syntax works in Cruss.
# Postman environment variable syntax
{{baseUrl}}/users
{{authToken}}
# Works identically in Cruss
{{baseUrl}}/users
{{authToken}}6
Verify auth configuration
Open each request and check the Auth tab. Cruss supports Bearer Token, Basic Auth, and API Key — the same types as Postman. If your tokens are stored in environment variables, they will resolve automatically.
7
Invite your team
Go to workspace Settings → Members → Invite by email. Team members get access to all collections in the workspace. Roles: admin (full control), editor (create/edit requests), viewer (read + send only).
8
Install the VS Code extension (optional)
Search "Cruss" in the VS Code Extensions marketplace. The extension gives you full request builder access inside VS Code with direct Node.js fetch — no CORS restrictions, works for localhost APIs without any setup.
code --install-extension Cruss-code.cruss
Frequently asked questions
Does Cruss support Postman Collection v2.1?
Yes. Cruss imports Postman Collection v2.1 JSON directly. Paste the contents of your exported file and all requests, folders, headers, and auth configs are recreated.
What about Postman environments?
Postman environments export as a separate JSON file. In Cruss, recreate them via the environment selector → "+ New". The variable syntax ({{variableName}}) is identical.
Can I export my Cruss collections back to Postman?
Yes. Right-click any collection → "Export as Postman JSON". The exported file imports cleanly into Postman.
Does Cruss have a Collection Runner?
Yes, and it is free. Right-click any collection → "Run collection". The runner supports request ordering, delays, iterations, and request chaining via extraction rules.
What about Postman monitors and mock servers?
Cruss does not have monitors or mock servers. It is focused on API testing and documentation. For monitoring, use a dedicated service like Better Uptime. For mocking, Mockoon or WireMock work well alongside Cruss.
Is there a limit on how many collections I can import?
No. You can import as many collections as you need. There are no limits on collections, requests, or workspace members.