---
sourceDocument: Yokohama Build workflows
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/build-workflows

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama Build workflows

ft:clusterId :

    - crworkflow

bundleId :

    - crworkflow

workflow :

    - Creator


---

# Copy a subflow

# Copy a subflow {#ariaid-title1}

Release version: Yokohama  
Updated June 30, 2025  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Copy a subflow to give it a new name and move it to another application scope.

## Before you begin

Role required: admin or flow_designer

## About this task

You can copy a subflow to give it a new name or move it to another application scope. The new subflow has the same subflow properties, inputs, actions, flow logic, and outputs as the source subflow.

You can't copy subflows that have a protection policy. You must have write access to a subflow to copy it.

## Procedure

1. Navigate to AllProcess AutomationWorkflow Studio.
2. On the homepage, select Subflows.
3. Select the subflow that you want to copy.
4. Click the more actions icon (![More actions menu]()) and select Copy subflow.  
   Note:  
   If the Copy subflow option is not visible, then you don't have permission to copy the subflow. This could be because the subflow has a protection policy or because you lack the necessary user role or developer permissions.
5. In New subflow name, enter a unique name you want the copied subflow to have.  
6. **Optional:** From Application, select the application scope where you want to copy the subflow.
7. Select Copy.
{#copy-subflow__steps_jbq_twt_wbc}

## Result

Workflow Studio opens the new subflow.

*[\>]: and then