# Prepare a transformation

Compare transformation scenarios based on what your estate really consumes.

## The steps

1. Check that someone on your team carries the **Presales** role: the **Transformation** section of the menu only appears with it.
2. Open **Sizing assistant**, and select the clusters to transform.
3. Keep or reduce the target platforms.
4. Adjust the assumptions, then run the sizing.
5. Open **Scenarios**: the platforms side by side, over 3 or 5 years.

## What you get

The number of servers needed and a total cost for each platform, against a baseline. The assistant starts from the **measured footprint** of your clusters, not an estimate, and saves each calculation as a scenario.

## The questions to ask

- **On which figures?** The scenario keeps the exact collections it was calculated on. After a new import, have it recalculated.
- **At which prices?** The **Platform catalog** holds the node models and their prices. Replace the default values with your negotiated prices before presenting a cost.
- **What assumptions?** Overcommit rate, high availability, growth: ask for them along with the figure.

> A scenario sizes: it replaces neither an architecture study nor a quote. It helps you know which options deserve one.

### I do not see the Transformation section

It requires the **Presales** role: see [Roles and rights](/en/administer/roles-and-rights).

### A cluster is missing from the list

The list follows your consolidated present and your analysis scope. Check your filters, then the last collection of its source.
