> 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" %}
Before syncing between media servers (such as Plex and Jellyfin) confirm both servers contain the same movies and shows. **Missing or different media cannot be synced!**
{% endhint %}

Consider this only when:

* You understand the risks.
* Both servers have **near-identical libraries**.
* You have tested backup and restore on both servers.

{% hint style="warning" %}
Bidirectional sync between media servers carries the highest risk.

Both sides can introduce conflicts, duplicates, unintended overwrites, and propagated deletions.

For most users, **one-way remains the safer choice.**
{% endhint %}

#### "Same library" is rarely the same library

Common causes:

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

#### ID mismatches 

Providers use different identifiers:

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

Small mismatches can write to the wrong item. 

#### Mistakes cascade

One bad match on Server A copies to Server B. A later rematch makes B look wrong. Then you "fix" B and A flips back. That loop is hard to unwind.

### Related topics

* [Best practices](/getting-started/best-practices.md) - safer defaults.
* [Trackers vs. Media Servers](/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 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://wiki.crosswatch.app/related-information/media-server-to-media-server.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.