# Global Lists: Multi-environment management

**URL:** <https://discuss.workflowgen.com/t/global-lists-multi-environment-management/524>\
**Category:** Global Lists\
**Created:** [July 27, 2013, 3:03am UTC](https://discuss.workflowgen.com/t/global-lists-multi-environment-management/524 "2013-07-27T03:03:54Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![wfg-admin](https://yyz2.discourse-cdn.com/flex030/user_avatar/discuss.workflowgen.com/wfg-admin/32/714_2.png) [@wfg-admin](https://discuss.workflowgen.com/u/wfg-admin)\
**Post date:** [July 27, 2013, 3:03am UTC](https://discuss.workflowgen.com/t/global-lists-multi-environment-management/524/1 "2013-07-27T03:03:54Z")

</div>

Global List definitions are not exported with a process definition. You have to consider a Global List like a database table when you manage multiple environments (e.g. development, staging, production)

This means that when you export a process definition from development to production, you have to check if the Global Lists used by the web form are already in production too.

To deploy a Global List from development to production, WorkflowGen administrators just have to export the Global List as an XML file and import it in the production server.

Then, if needed, you can change the Global List settings (such as the databinding settings) and content for production usage .

To manage multiple versions of a global list, you have to duplicate the global list and rename the new list (e.g. rename `MYVLIST_V1` to `MYLIST_V2`).
