# Low level commands using .NET client 8.13 **URL:** \ **Category:** Elasticsearch\ **Tags:** language-clients\ **Created:** [July 8, 2024, 1:22pm UTC](https://discuss.elastic.co/t/low-level-commands-using-net-client-8-13/362717 "2024-07-08T13:22:43Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![SoleusRex](https://avatars.discourse-cdn.com/v4/letter/s/e79b87/32.png) [@SoleusRex](https://discuss.elastic.co/u/SoleusRex)\ **Post date:** [July 8, 2024, 1:22pm UTC](https://discuss.elastic.co/t/low-level-commands-using-net-client-8-13/362717/1 "2024-07-08T13:22:43Z")
I'm working on a project where our index settings and mappings are maintained as JSON, and I'm wondering if there's a way for the current .NET client to use these to setup our indices. I've found older posts (example [here](https://discuss.elastic.co/t/is-there-a-way-to-just-post-a-command-using-the-low-level-or-nest-net-clients/283392)) that make it seem like this was once possible. However, the code in these examples does not seem to work with the current client; and I haven't found much when searching the Github repository for related terms, either. Does the feature I'm asking about no longer exist, or am I just not seeing how to access it? ---
**Author:** ![flobernd](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flobernd/32/124877_2.png) [@flobernd](https://discuss.elastic.co/u/flobernd)\ **Post date:** [July 9, 2024, 1:07pm UTC](https://discuss.elastic.co/t/low-level-commands-using-net-client-8-13/362717/2 "2024-07-09T13:07:49Z")
Hi @SoleusRex, this is still possible by accessing the low-level transport: > **[Migration guide: From NEST v7 to .NET Client v8 | Elasticsearch .NET Client...](https://www.elastic.co/guide/en/elasticsearch/client/net-api/current/migration-guide.html#_workarounds_for_missing_features)** ---
**Author:** ![sohamsinh31](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@sohamsinh31](https://discuss.elastic.co/u/sohamsinh31)\ **Post date:** [November 25, 2025, 6:39am UTC](https://discuss.elastic.co/t/low-level-commands-using-net-client-8-13/362717/3 "2025-11-25T06:39:18Z")
This page is no longer exist please check @flobernd ---
**Author:** ![flobernd](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flobernd/32/124877_2.png) [@flobernd](https://discuss.elastic.co/u/flobernd)\ **Post date:** [November 25, 2025, 4:13pm UTC](https://discuss.elastic.co/t/low-level-commands-using-net-client-8-13/362717/4 "2025-11-25T16:13:08Z")
Not sure what happened here, but this link still seems to work: > **[Migration guide: From NEST v7 to .NET Client v8 | Elasticsearch .NET Client...](https://www.elastic.co/guide/en/elasticsearch/client/net-api/8.19/migration-guide.html)** ---
**Author:** ![sohamsinh31](https://avatars.discourse-cdn.com/v4/letter/s/7ba0ec/32.png) [@sohamsinh31](https://discuss.elastic.co/u/sohamsinh31)\ **Post date:** [November 26, 2025, 6:53am UTC](https://discuss.elastic.co/t/low-level-commands-using-net-client-8-13/362717/5 "2025-11-26T06:53:24Z")
All solution for migrating NEST to ES seems temporary or not properly guided methods. Please look into this issue. ---
**Author:** ![flobernd](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/flobernd/32/124877_2.png) [@flobernd](https://discuss.elastic.co/u/flobernd)\ **Post date:** [November 26, 2025, 6:26pm UTC](https://discuss.elastic.co/t/low-level-commands-using-net-client-8-13/362717/6 "2025-11-26T18:26:58Z")
Sorry, I don’t really get this comment. Could you please explain? The end of life for NEST has been announced nearly 2 years ago - this should have given plenty of time to start an incremental upgrade like we suggest in our guide and blog posts. If there is any specific part that you need help with in regards of the upgrade, please don’t hesitate to ask.