Changing Your Server IP Without Losing Players

Changing your server's IP — a new VPS, a new host, a DDoS-forced move — is the moment a healthy community can quietly bleed out. Players have your old IP in their favorites and their muscle memory; when it stops answering, most do not go hunting for the new one. They just play somewhere else. The migration itself is easy; keeping the people is the real task. Here is how to move the address and carry the regulars with you.

1. Stand up the new server before touching the old one

Never migrate by tearing down first. Build the new server fully — same mod, same configs, same maps — and get it running and listed on the new IP while the old one is still live. Copy the whole config set across so the experience is identical: back up configs, bans and stats and restore them on the new box, including csstats.dat so ranks survive and users.ini/ban files so admins and bans carry over. A player who reconnects and finds their rank intact barely notices the move; one who finds a blank server feels like they lost their home.

2. Turn the old IP into a signpost

The players who will be lost are the ones who connect to the old IP and get nothing. So do not give them nothing. For as long as you control the old address, keep something there that points them onward. Two options:

• A redirect. The cleanest is a real connection redirect that bounces a joining client to the new address automatically — this is exactly the mechanism a boosting/redirect control plane provides, sending A2S queries and connections from the old endpoint to the live one.
• A message. If you cannot redirect, keep a bare server on the old IP whose hostname is the new address, so anyone who looks sees where to go:

hostname "MOVED -> connect 203.0.113.50:27015"

The worst outcome is a dead old IP that times out with no clue. Any signpost beats silence.

3. Re-register in the master list

A new IP is a new listing — the master list does not follow you. Confirm the new server appears: sv_lan 0, the correct ports open, and the heartbeat reaching the master, all covered in getting into the master list and fixing a server not in the master list. Until the new IP is listed, browsers cannot find you at all, so this is not optional — a migrated server that is not in the list is invisible to everyone who did not have the direct address.

4. Push the new address everywhere players look

Announce the move on every channel your community uses before and after the switch: your Discord, your website, and in-game on the old server while it is still up. On the new server, run an adverts plugin that repeats the connect address and your Discord in chat, so even a player who found you by luck can save the right place. Ask regulars to update their favorites — a one-time connect 203.0.113.50 and an "add to favorites" is all it takes, and reminding them is the single highest-return thing you can do during a move.

5. Keep the old IP alive as long as you can

Do not release the old address the day you migrate. The redirect or signpost on it is catching your slowest-returning regulars — the person who plays once a fortnight will hit the old IP weeks later. Hold it for as long as the host allows, ideally a month or more, so the long-tail of your community funnels across. Only when connections to the old address have dried up is it safe to let it go.

Common errors

• Regulars vanished after the move — the old IP went dark with no redirect or message. Always leave a signpost.
• New server not in the browser — it was never re-registered on the new IP. Re-check sv_lan 0, ports, and the heartbeat.
• Ranks and admins reset — you migrated configs but not csstats.dat, users.ini, or ban files. Copy the full data set.
• Released the old IP too soon — infrequent players still had it saved. Hold it for weeks.
• Announced only after the switch — players hit a dead server before they heard. Announce before, during, and after.

Verification

Before cutting over, connect to the new IP yourself and confirm the mod, maps, ranks, and admin access all behave exactly like the old server. Search the in-game browser for your hostname and confirm the new listing is present with a healthy ping. Then test the old address the way a returning player would — connect to the old IP and confirm you are redirected or clearly told where to go, not met with a timeout. When both the new listing works and the old address funnels players forward, the migration is safe to complete.