Migrate from Postman to Cruss

In Postman, open the collection you want to migrate, select the collection menu, choose Export, select Collection v2.1 and save the JSON file. Repeat for each collection you want to move to Cruss.

Create a Cruss account or sign in to an existing one. An account lets you keep your API work in a cloud workspace and collaborate with your team, and it is required to import collections.

Create a workspace for the API project you are migrating. A workspace gives your team a shared environment for collections, requests, environments and API documentation.

Create a collection in your workspace, open its menu and choose Import from Postman, then paste the contents of your Collection v2.1 JSON file. Cruss imports each request's name, method, URL, headers and body. Requests inside Postman folders are added to the collection you import into, and authentication, scripts and collection variables are not imported, so review the imported requests before continuing.

Recreate or configure the environments used by your collection in Cruss. Add the required variables and reference them using Cruss environment syntax: double braces around a name made of letters, numbers and underscores.

# Postman and Cruss: double braces
{{baseUrl}}/users
{{authToken}}

# Cruss allows letters, digits, _
# {{api-key}}    → {{api_key}}
# {{auth.token}} → {{auth_token}}

Authentication is not included in the import, so set it on each request that needs it. Cruss supports Bearer token, Basic auth and API key authentication, and Bearer tokens and API key values can reference environment variables such as {{authToken}}. Send representative requests to confirm credentials and variables resolve correctly before sharing the workspace with your team.

Invite the developers who work on the API and give them the appropriate workspace access: admins manage members, editors create and edit collections and requests, and viewers have read-only access. Your team can then work from the same collections, environments and API workflows.

Use Cruss alongside your existing development workflow, including the Cruss VS Code extension when you want to work with API requests directly from your editor.

code --install-extension HyacinthOkeke.cruss