> 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/media-server-to-media-server.md).

# Media Server to Media Server

{% hint style="info" %}
Media-server-to-media-server sync keeps watched state and supported data aligned across libraries, such as Plex and Jellyfin.
{% endhint %}

It works best when both servers contain the same movies and shows.

### Common uses

* Keep a Plex and Jellyfin library aligned during a migration.
* Use separate servers in different locations with the same media.
* Maintain a primary server and a matching backup server.

### Recommended setup

Start with a **one-way** pair and History only.

Enable **Only items in destination library**. Each server then writes only to items it contains.

Run **Interactive Sync** and review the first result. Add other features or enable two-way sync after clean runs.

{% hint style="warning" %}
Two-way sync is useful when both servers receive real playback activity.

Confirm matching works well on both sides before enabling it.

Keep removals disabled unless watched-state changes should propagate both ways.
{% endhint %}

### Keep libraries aligned

Servers can contain different versions of the same library. Review these differences before syncing:

* Different IDs
* Different editions or cuts.
* Partial seasons.
* Extras and specials.
* 4K vs 1080p duplicates.

#### IDs matter

Providers use different identifiers:

* Plex GUIDs
* Jellyfin/Emby internal IDs
* TMDb, TVDB, or IMDb remaps

Use accurate external IDs on both servers. This improves matching and avoids missed updates.

#### Manage changes carefully

Start with a small library or a dry run. Check unmatched items and metadata before expanding the scope.

Keep backups when testing a new two-way configuration.

### Related topics

* [Best practices](https://wiki.crosswatch.app/getting-started/best-practices.md) - safer defaults.
* [Trackers vs. Media Servers](https://wiki.crosswatch.app/related-information/trackers-vs.-media-servers.md) - pick a source of truth.


---

# 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/media-server-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.
