> For the complete documentation index, see [llms.txt](https://support.charlla.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.charlla.io/en/userguide/motion-thumbnail/migration.md).

# Migrate Thumbnail Player data

{% hint style="info" %} <mark style="color:$primary;">**Your existing Thumbnail Players keep working even before you migrate your data.**</mark>
{% endhint %}

### Migrate Thumbnail Player data from My Products

To keep using Thumbnail Players from the old **\[My Products]** menu, **you first need to migrate their data**.

1. If you use Thumbnail Players, a data migration pop-up appears when you open the **\[Motion Thumbnail]** menu.
2. Click **\[Migrate Data]** to complete the migration.

<figure><img src="https://1857767629-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fo7CC5HKFh1guYnGcyftj%2Fuploads%2FE7Z7c4jQ8eJHecU0hjG7%2Fmigration-1-en.png?alt=media" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}

#### <mark style="color:$primary;">Before you migrate</mark>

If we can't find the product linked to an existing Thumbnail Player, **we automatically create a product named after the thumbnail video and link it**.

<mark style="color:$primary;">**This does not affect your live Thumbnail Players.**</mark> After the migration, edit the details of the created products yourself.

*<mark style="color:$info;">Example: Thumbnail video B is linked to product A → a product named after thumbnail video B is created and linked automatically.</mark>*
{% 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://support.charlla.io/en/userguide/motion-thumbnail/migration.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.