Selling or Handing Over a FiveM Server: Asset Licences, Data and Keeping the Community Intact

Selling or Handing Over a FiveM Server: Asset Licences, Data and Keeping the Community Intact

The message always arrives around 2am. “im done bro, burnt out, do u want the server?” Twenty minutes later a folder of zip files lands in a DM with a database dump and a txAdmin password, and the new owner spends three weeks discovering that half of what he thought he bought is still attached to the guy who left. If you plan to sell a FiveM server, or to accept one from a friend who has had enough, the handover is closer to inheriting a restaurant where the recipes belong to the chef and the lease is in someone else’s name.

This is the checklist nobody writes down until after it has gone wrong: what transfers, what quietly does not, who owns the custom code, what happens to player data and staff, how to structure the money, and how to tell the community without a third of it leaving.

What do you actually own when you sell a FiveM server?

Start with the uncomfortable part. Three of the most valuable things attached to your city are not possessions at all, they are entitlements sitting on a Cfx.re account with your email on it.

The server key is the easy one. It gets generated in the Cfx Portal, dropped into server.cfg as sv_licenseKey, and costs nothing, so the buyer should make their own. Emailing someone your Cfx login so they can “just use yours” is how a bad month later ends with both of you locked out of the same account.

The Element Club subscription bills against whoever’s card is on file and does not come with the box. If your city streams custom clothing and needs a subscription to stay public, put that gap in the plan rather than finding it on cutover night.

Then the one that actually costs people money. Assets bought through FiveM’s escrow system are licensed to the Cfx.re account that bought them and decrypt at runtime against a key belonging to that account. Move the server onto somebody else’s key and those resources stop starting, no matter that the encrypted files sit on the disk you just paid for. If that mechanism is fuzzy, read how asset escrow ties a purchase to a Cfx.re account before agreeing a price with anyone.

What is genuinely for sale, then, is a community, some infrastructure and whatever code is truly yours. That is still worth real money. Just do not price it as though forty escrowed scripts come along for the ride.

The handover inventory: what transfers, what does not, and who wrote it

Build this list before a number is mentioned. After is when the number becomes a negotiation about your honesty.

• Every domain, which registrar holds it, and who controls the DNS.
• The game box, the database host, and wherever the backups actually live.
• The Tebex store and the gateway behind it. That gateway is tied to a verified business identity and does not transfer, and chargebacks on old orders keep landing on the seller for months.
• The Discord server, plus every bot, webhook and developer application pointed at it.
• The database, and an honest account of what is in it.
• The resources folder, split three ways: escrow-locked, purchased but open, and written in house.
• The listing entry, the socials, and the YouTube channel with four years of trailers on it.

That third pile is the one people guess at. Stop guessing, because escrow-protected resources announce themselves with a .fxap file at the resource root:

find resources -name '.fxap'

That is the exact list of things that break the moment the server key changes hands. Note the vendor for each and whether they will re-issue to a new account. Some will, plenty of licences say non-transferable in plain English, and a few sellers went quiet years ago. Ask before you promise a buyer anything.

Now the part that surprises owners: the custom scripts you commissioned are probably not yours either. In most countries the person who wrote the code holds the copyright unless something written says otherwise, so paying an invoice usually buys a licence to use it rather than the copyright itself. A contractor who built your custom MDT for two hundred quid in a Discord DM is not the same as an employee, and almost every custom FiveM script is the contractor. Get one line in writing from each developer: they assign their rights in that resource to you and are fine with it moving to a new owner. Most agree instantly. One or two will want paying, and better to learn that now than in front of a buyer.

While you are in there, be honest about anything that came from a “free release” thread. Reskinned leaks travel with the server, and so does the takedown risk. Read the fxmanifest.lua author fields and tell the buyer what you find.

What happens to player data when the server changes hands?

Your database holds more than character positions and bank balances. There are identifiers such as license:, steam: and discord:, sometimes IP addresses, ban records with the reasons written out, staff notes on individual players, and if a store is wired in, purchase history and email addresses.

A change of ownership is a change of who controls that data, and privacy law does not care that this is a video game. If your players are in the UK or the EU you need a lawful basis to keep processing their information, and they are entitled to be told the server changed hands and who runs it now. That is a paragraph in your Discord and an updated contact on your rules page, not a legal project.

The practical rule: do not hand over data you never told players you would share. Ban appeals stuffed with real names and photos of somebody’s ID get deleted, not transferred. Store customer records generally sit with Tebex as merchant of record, so exporting a CSV of buyer emails as a bonus is a bad idea dressed up as generosity. Transfer what the city needs and bin the rest on the way out.

Why your staff team can walk on day one

