Migrating a radio station or platform to a new panel can feel daunting, but it’s more straightforward than it looks. Whether you’re moving from CentovaCast, AzuraCast, or another panel, this guide covers the whole process. Before you do anything else, we recommend reading the Start your own streaming platform guide. Once you’re familiar with the basics, return here to work through the migration.

Step 1: Assess your Current Setup

If you’re migrating from CentovaCast, you’re in a particularly good position. We include a dedicated migration utility that automates the entire transfer, stations, playlists, media, configuration and there’s a full guide covering it in the MediaCP Server Admin Manual. There’s even a free migration service available for CentovaCast customers who take part in the competitor migrate programme. We migrate your stations exactly as they are, so there’s nothing to reconfigure. Head straight to Step 3.

For all other platforms, a few questions worth answering before you begin: Will you be using AutoDJ? How many streams do you need, and are they tied to one station or spread across multiple? Are you managing your own station, or do you have clients and resellers that each need their own setup? If you need help navigating these questions or any part of this guide contact our support team.

If you’re running basic live encoder streams only, migration is straightforward; simply recreate your stations with the same stream links. AutoDJ setups require more work: you’ll need to transfer your media library and recreate your playlists and schedule.

Step 2: Install

With a clear plan in place, it’s time to install the Media Control Panel on your server. If you’re migrating from CentovaCast, the Media Control Panel will need to be installed on the same server to allow the migration utility to function.

To install the Media Control Panel, you’ll need root access to a server meeting our system requirements and running a supported operating system: Debian 11, 12, or 13; Ubuntu 22.04 or 24.04; CentOS Stream 9 or 10; or AlmaLinux 9 or 10. You’ll also need a domain pointed at your server so the panel and streams can run securely over HTTPS. If you don’t have a VPS or domain sorted yet, see our guide: Start your own streaming platform

Install with a single command: su -c "$(curl -sSL http://install.mediacp.net)"

Prefer to have us handle it? We include a free installation service with every new license. Along with this, there is a migration deal for CentovaCast customers which offers installation and a full migration service for free.

Step 3: Migration

Once your Media Control Panel is online and working it’s time to migrate your customers over.

CentovaCast

CentovaCast users should follow the dedicated CentovaCast migration guide or contact our helpdesk for support: https://www.mediacp.net/doc/admin-server-manual/migrate/migrate-from-centovacast-to-mediacp/

Because the migration for CentovaCast is automated and completed on a single server, there should be no further steps once you’ve completed the guide above or our team has completed the migration for you. The rest of this guide is for users of other panels.

AzuraCast and other panels

For AzuraCast and other platforms, the two main tasks are replicating your stream links and transferring your media library. Your listeners connect to specific URLs, so recreating the same mount points, ports, and passwords in MediaCP will keep disruption to a minimum. For AutoDJ stations, you’ll need to move your media files to the new server (we recommend rsync for large libraries) and then re-import them into your station’s media library along with any playlists and schedules.

AzuraCast has a specific scheme for their streaming links; to help with this, we’ve put together a dedicated migration guide for AzuraCast. The process involves creating a custom ngnix rewrite rule to allow you to use links like /radio/8000/stream or /radio/servicename/stream and keep compatibility with your AzuraCast links.

The same can be done for other panels if you need to replicate a specific streaming link format:
https://www.mediacp.net/doc/admin-server-manual/migrate/migrate-from-azuracast/

Multiple stations on a single Icecast instance?

If you’re currently using a single Icecast server with multiple mount points to host different stations, this is still possible in the Media Control Panel. However, for easier management, we recommend setting up a dedicated station in the panel for each station instead. This allows for greater management, monitoring, per station analytics and controls for each unique broadcast.

Step 4: Configure and Go Live

The final step is verifying everything works before you switch listeners over. Confirm your stream URLs match your previous setup, test AutoDJ playback if you’re using it, and check that your live encoder can connect. It’s worth running your old and new streams in parallel during testing so there’s no downtime for your audience when you make the switch.
Once you’re happy everything is broadcasting correctly, update your DNS or stream redirects to point to the new server and you’re done.

Ready to get started? Head to the MediaCP quick-start guide and launch your platform.