> For the complete documentation index, see [llms.txt](https://docs.yoplanning.support/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/parametrage-produit/comment-marche-la-sauvegarde-par-transition-d-un-produit..md).

# How does product transition backup work?

### Explanation of the operating principle of a transition backup.

#### Let's imagine the following situation:

You have a product called "Yoga Classes". This product is used to create sessions on a schedule, so every time you schedule a class, you use this product "Yoga Classes" to have everything in place: the name, description, times, etc.

#### How does transitional backup work in this context?

1. **Initialization**: Initially, you have a product called "Yoga Class". You use it to create multiple sessions on your schedule: Monday at 10am, Wednesday at 6pm, etc. Each session is linked to this product and uses information like the name "Yoga Class".
2. **Product Modification**: One day, you decide to change the name of the product to "Yoga Relaxation" because you want it to be more specific. So you modify the original product: "Yoga Class" becomes "Yoga Relaxation".
3. **Future use to create sessions**:
   * **New Sessions**: When you create new sessions in the future, the system will automatically use the name "Yoga Relaxation" since it is the new name of the product.
   * **Existing Sessions**: If you have already created sessions with the name "Yoga Classes", the system will check if this name has been changed in these specific sessions. If you have not touched the name in these sessions, then the system can automatically update the name to "Relaxation Yoga". But if you have already manually changed the name in a specific session to "Dynamic Yoga", for example, then the system will respect this change and will not touch this session.

#### Why is it important?

This allows all your future sessions to be updated with the new product information without overwriting any specific changes you may have made to any sessions you have already created.

#### Simple summary with example:

* **New name for the product**: “Yoga Classes” becomes “Yoga Relaxation”.
* **Auto-update for future sessions**: New sessions will automatically use "Yoga Relaxation".
* **Respect for personalized sessions**: If you have manually changed the name of an existing session to "Dynamic Yoga", this session will not be modified.

In short, transitional saving helps you keep your information up to date and consistent while respecting the custom changes you made in specific sessions. This ensures that your changes are applied everywhere they are needed, without ever erasing important details you customized.

To go further


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.yoplanning.support/en/yoplanning-academy/yoplanning-parametrage/parametrage-produit/comment-marche-la-sauvegarde-par-transition-d-un-produit..md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.