> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/related-information/tracker-to-media-server.md).

# Tracker to Media Server

Why syncing from a tracker into a media server is risky, and safer defaults for history and ratings.

Tracker-to-media-server sync brings your existing tracker data into the library where you watch.

It works well when your tracker is the source of truth. Many people use it to restore watched state after a new server setup or keep several playback libraries aligned.

{% hint style="warning" %}
Plex has no supported way to **backdate** a play.

If CrossWatch writes **History** into Plex, Plex records `watched_at` as **now**.

This affects history sync and **History** capture restores.

That matters because when you later syncs history back from Plex to a tracker, CrossWatch send those Plex timestamps back to the tracker as if they were the real watch dates. This can overwrite the user’s historical watch timeline.
{% endhint %}

### Before you sync

#### Libraries change

Media servers rematch items. Editions change. Specials move.

Use current, well-matched metadata for reliable results.

#### Trackers often include more titles

A tracker records everything you watched. This can include cinema, streaming, and shared-server plays.

A media server only knows what is on disk. That is a subset.

Enable **Only items in destination library** for History. CrossWatch then skips tracker items that are missing from the server.

This keeps sync results focused on playable local media.

#### Plex history dates

Plex records a newly written play as watched now. It cannot backdate that play.

This affects History sync and History capture restores. A later Plex-to-tracker sync can send that newer timestamp back to the tracker.

### When it can make sense

Use tracker-to-server sync when the tracker has the state you want locally.

Common uses:

* Restore watched state after migrating or rebuilding a media server.
* Show your tracker history in a server library.
* Use a tracker watchlist as a Plex or Jellyfin queue.

### Recommended setup

Start with these settings:

* Use a **one-way** pair from the tracker to the media server.
* Enable **Only items in destination library** for History.
* Run **Interactive Sync** and review the first result.

After the first clean run, enable other supported features as needed.

### Related topics

* [Best practices](https://wiki.crosswatch.app/getting-started/best-practices.md) - recommended directions and defaults.
* [Trackers vs. Media Servers](https://wiki.crosswatch.app/related-information/trackers-vs.-media-servers.md) - why the roles differ.


---

# 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://wiki.crosswatch.app/related-information/tracker-to-media-server.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.
