# Windows to Linux Gateway Conversion

**URL:** <https://forum.inductiveautomation.com/t/windows-to-linux-gateway-conversion/89698>\
**Category:** Ignition\
**Created:** [April 30, 2024, 1:14pm UTC](https://forum.inductiveautomation.com/t/windows-to-linux-gateway-conversion/89698 "2024-04-30T13:14:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![tmahaf](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tmahaf/32/23492_2.png) [@tmahaf](https://forum.inductiveautomation.com/u/tmahaf)\
**Post date:** [April 30, 2024, 1:14pm UTC](https://forum.inductiveautomation.com/t/windows-to-linux-gateway-conversion/89698/1 "2024-04-30T13:14:32Z")

</div>

Are there some best practices to consider?

Our approach would be to spin up a server with the same host name, IP address, same Ignition service name as the Windows machine, same gateway name, remove windows machine from network, put Linux machine on network, install gateway backup, transfer license.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [April 30, 2024, 2:15pm UTC](https://forum.inductiveautomation.com/t/windows-to-linux-gateway-conversion/89698/2 "2024-04-30T14:15:58Z")

</div>

Check `ignition.conf` for any windows-style paths with backslashes that need converting to forward slashes. And any other paths that are windows-specific.