# Code deployment DEV -\> QA -\> PROD

**URL:** <https://forum.inductiveautomation.com/t/code-deployment-dev-qa-prod/10087>\
**Category:** Ignition\
**Created:** [June 3, 2015, 11:58am UTC](https://forum.inductiveautomation.com/t/code-deployment-dev-qa-prod/10087 "2015-06-03T11:58:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![aaronkneeland](https://avatars.discourse-cdn.com/v4/letter/a/3d9bf3/32.png) [@aaronkneeland](https://forum.inductiveautomation.com/u/aaronkneeland)\
**Post date:** [June 3, 2015, 11:58am UTC](https://forum.inductiveautomation.com/t/code-deployment-dev-qa-prod/10087/1 "2015-06-03T11:58:51Z")

</div>

Our company requires a traditional code migration from DEV to QA to PROD and we have been using TFS for code revision control and wondered if and how this might work for Ignition. I am familiar with traditional gateway backups and project backups but had some trouble trying to load a project file from one environment to the next (maybe because I had them named differently so I could differentiate if I had more than one environment open). Any suggestions on how to manage deploying project changes to a prod environment (smoothly, maybe even scripted) witout having to use the designer or causing any downtime to the application?