Import from M3U or Another Panel

Nobody starts from an empty catalogue. XUI.live gives you three import routes, matched to where your content lives today: a playlist, another panel you buy from, or the panel you are leaving.

From an M3U

Every content type’s add screen has an Import mode that accepts an M3U file or URL — live streams, movies, series. The panel parses the playlist and creates an entry per item.

Bulk imports do not go straight to production. They land in Import & Review, one queue for streams and one for movies, where the whole batch is prepared before a single item goes live: categories assigned in bulk, duplicates flagged, delivery options set across the selection — direct source or managed, on-demand, the server tree. Approve the batch and it becomes catalogue.

The review step is what makes a 5,000-item import survivable: decisions are made once per batch, not once per item.

From an upstream provider

If you resell from an Xtream-compatible panel, register it once under Providers: name, IP or hostname, port, username, password, and switches for SSL, HLS output and legacy URL formats.

From then on the provider is part of your panel:

• The list shows the account itself — expiry date, allowed connections, and how many live streams, movies and series the account carries, refreshed on demand with Force Reload.
• Its catalogue is browsable from your add screens. Adding a live stream or a movie offers the provider’s list as a source — pick items and they become your content, delivered through your servers, sold under your packages.
• Titles stay in sync. An hourly job re-reads the provider’s naming, and any stream you have bound with title sync follows upstream renames automatically.

A provider is a source, not a mirror — you choose what to carry, and your bouquets, categories and pricing stay entirely yours.

From your previous panel

Moving off an older XUI installation is a single command on the new server, pointed at a database backup of the old one:

sudo /home/xui/tools restore /path/to/old-backup.sql

It imports the things you cannot retype — subscribers, resellers and their credits, streams, movies, series, bouquets, categories, packages, devices, blocking rules — while keeping the new installation’s schema and settings, and it takes a safety backup of the current database before touching anything. The full procedure, including what is deliberately not imported and how rollback works, is on the CLI tools page.

Which route, when

The three combine freely — most operators migrate their base with restore, wire ongoing suppliers as providers, and keep M3U import for the occasional one-off batch. However the content arrives, it behaves identically afterwards: same bouquets, same packages, same API.