> For the complete documentation index, see [llms.txt](https://help.modelreef.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.modelreef.io/syntax/scenario-syntax/cloning-scenarios.md).

# Cloning Scenarios

This article explains how to **clone scenarios** in Model Reef.

You will learn:

* How to duplicate an existing model to create a new scenario.
* What is copied during cloning.
* How to use cloning for both scenario design and version control.

Cloning is the main way to create new scenarios without rebuilding structure or re-importing data.

{% hint style="info" %}
The clone is a complete copy of the original at that moment in time. After cloning, the original and the clone no longer interact.
{% endhint %}

***

## Cloning a model to create a scenario

To clone a scenario or base model, follow these steps:

{% stepper %}
{% step %}

### Locate the model

In the workspace, locate the model that represents your current case.
{% endstep %}

{% step %}

### Duplicate / Copy model

Use the **Duplicate / Copy model** function.
{% endstep %}

{% step %}

### Name the new model

Name the new model to reflect its role, for example:

* `Client - FY25 - Base`
* `Client - FY25 - Upside`
* `Client - FY25 - Equity raise case`
  {% endstep %}
  {% endstepper %}

***

## What cloning copies

Cloning copies:

* All branches and their hierarchy
* All variables and their timing and formula settings
* All drivers and Data Library entries
* All imported data (historicals and fundamentals)
* All dashboards, charts and custom reports
* All valuation settings and assumptions

***

## Using clones for scenario exploration

You can use clones to explore:

* Alternative growth, cost or capex paths
* Different funding or capital structure options
* Transaction and project cases versus base business
* Stress, downside or upside cases

Each clone can be modified independently while the base remains intact for reference.

***

## Cloning for version control

Cloning can act as a simple versioning strategy:

* Clone before major structural or assumption changes
* Keep previous versions in an archive or version folder
* Use names such as `Model v1.0`, `Model v1.1`, `Model v2.0`

This gives you a clear trail of how the model has evolved.

***

## Clean up and governance

Over time you may accumulate many clones. To keep things tidy:

* Archive models that are no longer active
* Use folders to group scenarios by client, project or planning cycle
* Periodically review and remove obsolete experimental clones

Clear governance keeps scenario sets understandable for everyone using the workspace.

***

## Related articles

* [Creating Scenarios](/syntax/scenario-syntax/creating-scenarios.md)
* [Branch Selector](/syntax/understanding-the-interface/branch-selector.md)
* [Data Library Mapping](/help/quickbooks-integration/data-library-mapping.md)
* [Scenarios & Planning](/how-tos/scenarios-and-planning.md)


---

# 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://help.modelreef.io/syntax/scenario-syntax/cloning-scenarios.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.