LoadRunner to JMeter migration
You have VuGen scripts and a reason to stop paying for LoadRunner, or a team that now runs JMeter or k6. I will tell you exactly what moving them involves, in writing, and then give you a fixed price to do it. It starts with a sanitised Action.c and its parameter files, not a meeting.
The problem, in plain words
A LoadRunner script is a C program. VuGen writes it, Controller runs the scenario around it, and Analysis reads the results. JMeter keeps the script and the load profile together in one test plan; k6 is a JavaScript file that is the scenario. So a migration is not a file conversion. It is reading what each script does and expressing it again in a tool built around a different model.
Most of that is straightforward once it is laid out: a web_url becomes an HTTP Request, a .dat file becomes a CSV feed, a transaction becomes a transaction controller. The time goes on the parts that are not straightforward, and on finding them before they turn into a test that runs cleanly while exercising nothing.
There is no LoadRunner converter in my tooling, so the mechanical part is hand work. That is why LoadRunner comes in through the review rather than a request-count tier.
What is usually awkward
-
Correlation, in the opposite order
VuGen registers a correlation before the request that produces the value (web_reg_save_param, then the request). In JMeter the extractor sits under the sampler whose response it reads. VuGen’s automatic correlation rules have no JMeter equivalent either, so every extractor is written by hand, once.
-
Login and authentication
web_set_user becomes an HTTP Authorization Manager, and NTLM or Kerberos need configuring rather than copying. Tokens issued at login have to be extracted and carried forward; a script that replays the recorded one still returns 200s, it just stops testing the logged-in journey.
-
Custom C code and lr_ functions
String handling in C, lr_eval_string, and helper functions in the script have no direct counterpart. They are rewritten, in Groovy for JMeter or JavaScript for k6, and some are better removed than ported.
-
HTML-mode calls
web_submit_form, web_link and web_image find their target in the previous response. They do not map to anything. The underlying request has to be found and written out explicitly.
-
Parameter rules and run-time settings
VuGen’s rules for which row to pick and when to update a value have to be matched with CSV feed settings, and not every combination has a direct equivalent. Pacing, think time and the scenario itself live outside the script in LoadRunner, so they need carrying across deliberately.
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
A written review of your VuGen script and a fixed price for migrating it. There is no converted script at this stage: LoadRunner has no converter, so the review is the hand work of mapping it.
- Covers
- One script, any size
- Guaranteed
- Within 2 days
VuGen scripts in the Web – HTTP/HTML protocol are accepted at the review tier. Send Action.c and the parameter files, sanitised, and you get back every request the script makes, every web_reg_save_param that becomes an extractor, every .dat that becomes a CSV feed, the functions with no JMeter or k6 equivalent, and a fixed price for the migration. Commission it and the review fee comes off.
DevWeb, TruClient, Citrix, SAP GUI and RTE scripts do not convert and are not accepted. Say which protocol yours is when you write.
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
Can LoadRunner scripts be converted to JMeter automatically?
Not with my tools: there is no LoadRunner converter in them, so the mechanical part of the migration is hand work. That is why a LoadRunner migration is quoted from a written review rather than priced from a request count like the JMeter, k6 and Gatling tiers.
Which LoadRunner protocols do you accept?
Web – HTTP/HTML (the C Web protocol) only. DevWeb, TruClient, Citrix, SAP GUI and RTE scripts do not convert and are not accepted. Say which protocol yours is when you write.
What do I get for the £250 review?
Every request the script makes, every web_reg_save_param that becomes an extractor, every .dat file that becomes a CSV feed, the functions with no JMeter or k6 equivalent, and a fixed price for the migration. If you commission the migration, the £250 comes off.
What do I send, and how?
Action.c and the parameter files, sanitised: real usernames, passwords, tokens and data replaced with synthetic values. Share them as a link from your own file store rather than an email attachment, so you can revoke access once the work is delivered.
Can the scripts end up in k6 instead of JMeter?
Yes. The review covers what each VuGen construct becomes in JMeter and in k6, including what has no equivalent in either. Say which target you want when you write.
Do we need a call to scope it?
No. The review is the scoping, and it is written. Everything is done asynchronously by email; if a question comes up we can deal with it by email too.
Start with the free version
Every VuGen construct and what it becomes in JMeter and k6, including the ones that have no equivalent. Free, no signup.
Related reading
Other migration routes
- JMeter to k6 migration, finished
Your plans are JMeter, your team now runs k6, and you want the scripts finished rather than drafted.
- What a JMeter to Gatling migration costs
You are pricing a move from JMeter to Gatling and want the number before the conversation.