Syncing
Align watchlists, history, and ratings between services. Start with one-way + one feature + dry run, then scale up.
Syncing aligns watchlists, history, and ratings between services. Start small. Scale up after the first clean run.
Save changes often. Most settings do nothing until you click the red floating Save button.
1) Connect authentication providers
Open Settings → Authentication. Connect only what you need.
Start with:
One media server: Plex, Jellyfin, or Emby
One tracker: Trakt, SIMKL, MDBList, etc.
Click the red Save button.
Related: Authentication
2) Create one pair
Open Settings → Pairs. Create one pair first.
Use the safest setup. Keep defaults unless you know why you’re changing them.
Golden rule: start one-way, with one feature enabled.
Recommended first run
Mode: One-way
Feature: enable one
Watchlist
Ratings
History
Progress (Plex/Emby/Jellyfin pairs only)
Source: your media server
Target: your tracker
Progress only appears for Plex/Emby/Jellyfin ↔ Plex/Emby/Jellyfin pairs.
It does not apply when your target is a tracker (Trakt/SIMKL/MDBList/etc).
Do not start with “everything”. Run one feature first. Then add more.
Keep Dry run enabled at first. It previews the plan without writing changes.
Click the red Save button.
Related: Configure Pairs
3) Add metadata (recommended)
Open Settings → Metadata. Add TMDb (API key).
This improves matching. It also reduces missing peers.
Click the red Save button.
Related: Metadata
4) Run a sync
Run a sync. Review results. Fix matching issues. Repeat.
If the run ends with a line like Done. Total added: ..., see: Sync results (added/removed/skipped)
Use these tools when something looks off:
Once your first pair is stable, add the next feature or pair.
Related topics
Webhook or Watcher — real-time scrobbling instead of periodic syncing.
Best practices — recommended sync layouts.
CW Orchestrator — how planning and applying works.
Scheduling — run pairs on a cadence.
Summary
Syncing aligns watchlists, history, and ratings between providers.
Start with one-way + one feature + dry run.
Add TMDb early to avoid bad matches.
Next steps
Configure feature toggles and guardrails: Configure Pairs
Improve matching quality: Metadata
Automate runs safely: Scheduling
Diagnose missing peers and IDs: Analyzer
Last updated
Was this helpful?