What a JMeter to Gatling migration costs
The short answer is below, in four prices. The longer answer is that the cost of moving a JMeter plan to Gatling depends on two numbers you can find yourself, for free, before you talk to anyone: how many HTTP requests the plan makes, and how many parts of it need doing by hand.
The problem, in plain words
Gatling does not think in JMeter’s terms. JMeter is a tree of GUI elements; Gatling is a simulation in code, with scenarios, injection profiles and checks written as a DSL. The requests carry across. The behaviour around them has to be expressed again, and that is where the time, and therefore the cost, goes.
That is also why an hourly estimate for this kind of work is hard to trust: nobody knows how many awkward parts a plan has until they look. The free converter looks for you. Once you have its two numbers, the price is arithmetic.
What is usually awkward
-
Correlation
JMeter extractors become Gatling checks that save values into the virtual user’s session. Every one has to be carried across, and any value the plan was replaying from a recording has to be found first.
-
Logins and sessions
Gatling keeps cookies per virtual user for you, but tokens issued at login, auth headers and anything JMeter set at Header Manager scope still have to land on the right requests and no others.
-
Custom code
Groovy in JSR223 and BeanShell blocks is rewritten as code in the simulation’s language. It is the least predictable part of any migration, which is why it is priced separately.
-
Injection profile
A thread group is a fixed number of users looping. Gatling can express that, or an arrival rate of new users. Which one the original test meant is a decision, not a conversion, and choosing wrongly changes what the results mean.
-
Feeders
CSV Data Set Config becomes a feeder. How rows are shared between users and what happens at the end of the file have to match what the JMeter plan did, or the test quietly runs with different data.
How the fixed prices apply
Turnarounds are calendar days, counted from when a complete submission arrives. Full details, and checkout, are on the script migration page.
Conversion review
£250
One-off, inclusive
You get the converted script and a written report of exactly what still needs doing by hand, and how to do it. I do not do the manual work at this tier.
- Covers
- One script, any size
- Guaranteed
- Within 2 days
Single script
£750
One-off, inclusive
One user journey migrated and finished — including the parts no converter can do faithfully.
- Covers
- Up to 50 HTTP requests and 10 manual-work items
- Guaranteed
- Within 3 days
Suite
£1,500
One-off, inclusive
A set of related scripts migrated together, with shared data files and configuration kept consistent across them.
- Covers
- Up to 200 HTTP requests and 30 manual-work items
- Guaranteed
- Within 5 days
Larger migrations
From £3,000
Quoted from your numbers
Beyond the caps above, or with constraints that need agreeing first. Priced from the same request and manual-work counts, so the quote is arithmetic rather than a negotiation.
- Covers
- No cap — scope agreed up front
- Guaranteed
- Agreed with you
Custom script blocks (JSR223, BeanShell) are the one thing priced outside the caps: the time they take depends on what they do, so I price them before starting rather than guess.
Cheaper routes are real, and worth trying first on a small plan: the free converter handles one journey of up to 25 HTTP requests in your browser, and Perf Script Studio converts without that cap, offline, for a one-off £149. Gatling also publishes its own AI converter skill; the post linked below compares the options fairly.
No risk in picking the wrong tier. If your script turns out to exceed the cap you bought, I will refund you in full or quote the difference — your choice, and you decide before I start any work.
Need it faster? Ask before you buy. A faster turnaround is +50%, if I can commit to it for your job, and I will tell you either way. I would rather turn it down than miss it.
Your script stays yours
Send sanitised scripts only, with real usernames, passwords, tokens and data replaced by synthetic values, and share them as a link from your own file store rather than an email attachment. Everything is done asynchronously by email; there is no call.
Read exactly what happens to your script, or check it first with the free script scanner.
Questions
How much does it cost to migrate JMeter scripts to Gatling?
With me: £250 for a Conversion Review (the converted simulation plus a written list of the manual work), £750 for one script finished (up to 50 HTTP requests and 10 manual-work items), £1,500 for a suite (up to 200 HTTP requests and 30 manual-work items), and from £3,000 beyond that, quoted from the same counts. Custom script blocks are priced before I start.
How do I know which price applies to my test plan?
Run the free converter with JMeter → Gatling selected. It reports the number of HTTP requests and the number of items needing manual work, which are the numbers the tiers are written in, so you know the price before you contact me.
Is the fixed price really fixed?
Yes. The price on the card is the price, paid at checkout. If your script turns out to exceed the cap you bought, I will refund you in full or quote the difference — your choice, and you decide before I start any work.
How long does a JMeter to Gatling migration take?
Turnarounds are calendar days from when a complete submission arrives: Conversion Review within 2 days, Single script within 3 days, Suite within 5 days, and dates agreed with you for larger migrations. A faster turnaround is +50%, if I can commit to it for your job.
Should I use Gatling’s own AI converter instead?
If Gatling is definitely the destination and your team already works in a compatible AI coding assistant, it is a reasonable first step. Paying for a finished migration makes sense when the list of things it flags turns out to be the project.
Start with the free version
Converts a .jmx to a Gatling simulation in your browser, nothing uploaded, and gives you the request count and manual-work list the prices are based on.
Related reading
Other migration routes
- LoadRunner to JMeter migration
You have VuGen Web HTTP/HTML scripts and want them in JMeter or k6.
- JMeter to k6 migration, finished
Your plans are JMeter, your team now runs k6, and you want the scripts finished rather than drafted.