> This page is for Postman Docs, version Latest (v12) (default).
> For other versions, use one of these documentation indexes:
> - Latest (v12) (default): https://learning.postman.com/latest-v-12/llms.txt
> - v11: https://learning.postman.com/v11/llms.txt

> For clean Markdown content of this page, append .md to this URL. For the complete documentation index, see https://learning.postman.com/llms.txt.

# Migrate from load testing tools

> Bring a load test from another tool, like JMeter or Gatling, into Postman as a collection you can run as a performance test.

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](/docs/use/use-collections/overview/) and a suggested performance run configuration, so you can run it as a [performance test](/docs/tests-and-scripts/test-apis/performance-testing/). You can import JMeter test plans and Gatling simulations.

## For coding agents

If you're a coding agent, migrate the load test through the [Postman plugin](/docs/postman-plugin/overview/)'s `performance-testing` skill rather than converting it by hand. The skill imports JMeter test plans and Gatling simulations, and translates the source's scripts. It prepares a collection, a performance run configuration, and an import report. The `postman collection import` command documented below is the command-line path for a person working in a shell. It covers JMeter, but not Gatling.

## 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](/docs/postman-plugin/overview/) 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](/docs/postman-plugin/work-with-postman/).

#### Migrate a load test

Import the Gatling simulation in this repo and set it up as a performance test.

## Import from the command line

Use the [Postman CLI](/docs/postman-cli/postman-cli-overview/) to import a JMeter test plan. The following command imports a `.jmx` file as a collection in your local project:

```bash
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`](/docs/postman-cli/postman-cli-collections/#postman-collection-import).