> For the complete documentation index, see [llms.txt](https://help.dscout.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.dscout.com/study-basics/edit-close-or-relaunch-studies/move-a-screener-or-study-to-another-project.md).

# Move a screener or study

Projects help you keep your research organized, and sometimes you might need to move a screener or study to a project other than the one where you created it. Maybe you used a screener to find participants for a study that lives in another project—you can move either the screener or the study to the other project so you don't have to rebuild anything.

{% hint style="info" %}
**Note:** Any role except `Viewer` can move screeners and studies, however you can only move screeners and studies between projects you have access to.
{% endhint %}

**To move a screener or study to another project:**

{% stepper %}
{% step %}
Open the project that contains the screener or study you want to move.
{% endstep %}

{% step %}
On the screener or study card, click the **three-dot (options)** icon. Then, click **Move**. A modal is displayed.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FGA0sbLTUcymHKGwoUYjy%2FMove_studies%20(1).jpg?alt=media&amp;token=3fcf9122-1362-4e41-94c9-02912415bedf" alt="" width="563"><figcaption></figcaption></figure></div>
{% endstep %}

{% step %}
Select a destination project from the drop-down. Then, click **Move study/screener**.

<div align="left"><figure><img src="https://3976082747-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FIKfn7RcT4CW9XaIbqAdd%2Fuploads%2FRXljUyOVIXw8S5N5ng2u%2FMove_studies.jpg?alt=media&amp;token=5a4b2e7d-0340-49b6-b4f0-cc7e4544afc0" alt="" width="563"><figcaption></figcaption></figure></div>

{% hint style="info" %}
**Note:** Only projects you have access to are displayed. You cannot move a screener or study to a project you're not a part of.
{% endhint %}
{% endstep %}
{% endstepper %}

{% hint style="success" %}
**Tip:** You can also move a screener or study from inside the builder. Open the **More actions** (**...**) menu in the header, then select **Move**.
{% endhint %}

### Frequently asked questions (FAQ)

<details>

<summary>Can I move a screener or study regardless of launch state?</summary>

Yes, you can move screeners or studies in `Draft`, `Launched`, or `Closed` states. However, you cannot move screeners or studies out of projects that have been marked `Completed`.

</details>

<details>

<summary>Can I move a screener or study out of a Completed project?</summary>

No, you cannot move screeners or studies out of archived projects or projects marked as `Completed`. You should ensure you've moved anything you need out of a project prior to marking it complete.

</details>


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.dscout.com/study-basics/edit-close-or-relaunch-studies/move-a-screener-or-study-to-another-project.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.