---
category: [Administration & Integrations, Platform and Product Extensions, Platform and Product Extensions/Integration, Administration & Integrations/Custom Integrations & Apps, Platform and Product Extensions/Workday Extend]
keyword: [Extend, Orchestration Builder, Orchestrate, Orchestration]
nav: wcp_docs
parent_url: /wcp_docs/
title: Import Orchestrations and Suborchestrations
layout: subsection
---

### Prerequisites

<a id="prereqs-importorchsandsuborchs"></a>
Create an app containing an orchestration.

### Context

<a id="context-importorchsandsuborchs"></a>
When creating an orchestration you may find that the logic you want to employ has already been created in a different app in your account. Rather than recreate the steps from scratch, you can import the existing material and reuse it with relatively minor adjustments.

### Steps

1.  Open an orchestration in the app into which you want to import an existing orchestration or suborchestration.
2.  In the <b>Orchestrations</b> tab, click the plus symbol in the <b>Orchestrations</b> or <b>Suborchestrations</b> panel.
3.  In the <b>New Orchestration</b> or <b>New Suborchestration</b> window, select <b>Import Existing Orchestrations</b>.
4.  In the <b>Import Existing Orchestrations</b> window, use the drop-down menu to display a list your account's apps. Select the one from which you want to import.

    Orchestration Builder displays a list of orchestrations in that app. If there are a great many, you can use the <b>Search</b> field to narrow the list.

5.  Select the orchestration or orchestrations you want to import. Click <b>Import</b>.

    If any of your selected orchestrations have suborchestrations, Orchestration Builder imports those too.

    If any of your selected orchestrations use Connectors, they're added to the app's <b>Connectors</b> tab. Connected accounts aren't imported, however, so you must configure a Default and a Production account for each Connector. You must also register imported actions with agents again, as their identifiers include app information. Note that in the event of name clashes, Orchestrate appends a number to the imported action name, potentially taking it over the 30-character limit and causing the build to fail.





### Result

<a id="results-importorchsandsuborchs"></a>
Your imported orchestrations and suborchestrations appear in the relevant panels on the <b>Orchestrations</b> tab, alongside any that you created in the current app. These are your own separate copies and you can amend them as you see fit. They are not linked to the originals.