> For the complete documentation index, see [llms.txt](https://docs.scaleconnect.com.au/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.scaleconnect.com.au/scaleconnect-docs/simulator/cloning-a-strategy.md).

# Cloning a Strategy

The **Base Case** is the primary strategy created when a client is onboarded. It represents their current financial reality and cannot be deleted.

To explore alternatives, **clone** the Base Case. Each clone becomes a **sub-strategy** — a fully independent simulation you can modify without touching the original. Common reasons to clone:

* Test a different property or loan structure and see how the numbers change.
* Model an aggressive vs conservative growth scenario.
* Prepare an alternative recommendation to present alongside the original.

***

## How to clone

1. Open the **Simulator** from the sidebar.
2. Find the client's strategy card.
3. Click the **clipboard icon** on the card (top-right corner).
4. In the clone dialog, enter a **Strategy Name** for the new copy.
5. Choose a **Clone Destination**:
   * **For me** — the cloned strategy appears in your own strategy list. Only you can see it.
   * **For the client** — the cloned strategy appears under the client's account. Both you and the client can see it.
6. Click **Clone**.

The new strategy appears in the strategy list immediately. Click it to open the simulator and start making changes.

{% hint style="info" %}
Cloning always copies the client's **Base Case** strategy. If the client has multiple sub-strategies, the clone is taken from the base.
{% endhint %}

***

## What gets cloned

The clone is a complete snapshot of the strategy at the moment you copy it:

<table><thead><tr><th width="177.7109375">Included</th><th>Details</th></tr></thead><tbody><tr><td>Properties</td><td>All properties on the timeline, including addresses, acquisition details, and property assumptions</td></tr><tr><td>Property events</td><td>Loans, refinances, sales, construction loans, move house events, expenses, appraisals — every event on every property</td></tr><tr><td>Personal details</td><td>Income, expenses, HECS/HELP balance, savings, marital status, dependants</td></tr><tr><td>Projections and settings</td><td>Capital growth rates, cost escalation, variable rate, occupancy, selling costs</td></tr><tr><td>Loan structures</td><td>All loan terms, fixed/variable splits, offset account settings, commission tracking</td></tr></tbody></table>

{% hint style="warning" %}
Goals and subgoals (e.g. portfolio value targets, equity milestones) are **not** cloned. You'll need to recreate any goals on the new strategy if required.
{% endhint %}

Any changes made to the Base Case after cloning are not reflected in the clone, and vice versa. There is no way to merge changes from a clone back into the Base Case — if you want to apply changes, recreate them manually on the original.

{% hint style="info" %}
To put strategies side by side after cloning, see [Compare Strategies](https://github.com/scaleapp-au/scaleconnect-docs/blob/main/simulator/strategies/clone-and-compare.md).
{% 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 by asking a question.

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

```
GET https://docs.scaleconnect.com.au/scaleconnect-docs/simulator/cloning-a-strategy.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.