Move or Copy Workflows

Use Move to to reorganize Workflows inside a Site. Use Copy to and Paste Workflows to create independent copies in the same Site or another Site.

Move Workflows

  1. Open Workflows and select the Workflows or folders.
  2. Click Move to.
  3. Select the destination Workflow folder.
  4. Confirm the move.
  5. Open the destination and verify the paths.

Moving changes organization, not the Workflow key or runtime. Review any external team process that relies on the former folder path.

Copy and paste

  1. Select the Workflows or folders on the Workflows screen.
  2. Click Copy to. The Console writes a copy payload to the browser clipboard.
  3. Navigate to the target Site and Workflow folder.
  4. Click Paste Workflows.
  5. If you are copying within the same Site and the selection refers to unselected Sub-Workflows, choose whether to create new copies of those dependencies or keep the existing references.
  6. Wait for the final success or warning alert.

The Workflow runtime is preserved. The Console creates new Workflow identities, keeps the relative folder structure below the common copied root, and remaps copied Sub-Workflow references to the new keys.

Connections and cross-Site copies

When you paste into another Site or Tenant, the Console creates Connection stubs and remaps copied references. Stubs preserve the Connection contract, but they do not transfer protected endpoint values or credentials. Open each new Connection, configure every required Environment, test it, and save it before using the copied Workflow.

A cross-Site paste also includes implicitly referenced Sub-Workflows. Within the same Site, the Console prompts you because keeping a reference to the existing Sub-Workflow can be preferable.

Validate the result

  1. Open each copied Workflow in Test.
  2. Resolve warning alerts about Sub-Workflows or Connections.
  3. Check Connection assignments, Sub-Workflow contracts, execution placement, and triggers.
  4. Run a safe test using the Workflow's runtime-specific designer controls.
  5. Save the validated revision and promote it through the normal lifecycle.

Clipboard errors

The copy flow requires browser clipboard access. If paste reports invalid or missing copied data, copy the selection again and confirm the browser permits clipboard access for the Console. Firefox can require explicit clipboard configuration. Avoid pasting arbitrary clipboard content into the Console.

See Workflows Screen, How to Use Sub-Workflows, and Create a Connection.