Migrate from other API clients

If you’re moving to Postman from another API client, you can bring your existing requests, collections, and environments with you instead of rebuilding them from scratch.

Use the Migrate to Postman wizard to migrate projects from SoapUI, Hoppscotch, Insomnia, and Thunder Client. To migrate a ReadyAPI project, see ReadyAPI.

SoapUI

1. If needed, unzip the exported SoapUI project file.
2. Access your workspace, then click Use resources or import > Import tab > Migrate to Postman > SoapUI.
3. Click files or folder, then select the exported project file you want to import.
4. Click Start Migration.

If the Start Migration button isn’t enabled, make sure you’ve selected a valid SoapUI project file.

Hoppscotch

1. In Hoppscotch, click the more icon next to the collection or environment you want to export, then click Export.
2. Select a save location and click Save.
3. Access your workspace in Postman, then click Use resources or import > Import tab > Migrate to Postman > Other.
4. Select the exported file or folder, then click Start Migration.

Insomnia

1. In Insomnia, export your data. Insomnia can export all data, or individual documents, collections, and requests. See the Insomnia documentation for details.
2. Access your workspace in Postman, then click Use resources or import > Import tab > Migrate to Postman > Other.
3. Choose one of the following:
   • Detect and import data from default directory — Postman automatically detects data in the default Insomnia directory. If Postman finds data in multiple directories, select the data you want to import. This option is only available in the Postman desktop app.
   • Select data to migrate — Click files or folder, then select the files or folder you want to import.
4. Click Start Migration. A message appears in the footer when migration is complete.

If the Start Migration button isn’t enabled, make sure you’ve selected a valid Insomnia file.

Thunder Client

1. In the Thunder Client extension in VS Code, click next to the collection or environment you want to export, then click Export.
2. Select a save location and click Save.
3. Access your workspace, then click Use resources or import > Import tab > Migrate to Postman > Other.
4. Choose one of the following:
   • Detect and import data from default directory — Postman automatically detects data in the default Thunder Client directory. If Postman finds data in multiple directories, select the data you want to import. This option is only available in the Postman desktop app.
   • Select data to migrate — Click files or folder, then select the files or folder you want to import.
5. Click Start Migration. A message appears in the footer when migration is complete.

If the Start Migration button isn’t enabled, make sure you’ve selected a valid Thunder Client file.

ReadyAPI

To migrate a ReadyAPI project, you can call a conversion API that accepts a ReadyAPI project file and uploads the resulting collection directly to a Postman workspace.

To learn more, see Migrate your ReadyAPI projects to Postman without rebuilding your tests.

Prerequisites

• A SoapUI/ReadyAPI project exported as an XML file (for example, REST Project.xml).
• Access to your Partner Workspace, created and shared by your Postman migration team, containing the Postman Migration API.
• Postman API key. Store the key in a local environment variable, then configure the collection’s Authorization tab to reference that variable.
• A Postman workspace ID to upload the converted collection into.

Export the source ReadyAPI project

Before migrating, your source project in ReadyAPI should contain the following elements:

• A REST or SOAP project with an API.
• A test suite.
• Assertions.

To export the project for migration, right-click the project in the ReadyAPI navigator and select Export, saving it as an XML file (for example, REST Project.xml).

Open the migration request in Postman

In the Postman Migration API collection, open Convert ReadyAPI XML to Postman JSON, a POST request to {{baseUrl}}/convert.

The request body uses form-data with two fields:

Attach the exported project file and set the workspace ID

1. In the file field, upload the exported REST Project.xml file.
2. In the workspaceId field, paste the target workspace’s ID.

Confirm your environment is selected correctly before proceeding.

Send the request

Click Send. The request runs against the migration service and returns a 200 OK response.

Review the JSON response

The raw JSON response includes a top-level summary and a results array with one entry per converted file:

{
  "batchId": "<batch-id>",
  "status": "succeeded",
  "totalFiles": 1,
  "successCount": 1,
  "failCount": 0,
  "results": [
    {
      "conversionId": "<conversion-id>",
      "fileName": "REST Project.xml",
      "fileSizeMB": 0.1,
      "status": "succeeded",
      "manualAttentionRequired": null,
      "processingTime": 7.4,
      "metrics": {
        "collectionName": "REST Project",
        "folders": 13,
        "apiRequests": 11,
        "testCases": 3,
        "testRequests": 7,
        "totalRequests": 18,
        "outputFiles": 2,
        "groovyScripts": 7,
        "assertions": 41,
        "environments": 1
      },
      "workspaceUpload": {
        "success": true,
        "collectionId": "<collection-id>",
        "collectionUid": "<collection-uid>",
        "collectionName": "REST Project",
        "environments": [],
        "environmentCount": 0
      }
    }
  ]
}

View the conversion summary

Instead of reading raw JSON, switch to the Visualization tab on the response to see a rendered dashboard of the conversion and observe the following:

• Batch summary — Total files, successful conversions, failed conversions.
• Per-file conversion results — Folders, total requests, output files, Groovy scripts, assertions, environments, and test cases.
• Request breakdown — API and test requests.
• Upload details — Collection name, workspace ID, upload status, and environments uploaded.
• Errors.
• Warnings.

Verify the migrated collection in the workspace

After the upload succeeds, a new REST Project collection appears in the Postman sidebar. Expand it to confirm the structure mirrors the original ReadyAPI project.

Inspect a migrated test request and its converted scripts

1. Open Get Products under REST Project > Tests > Test Suite > Test Case - Test Assertions to confirm the request matches the original ReadyAPI test step.
2. Switch to the Scripts > Post-response tab to see that the original ReadyAPI assertions have been converted into Postman pm.test() JavaScript blocks.