> For the complete documentation index, see [llms.txt](https://developer.collibra.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developer.collibra.com/workflows/designing-workflows/apps/move-apps.md).

# Move apps

You can move apps between workspaces in Workflow Designer by using the **Move app** functionality of the actions menu:

* On the Apps page, find the app and click the <img src="/files/gyk2kTbte32WAuS5I2on" alt="More icon" data-size="line"> more icon next to it.
* From an individual app page, click <img src="/files/tf8vo259XhGLT2TZNYEN" alt="Beak down icon" data-size="line">**Actions** next to the name of the app in the navigation menu.

![The Move app dialog box in Collibra Workflow Designer showing advanced options](/files/lt0z4Fz8Fo5uD3OGnr6V)

## Important considerations

When you move an entire app to a different workspace, all associated revisions are included in the move.

However, there are specific scenarios to be aware of:

* Conflicts: A conflict arises when a model in your app is linked to other models outside your app, or when a model from another app references a model in your app. In these situations, the conflicted models are copied instead of moved. The app retains its revisions, but there is no model history for the conflicted models.
* Clashes: A clash occurs if there are models in the target workspace that have the same key as models in the app that you are moving. In such cases, the app revisions are lost. Additionally, no history is available for those models.

The move operation provides advanced options that allow you to choose how to handle these conflicts:

* **Warn and stop**: If the target workspace contains models with keys identical to the ones being moved, the operation stops with a warning. This prevents unintended overwrites or duplicate creations without explicit user intervention.
* **Copy conflicted models to the target workspace**: This is the default behavior for conflicts.
* **Update existing models with moved versions**: The moved models replace the existing models that have the same key.
* **Create new keys and move as new models**: The keys of the moved models are renamed by appending a sequential number to the key names.

### Copying apps

You can copy a specific app revision into a different workspace using the **Copy into workspace** action available in the **Revisions** section and use this as an effective way to copy an app to a different workspace.

{% hint style="info" %}

* You cannot copy a revision into the same workspace or into a workspace that already has a process with the same model key.
* Copying a revision does not copy the [versions](/workflows/designing-workflows/models.md#model-versions) of the app models.
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://developer.collibra.com/workflows/designing-workflows/apps/move-apps.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
