Migrate your radio hosting to SPCast
Changing radio providers involves more than an encoder. Audio files, schedules, players, apps and radio directories need to work together. Keep the existing service available until testing is complete and agree on a switching window.
Inventory and local backups
Record existing listening URLs, bitrates, peak concurrent listeners, storage use and encoders. List playlists, broadcast times with their time zone, broadcaster accounts and every website, app or directory using your stream URL.
Keep local backups of your audio files. Export settings and playlists where your current system allows it. Check the files are complete. An export does not establish that SPCast can import its format. Do not put passwords in public documents.
Prepare the destination
Choose listener capacity and storage from your inventory. The hosting overview separates included services from upgrades. AutoDJ accepts MP3 only; convert other files before uploading and retain the originals.
Start with a small playlist and the required broadcaster accounts in SPCast. Recreate a schedule only after checking times, time zone and playback. Automatic transfer of third-party playlists, accounts or settings is not part of this procedure.
Test in parallel
Follow the setup tutorial in the new environment while the existing stream remains available. Test AutoDJ, live connections, the return to AutoDJ and public outputs on the intended devices. Record which software, format and player combination works.
Agree with your team who may test the new stream. A test encoder may take over the programme in the new environment. Use headphones and include monitoring devices when checking listener capacity.
Switch encoders, players and directories
- Save the existing encoder profile and create a separate SPCast profile. Copy new connection details from product management.
- Switch to the tested profile during the agreed window and listen to the public stream on a second device.
- Update website players, apps and directory listings with the new listening URLs. Test each integration after changing it.
- Tell your team which accounts to use. Check again after the next scheduled programme transition.
URLs owned by the previous provider do not automatically carry over. For domains you own, check which redirects you control. Directory and app changes may take time to appear; allow for that transition period.
Fallback and completion
Keep the old encoder profile and previous player settings available. Decide in advance which failures require a rollback and who makes that decision. After reverting, review any players and directory entries already changed.
Retire the old service only after the agreed checks and according to its contract terms. Use contact to clarify specific import formats or the scope of migration assistance. This guide does not promise automatic imports or a free, interruption-free migration.