Moving to a new panel without your customers noticing

By the Minimus team · · 3 min read

The copy is rarely what goes wrong in a panel move. The cleanup afterwards is: customers whose apps saved the old link, resellers who can't find their credits, films pointing at a server that isn't there any more.

All of it is avoidable, and it's the same short list every time.

What your customers actually notice

Customers don't care which panel you run. They notice whether their login still works, whether the link saved in their app still works, and whether the evening you switched was the evening everything buffered.

Resellers notice one more thing: whether their customers, credits and prices came across.

Plan around those first.

Before you move anything

Lower the TTL on your DNS records a few days ahead. If your panel's address has a TTL of a day, a change can take a day to reach everyone, and so can changing it back. Drop it to five minutes well before the move.

Write down what your customers' links look like today: the host name, the port and the path. The new panel has to answer exactly the same links, or every saved playlist breaks at once. If the old one used port 8080, the new one needs to as well.

Find out what the old panel can give you. Some can be read over SSH, some give you a backup file, some only have an API. Know which before you start, because it decides how the copy works and how long it takes.

And take a full backup of the old panel, kept somewhere the move can't touch.

Copy while the old panel keeps serving

Don't switch anything off to make the copy. Channels, categories, packages, films and series, customer accounts with their passwords and expiry dates, resellers with their credits: copy all of it while the old panel carries on serving everyone as normal.

Old Serving every customer Standing by New Copying, then testing Serving every customer 1. Copyold one still serves 2. Testa few real lines 3. Switchsame logins 4. Retireonce it's quiet
The old panel never stops serving until the new one has taken over.

Passwords are the usual trap. If the new panel can't take the old ones as they are, every customer needs a new password, and that's exactly the support flood you're trying to avoid. Make sure logins come across unchanged.

Films and series are the other one. If they sit on your load balancers' disks, copying them somewhere else can take days. It's far better if the new panel can serve them from where they already are.

Test with real lines

Before you switch, pick a handful of real customer lines and try them against the new panel on the devices your customers use: a phone, a TV box, a browser. Check a live channel, a film, the TV guide and catch-up if you offer it. Sign in as a reseller too, and look at the credits.

Do it at the busy hour if you can. A panel that copes at noon might not at 9 pm.

The switch itself

Pick a quiet time, usually early morning in your customers' main time zone. Run one last copy so anything created since the first one comes across, point the addresses at the new panel, and watch.

Leave the old panel running, untouched, for a week. If something's wrong, you can point the addresses back in a few minutes, thanks to that low TTL, but only while the old servers are untouched, so reinstall load balancers last. Anything changed on the new panel in the meantime won't be on the old one.

After the move

Keep an eye on support messages for the first evening. A spike nearly always has one cause, with one answer for everyone. Once you're sure, put the DNS TTL back up. Then switch the old panel off.

How it works in Minimus

Moving in is one button in Minimus. You connect the old panel over SSH or with a database backup and press Move. It copies everything while the old panel keeps serving, keeps customers' usernames, passwords and links, brings resellers across with their credits, and lists anything it couldn't bring. A panel you can only reach through its API gives you the channels, films and series, but not the accounts. Boxes that need their own portal aren't supported yet. Films on your load balancers are served from where they already are. On one real panel it moved 62,145 films, 508,023 episodes and every customer account in about six minutes.

Lower the TTL and test a few real lines anyway; no tool does that part for you.

More from the blog