Postman to Tiger
Migration Guide

Step-by-step migration

Follow each step in order. The whole migration takes about 30 minutes for a typical team with a handful of collections.

1. 1

   Export your Postman collection (Collection v2.1 JSON)

   Open Postman and locate the collection you want to migrate in the left sidebar. Right-click the collection name and choose Export. In the dialog, select Collection v2.1 (Recommended) and click Export. Save the .json file to a convenient location on your machine.

   Repeat for each collection you want to bring over. If you have environment definitions, export those separately from Environments in the left sidebar (you will not import them directly; you will re-enter the values in step 4, but having them open for reference saves time).

   v2.0 works too. Tiger accepts both Postman Collection v2.0 and v2.1 formats. v2.1 is preferred because it preserves more metadata.
2. 2

   Download Tiger

   Grab the installer for your platform from the Tiger download page. Available for macOS (Apple Silicon and Intel) and Windows (installer and portable).

   macOS gatekeeper note. These are early preview builds and are not yet code-signed. On macOS, right-click the app and choose Open the first time to bypass the Gatekeeper warning.

   Tiger requires no account creation and no license key. Launch it once to confirm it starts.

3. 3

   Import in Tiger via Import / Export > Postman

   In Tiger, look for the Import / Export option in the sidebar or the File menu. Choose Postman as the source format. Drop your exported .json file onto the import dialog, or click Browse and navigate to it.

   Tiger parses the collection and recreates the folder structure, request names, HTTP methods, headers, query parameters, request bodies and variable references. Large collections with hundreds of requests import in seconds.

   payments/create-invoice.tiger

   meta {
     name: Create invoice
     method: POST
   }
   
   url {
     {{baseUrl}}/v1/invoices
   }
   
   headers {
     Authorization: Bearer {{accessToken}}
     Content-Type: application/json
   }
   
   // Body and query params follow...

   Variable references like {{baseUrl}} and {{accessToken}} are preserved exactly as they were in Postman. You fill in the actual values in the next step.

4. 4

   Re-enter environment values and auth credentials

   Tiger does not import environment values from Postman (secrets and tokens should not travel in an exported JSON anyway). Open Settings > Environments in Tiger and create an environment for each context you need, for example staging and production.

   environments/staging.tiger

   meta {
     name: staging
   }
   
   vars {
     baseUrl: https://api.staging.acme.dev
     idp: https://id.staging.acme.dev
     clientId: acme-ci
     ~clientSecret: kept-out-of-git
   }

   For OAuth 2.0 client credentials flows, Tiger has a built-in auth exchange. Set the token URL, client ID and client secret and Tiger fetches and refreshes the token automatically. For Bearer or API key auth, paste the value into the corresponding environment variable.

   Prefix a variable with ~ to mark it as secret. Tiger stores it separately from the main collection files so you can safely add the environment files to Git without leaking credentials.
5. 5

   Commit your collection to Git

   Tiger stores each request as a plain .tiger text file. Your imported collection is a folder on disk. Add that folder to your team repository:

   terminal

   # From your project root
   git add api-collections/
   git commit -m "import: add payments collection from Postman"
   git push

   From now on, adding a request is a commit, changing an endpoint is a diff, and reviewing auth changes is a pull request. Engineers joining the team get everything with git clone.

What carries over and what to redo

The importer is accurate but honest: structural data migrates automatically; secret values are entered once in Tiger.

Troubleshooting

• FIX
  Import dialog rejects my file. Confirm you exported as Collection v2.1 or v2.0 JSON, not a Postman "workspace" or team export. The file should be a single .json whose top-level key is "info" with a "schema" field.
• FIX
  Variable references show as literal text after import. You need to select an active environment. Open Settings > Environments, confirm your environment has the matching variable names, and set it as active for the collection.
• FIX
  OAuth flow does not complete. Check that your authorization server allows the redirect URI Tiger registers. For client credentials flows there is no redirect; confirm the token URL and client credentials are entered in the environment, not hard-coded in the request.
• FIX
  Requests that used Postman pre-request scripts no longer work. Common cases like dynamic timestamp headers or UUID generation are covered by Tiger's built-in {{$timestamp}} and {{$uuid}} dynamic variables. For custom token-injection logic, use Tiger's OAuth auth configuration instead of a script.
• FIX
  SSL certificate errors on internal services. Go to Settings and disable SSL verification for development environments, or import your internal CA bundle under Settings > Certificates.
• FIX
  macOS "app is damaged" message. These are unsigned preview builds. Right-click the app in Finder and choose Open, then confirm. You only need to do this once.

More resources

Read the Tiger vs Postman full comparison for a detailed feature-by-feature breakdown, or head back to the Tiger homepage to download the app. Considering other alternatives? See the Postman alternatives overview or the Tiger as an MCP API client guide.