# Neoload to Gatling migration

**URL:** <https://community.gatling.io/t/neoload-to-gatling-migration/9844>\
**Category:** Gatling (Open-Source)\
**Created:** [May 2, 2026, 11:41am UTC](https://community.gatling.io/t/neoload-to-gatling-migration/9844 "2026-05-02T11:41:36Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![sack112007](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@sack112007](https://community.gatling.io/u/sack112007)\
**Post date:** [May 2, 2026, 11:41am UTC](https://community.gatling.io/t/neoload-to-gatling-migration/9844/1 "2026-05-02T11:41:36Z")

</div>

Like you have provided AI skill to migrate from Jmeter to Gatling. Anybody working on same for Neoload migration? I tried but the skills were not effective.

---

<div class="post-metadata">

**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\
**Post date:** [May 2, 2026, 12:27pm UTC](https://community.gatling.io/t/neoload-to-gatling-migration/9844/2 "2026-05-02T12:27:17Z")

</div>

Can Neoload tests be exported in a documented format?

---

<div class="post-metadata">

**Author:** ![sack112007](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@sack112007](https://community.gatling.io/u/sack112007)\
**Post date:** [May 6, 2026, 7:26am UTC](https://community.gatling.io/t/neoload-to-gatling-migration/9844/3 "2026-05-06T07:26:07Z")

</div>

It’s not possible to export Neoload into documented format. They have complicated folder structure where correlations and other parameters are stored with encoding in xml files. All the decoding happens on Neoload IDE while opening the project.

---

<div class="post-metadata">

**Author:** ![sack112007](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@sack112007](https://community.gatling.io/u/sack112007)\
**Post date:** [May 6, 2026, 7:32am UTC](https://community.gatling.io/t/neoload-to-gatling-migration/9844/4 "2026-05-06T07:32:33Z")

</div>

Also, I’m currently working on Copilot skills where the scenario is executed using **NeoLoad** , with the **Gatling Recorder configured as a proxy** so that all requests pass through the Gatling Recorder.  
This approach allows me to generate a **vanilla Gatling script** , which I can then process using another skill to convert it into our **framework-specific structure**.

However, before proceeding further, I wanted to check whether we already have an existing skill that can **directly migrate a NeoLoad script to Gatling** , eliminating the need for the intermediate recording and conversion steps.

---

<div class="post-metadata">

**Author:** ![slandelle](https://dub1.discourse-cdn.com/flex013/user_avatar/community.gatling.io/slandelle/32/4_2.png) [@slandelle](https://community.gatling.io/u/slandelle)\
**Post date:** [May 7, 2026, 7:17am UTC](https://community.gatling.io/t/neoload-to-gatling-migration/9844/5 "2026-05-07T07:17:13Z")

</div>

> However, before proceeding further, I wanted to check whether we already have an existing skill that can **directly migrate a NeoLoad script to Gatling** , eliminating the need for the intermediate recording and conversion steps.

There is none. As NeoLoad scripts are obfuscated, I don’t think there’s a way to train a LLM.

---

<div class="post-metadata">

**Author:** ![system](https://europe1.discourse-cdn.com/flex013/uploads/gatling2/original/2X/b/b148e0742de35c6280726cabf3ecd3de2d320f63.png) [@system](https://community.gatling.io/u/system)\
**Post date:** [June 6, 2026, 7:17am UTC](https://community.gatling.io/t/neoload-to-gatling-migration/9844/6 "2026-06-06T07:17:53Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.