Staff are not an asset on the inventory. They are volunteers who signed up to work for you, and a new owner is a stranger with opinions about their permissions. Losing them in one evening is the fastest way to turn a sale into a dead server, because the moderators are the reason anything runs on a Saturday night.

Tell them before you tell the players, and before you sign anything. Learning that your own community has been sold from a public announcement is rotten, and people who feel that way take their friends with them. Give the buyer a real conversation with the admin team, let staff ask whether their roles survive, and accept that some leave anyway. A buyer who understands how a FiveM staff team is actually structured and kept treats that meeting as the most important part of the deal, because it is.

Treat the handover as an access event in both directions: departing staff come off the admin lists on the same day as the departing owner.

How to structure the payment and the handover window

FiveM uses the word escrow for asset DRM. The rest of the world uses it for holding money safely, and that second kind, the one that would actually protect you here, is the kind FiveM does not provide. Confusing them is an expensive way to learn vocabulary.

Split the payment three ways: a deposit when access starts moving, the bulk once the buyer has personally logged into the registrar, the hosting panel, the store and the Discord with their own credentials, and a fifth held back for thirty days while the seller stays contactable. If the sum matters, park the funds with a neutral third party instead of wiring money to a stranger on the promise of a button being clicked. PayPal friends and family protects neither side, which is precisely why it gets suggested.

Write the boring document too: what is included, what is excluded with the escrowed resources named line by line, how long the seller stays available for questions (two to four weeks is normal and worth paying for), and what happens to money already taken for perks not yet delivered. That last one starts more arguments than the sale price. If eighty players bought a three month priority package last week, somebody decides who honours it before the announcement, not after the first refund request.

Telling players without starting an exodus

Players rarely leave because ownership changed. They leave because they heard it as a rumour and concluded the city was dying. Control the sequence and you control most of the damage: staff first, then a joint announcement from both names on the day access actually moves. Not a fortnight early, not a month late.

Answer the four questions everyone is silently asking. Are characters and money being wiped. Are existing perks still honoured. Are the rules or the whitelist changing. Do the Discord and the connect address stay the same. Say all four out loud and most of the panic never forms. Skip them and your general chat writes worse answers for you within the hour.

Then the old owner should say goodbye properly and actually go. A predecessor who lingers in the staff channel second-guessing every decision does more harm than a clean exit ever could. Resist the “big changes coming soon” teaser too, which reads to a nervous community as a threat and to a rival recruiter as an invitation.

The three ways a FiveM server handover goes wrong

Nearly every horror story is one of these three.

The seller keeps a way back in. Occasionally malicious, usually just leftovers: an ACE principal on an old identifier, a txAdmin account nobody removed, a personal SSH key, a webhook still posting into a Discord the seller owns, or a resource with a hardcoded admin check on one licence identifier. Rotate everything on day one, and read the permission lines rather than skimming them:

grep -nE "add_principal|add_ace" server.cfg

The same discipline applies to anyone leaving the staff team during the transition, which is why this is worth thinking about as an insider access problem rather than a paperwork problem.

The buyer discovers the assets do not transfer. This surfaces in week two, when the entitlements stay with the old account and a stack of resources refuse to start. Name those resources in the agreement, price the deal as though they are excluded, and have the buyer re-purchase the ones the city cannot run without before completion rather than after.

Discord ownership never actually moves. Transferring a Discord server requires two-factor authentication on the current owner’s account, and plenty of handovers stall right there. Administrator permissions are not ownership, and whoever holds ownership can remove everyone else on a whim. Verify properly: the new owner opens their own server settings and confirms it. Bots are a second trap, because those applications live in the seller’s developer account, so re-create them rather than borrowing them forever.

Handing the server to your own staff instead of selling it

The handover that works most often has no money in it at all. You give the city to the people already running it. They know the rules, the players trust them, and the staff team survives the transition because the staff team is the transition.

Do the same inventory anyway. Succession fails for the reasons a sale fails: the domain is still on the founder’s registrar account, the payouts still land in the founder’s bank, and the one person who knew the database password went travelling. If revenue is involved, the new owner needs their own store and gateway live before the old one switches off, plus a date after which you stop taking payouts for a city you no longer run.

Do it gradually. Make them co-owner for a month with real access rather than the ceremonial kind, hand over the money side next, then step back and stay quiet. The honest test is whether you can disappear for two weeks and come back to nothing on fire. If you can, the handover already happened and the rest is paperwork.

Burnout is a terrible time to make permanent decisions, which is unfortunately when most of these transfers happen. If you are at the 2am DM stage, build the inventory first, in daylight, while you still care enough to be accurate: one column for what transfers, one for what dies with your account, one for what needs somebody’s written permission. Whether it ends in a sale, a succession or a fortnight off, that document is the difference between handing over a city and handing over a folder of zip files.