Migrate from load testing tools

If you have existing load tests in another tool, you can bring them into Postman instead of rebuilding them. Postman imports the test as a collection and a suggested performance run configuration, so you can run it as a performance test. You can import JMeter test plans and Gatling simulations.

What gets imported

When Postman imports a load test, it creates a collection that maps the source’s requests, authorization, variables, test data, and assertions. Where the source defines load settings, Postman can also suggest a performance run configuration. It reports anything that doesn’t carry over, such as think-time pauses and non-HTTP steps, and flags any scripts for you to review.

Import with your coding agent

If you use a coding agent, install the Postman plugin and ask it to migrate your load test. The plugin’s performance-testing skill imports JMeter test plans and Gatling simulations, preparing a collection, a performance run configuration, and an import report for you to review and run. Gatling is available only through the coding agent, not the Postman CLI. For more tasks you can give your agent, see Work with Postman from your agent.

Import from the command line

Use the Postman CLI to import a JMeter test plan. The following command imports a .jmx file as a collection in your local project:

postman collection import ./load-test.jmx --name "Load test"

To create the collection in a Postman Cloud workspace instead of locally, add the -w, --workspace option with your workspace ID. For the full behavior and options, see postman collection import.