---
title: Exporting a flow
description: Export a flow to create a flow backup file that you can analyze or import into another environment.
component: davinci
page_id: davinci:flows:davinci_exporting_a_flow
canonical_url: http://docs.pingidentity.com/davinci/flows/davinci_exporting_a_flow.html
revdate: October 14, 2024
section_ids:
  about-this-task: About this task
  steps: Steps
  choose-from: Choose from:
---

# Exporting a flow

Export a flow to create a flow backup file that you can analyze or import into another environment.

## About this task

Exporting a flow creates a JSON version of the flow. You can use this file to:

* Copy flows between your different environments, such as between test and production

* Create backups or store flows in external version control systems

* Share the flow with colleagues who use a different environment

You can also export forms that are part of the flow. Learn more in [Importing and exporting forms](http://docs.pingidentity.com/pingone/user_experience/p1_import_export_forms.html).

Ping support might also request flows for troubleshooting purposes.

## Steps

1. In DaVinci, click the **Flows** tab.

2. Open the flow that you want to export.

3. Choose one of the export options:

   ### Choose from:

   * To export the current version, click **More options ( [icon: ellipsis-v, set=fa]) > Download Flow JSON**.

   * To export a previous version, go to **More options ( [icon: ellipsis-v, set=fa]) > Flow Versions**, locate the version that you want to export, and click **... > Download Flow JSON**.

4. (Optional) Select **Include Variable Values** to include the current values of company or flow variables that are used in the flow.

   |   |                                                                                                                                                             |
   | - | ----------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | Because variables can contain secret or proprietary information, only use this option for flows that you do not plan to share outside of your organization. |

5. (Optional) If the flow uses subflows, select **Include Subflows** to include the subflows in the JSON file.

   |   |                                                                                                                                           |
   | - | ----------------------------------------------------------------------------------------------------------------------------------------- |
   |   | If you plan to import the flow into another environment for a second time, you can disable this option to avoid reimporting the subflows. |

   |   |                                                                                                                                                                                                                                                                |
   | - | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
   |   | If you selected **Include Subflows**, and the flow contains **Flow Conductor** nodes that use invalid subflows or subflow versions, an error message displays detailing the issues. You must resolve these issues before exporting the flow with its subflows. |

6. (Optional) If the flow includes forms, select **Include Forms** to include any forms that are part of the flow.

7. Click **Export**.