Moving from alt:V or RAGE:MP to FiveM

If you ran a server on alt:V or RAGE:MP, the platform under it is gone. Not deprecated, not discouraged. Switched off.

This guide is about the part of the move that nobody plans for: your community's web presence. Your Discord survives a platform change. Your domain survives. Your search rankings survive, if you do not throw them away. The connect address does not, and everything that points at it has to be found and changed.

What actually happened

Rockstar's parent company, Take-Two Interactive, issued cease-and-desist orders to both remaining GTA V multiplayer platforms during 2026. The stated reason in both cases was the same: under Rockstar's Platform License Agreement, FiveM is the only authorized platform for GTA V multiplayer modding. Rockstar acquired Cfx.re, the organization behind FiveM, in 2023.

alt:V wound down in three stages and went fully offline on 6 July 2026. New server registrations and SDK access stopped on 2 March, and the public server list went dark on 4 May.

RAGE:MP followed the same shape, with a final date of 31 August 2026. Its public server list was wiped on 1 June, which is the date most players stopped being able to find servers at all.

Both teams pointed server owners at FiveM.

If you are reading this after those dates and your server still appears to work, that is residual infrastructure, not a reprieve. Plan as though it stops tomorrow, because it can.

The part that survives, and the part that does not

Worth being precise about, because it decides what you actually have to do.

Survives: your domain, your website, your Discord, your rules and lore, your staff, your search rankings, your community's memory of your name.

Does not survive: your connect address. On RAGE:MP that was a raw host:port. On FiveM it is a cfx.re/join/xxxxxx code instead, which is a different shape of thing entirely, and every place you published the old one is now a dead end.

Changes underneath you: anything on your site that queried the old platform's master list for a player count. That endpoint is gone or going, and a status widget pointed at it will either error or, worse, quietly render zero forever.

So the website work splits into three jobs: replace the address, repoint the live status, and keep the URLs people already have.

Get your cfx.re join code first

You cannot update any of the above until the FiveM server exists and has a code. Stand it up, even empty, before you touch the website.

Once it is running, your join code is the six characters in cfx.re/join/xxxxxx. You can read it from the server's own F8 console, or from your server listing. It is stable for the life of the server, so it is safe to hard-code in a config file and in your Discord.

If you have not met join codes before, they are covered properly in what a cfx.re join code is.

Replace every published copy of the old address

This is the tedious part and the part people half-finish. Make the list before you start changing things, because the address is usually in more places than anyone remembers:

• Your website: the join button, the footer, any "how to connect" page.
• Your Discord: channel topics, pinned messages, the welcome channel, any bot that posts status.
• Server listing sites you submitted to.
• Your YouTube and TikTok video descriptions.
• Forum signature and any forum threads advertising the server.
• Any printed or image asset with the address baked into it, which you will have to re-render rather than edit.

Search your own site's source for the old host and port as a literal string. It is usually in fewer places in the code than in the content.

Repoint the live status on your website

If your site showed a player count, it was calling the old platform's master list. That call has to be replaced with a FiveM one.

FiveM exposes per-server data through the Cfx.re infrastructure, keyed by your join code, and a whole-network player count separately. Neither is a formally documented public API, which is worth knowing before you build a hard dependency on it, and both are what every FiveM status widget in existence uses.

The mechanics of doing this well, including caching so you are not hitting the upstream once per visitor, are in showing live server status on your website.

If your site runs on RPWebsite, this is a configuration change rather than a code change: set the FiveM join code, and the status, the player list and the join button all follow.

Do not let your old URLs 404

This is the one with lasting consequences, and it is the one most often skipped.

If your move involves any URL changes at all, and it usually does, send the old URLs to the new ones with a permanent redirect rather than deleting them. A 301 tells search engines the page moved and passes the ranking along. A 404 tells them the page is gone and starts you from nothing.

The cases that matter:

• A page that changed address. Redirect the old path to the new one, one to one. Not everything to the homepage, which search engines treat as a soft 404 and which strands the visitor.
• A page about the old platform that no longer applies. If you had a "how to install RAGE:MP" page, redirect it to your FiveM equivalent. People are still searching for it and still landing on it.
• Your domain, if you are changing it. Do not. If you must, redirect the whole old domain at the new one and keep it registered for years, not months.

If your site is behind Cloudflare, redirect rules at the zone level handle all of this without touching your application.

Tell your players where you went

Obvious, and still worth a checklist, because a player who tries the old address once and gets nothing does not usually try twice.

• Put a banner on your website with the new join code, and leave it up for longer than feels necessary. Two months, not two weeks.
• Pin the change in Discord and re-pin it after a fortnight, when the first wave has scrolled away.
• Post it wherever your server was listed, as an update rather than a new listing where the platform allows it.
• If you ran any paid promotion or had streamer partners, tell them directly. Their videos and panels still carry the old address.

What to do with the work you are not moving

If your server was scripted for RAGE:MP or alt:V, the server-side code does not port. The frameworks are different and the APIs are different. That is a genuine loss and there is no way to soften it.

What does port is everything that was never platform-specific: your rules, your lore, your factions, your staff structure, your Discord, your brand, and your website. On FiveM you will be rebuilding the server on ESX or QBCore rather than on your own base, which is faster than what you did before even though it is not the thing you wanted to be doing.

The short checklist

1. Stand up the FiveM server and get its join code.
2. List every published copy of the old connect address, then replace them.
3. Repoint the live status widget on your website at FiveM.
4. Redirect every URL that moved, one to one, permanently.
5. Banner the change on the site and pin it in Discord, for two months.
6. Tell listing sites, streamers and anyone whose video description still has the old address in it.