How do I move a Flow to a different application?

[GLewis5]

In most cases, if I have a script that is in the global scope, then I can move it to a different application in the global scope by using the "Move to Application..." UI Action.

This does not seem to work with Flow Designer.

If I have a Flow or a Subflow or Action that was created in the global scope, and I want to move it to a different globally scoped application, how do I do it?

[Community Alums]

Hi @GLewis5 ,

To move a Flow to a different application scope in ServiceNow, you can follow these steps:

1. Open the Flow you want to move.

2. Click on the "..." icon in the upper right corner of the screen and select "Move to Application" from the dropdown menu.

3. In the "Move to Application" window, select the new application scope you want to move the Flow to.

4. If you want to move all related items along with the Flow, select the "Include related items" checkbox.

5. Click on the "Move" button to complete the process.

6. After the Flow is moved, it will no longer be available in the original application scope.

Note that moving a Flow to a different application scope can have implications for other items that reference the Flow, such as other Flows, scripts, or business rules. Make sure to carefully review any potential impacts before moving a Flow to a different application scope.

[GLewis5]

When I open a flow and click "..." I see the following options

• Properties
• Executions
• Flow stages
• Manage flow catalog variables
• Flow Reporting Settings
• Flow Variables
• Configure connections
• Copy flow
• Flow preferences
• Create code snippet
• Manage security
• Change default title

I do not see "Move to Application"

[Ross Sonido]

Select the Copy Flow from the options then select the target Application.

You can then delete the previous copy of the Flow as you initially wanted to move, not copy.

[Nive]

In Flow Designer, you can move a Flow, Subflow, or Action from one globally scoped application to another by exporting it from the source application and importing it into the target application. Here are the steps to do so:

1. Open the source application where the Flow, Subflow, or Action is currently located.
2. Open the Flow Designer canvas and locate the Flow, Subflow, or Action that you want to move.
3. Click on the three-dot menu icon in the top right corner of the Flow, Subflow, or Action and select "Export".
4. In the Export dialog, select the "Export as JSON" option and click "Export".
5. Save the exported file to your local system.
6. Open the target application where you want to move the Flow, Subflow, or Action.
7. Open the Flow Designer canvas and click on the "+" icon in the top left corner to create a new Flow, Subflow, or Action.
8. In the "New Flow" dialog, select the "Import" option.
9. Browse for the exported file from Step 5 and select it.
10. Click "Import" to import the Flow, Subflow, or Action into the target application.

Once you have completed these steps, the Flow, Subflow, or Action will be available in the target application and you can continue working on it there.

Note that this method of moving Flows, Subflows, or Actions between globally scoped applications does not transfer any data, connections, or dependencies associated with them. If your Flow, Subflow, or Action has any dependencies on other objects in the source application, you will need to manually update those references in the target application.