How can we move workflow from one instance to another without an updateset in servicenow?

[Ankit Kumar6]

Hi Team,

I forgot to capture workflow in an update set, so how can i move it from one instance to another.

Please help me i have developed whole WF.

Thanks 

Ankit

[dgarad]

Hi @Ankit Kumar6 

 Create a new update set capture workflow in the new update set.

[Yashsvi]

Hi @Ankit Kumar6,

Yes it's possible, using update sets:

Moving a Workflow Using Update Sets in ServiceNow

1. Identify the Workflow in the Default Update Set:

  - Navigate to System Update Sets > Local Update Sets

  - Select the Default update set.

  - In the related lists, locate Customer Updates

  - Filter or search for the workflow you forgot to capture initially.

2. Move the Workflow to a New Update Set:

  - Navigate to System Update Sets > Local Update Sets

  - Create a new update set by clicking New

  - Name the update set appropriately and Save it.

  - Go back to the Default update set.

  - In the Customer Updates related list, find the workflow.

  - Right-click the record related to your workflow and select Move to Update Set

  - Choose the new update set you created.

3. Export the Update Set

  - After moving the workflow to the new update set, navigate to System Update Sets > Local Update Sets

  - Select your new update set.

  - Click Export to XML

  - Save the XML file to your local machine

4. Import the Update Set into the Target Instance:

  - Navigate to the target ServiceNow instance.

  - Go to System Update Sets > Retrieved Update Sets

  - Click Import Update Set from XML

  - Choose the XML file you exported and import it.

  - After importing, find the update set in System Update Sets > Retrieved Update Sets

  - Open the imported update set and click Preview Update Set to check for any conflicts or issues.

  - If everything looks good, click Commit Update Set

Please try these steps will help you move a workflow from one ServiceNow instance to another by utilizing update sets effectively.

Thank you, please mark helpful, if you accept the solution.

[Robbie]

Hi @Ankit Kumar6,

With the number of 'moving parts' associated with a workflow, and the assumption this will need to be moved to Prod with the existing update set/changes in the near future, the best approach would be to create a new update, checkout the required workflow and then publish it.

This will capture the workflow within the update set which you can deploy to the alternative instance(s).

To help others (or for me to help you more directly), please mark this response correct by clicking on Accept as Solution and/or Kudos.

Thanks, Robbie