Migration and Coexistence

Planned

Guided migration is planned. It is not available in the private beta and should not be treated as a current import feature.

OmniLux is a standalone media system. Connecting Plex, Jellyfin, or Emby will be optional and should make evaluation or migration easier, not create a permanent runtime dependency.

Private beta: compare side by side

You can begin without another media server or keep an existing server online while you evaluate OmniLux.

For a side-by-side comparison:

1. Mount the same lawful source library read-only.
2. Let each server keep its own database and application state.
3. Compare browsing and playback without changing the source files.
4. Keep the existing server available until you choose otherwise.

OmniLux in actionSee the folders OmniLux can scan and the storage settings available for your library. View full size ↗

Planned: guided migration

The planned migration experience will use visible checkpoints:

1. Discover supported libraries, users, collections, and watch-history sources.
2. Map source identities and libraries to OmniLux equivalents.
3. Preview counts, unsupported records, conflicts, and proposed changes.
4. Import only the scope you approve into OmniLux-owned state.
5. Verify playback, users, and representative history before cutover.
6. Choose whether to cut over or roll back.

The source media tree remains unchanged throughout that metadata and history workflow.

Unavailable

• Automatic import from Plex, Jellyfin, or Emby
• A connector presented as a current private-beta feature
• A forced replacement or installer-driven cutover

Migration safety promise

• Preview before import
• Report unsupported data instead of silently dropping it
• Explain duplicates before repeating an import
• Keep cutover as a household decision
• Preserve the option to stop and continue using the existing server

Next steps

• Product Roadmap
• Private Beta Guide
• Libraries and Metadata