> For the complete documentation index, see [llms.txt](https://docs.fylr.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fylr.io/for-system-administrators/migration/renaming-renditions-during-migration.md).

# renaming renditions during migration

## Via /inspect/migration

{% hint style="info" %}
This is available in fylr from version **6.33.0**.
{% endhint %}

The Restore form on `/inspect/migration/` exposes a **Rename Versions** table with three columns:

| File class | Source version | Target version |
| ---------- | -------------- | -------------- |
| `image`    | `preview`      | `640px`        |
| `video`    | `1920p`        | `1080p`        |
| `image`    | `thumbnail`    | *(empty)*      |

* one row per rename mapping; the table auto-grows a new empty row as soon as the last one is filled
* leave **Target version** empty to remove the version on the target
* rows with an empty **File class** or empty **Source version** are ignored on submit
* when a backup is selected, the table is pre-populated from the restore parameters of the previous run for that backup
* on submit, the rows are serialized into the single `rename-versions` parameter (`<cls>.<version>:<new version>`, comma-separated) and passed to `fylr restore --rename-versions`

## Via command line

```
fylr restore --help

      --rename-versions=,...        Rename versions before uploading. This affects
                                    uploaded rights as well as file versions.
                                    The versions need to be given in the notation
                                    "<cls>.<version>:<new version>", e.g.
                                    "image.preview:640px" would replace the "preview"
                                    version of image to "640px". If the "<new version>"
                                    is omitted, the version is removed.
```


---

# 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.fylr.io/for-system-administrators/migration/renaming-renditions-during-migration.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.