# Move backup from TEST to PROD in 8.3 **URL:** \ **Category:** Ignition\ **Tags:** ignition83\ **Created:** [September 29, 2026, 4:51pm UTC](https://forum.inductiveautomation.com/t/move-backup-from-test-to-prod-in-8-3/117248 "2026-09-29T16:51:34Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [October 7, 2026, 10:17pm UTC](https://forum.inductiveautomation.com/t/move-backup-from-test-to-prod-in-8-3/117248/7 "2026-10-07T22:17:45Z")
`ignition.conf` and `gateway.xml` are always collected as part of the backup and always restored as part of the restoration. If you don't want them overridden, you could remove them from the backup, in theory. But it's very intentional that the simplest case of "take a gateway backup, restore it somewhere else" does its very best to recreate that exact same gateway state - `ignition.conf` included. The extra files/directory workaround Phil mentioned is described in more detail by Kevin C here: > [@Disable devices in Gateway Startup Script (v8.3.0)](https://forum.inductiveautomation.com/t/disable-devices-in-gateway-startup-script-v8-3-0/111599/6): > > Setting the deployment mode via an environment variable is not yet supported, you've got to supply the Java system property via a JVM argument, -Dignition.config.mode=yourdeploymentmode. As @paul-griffith mentions, we're going to be doing additional refinements in this area. However, I've got some guidance that might be useful in the meantime. Currently, at time of writing w/ 8.3.0, if you add the deployment mode arg explicitly to your data/ignition.conf, it will be within any gateway backup … Partial gateway backup/restore (using .gwex files) is indeed part of 2027. --- _[View the full topic](https://forum.inductiveautomation.com/t/move-backup-from-test-to-prod-in-8-3/117248)._