The safest way to transfer a Roblox game is to move the game itself, never the account, through Roblox's own ownership transfer, and to start it only after payment is secured. The buyer prepares a group they own and gives the seller a role in it that can publish games, the seller starts the transfer from Creator Hub, the buyer accepts it, and the buyer inspects the game inside the escrow inspection window. If the buyer raises no dispute, the funds are released automatically about 24 hours after that window ends. Share no passwords, cookies, or authentication codes at any point.
This is the procedure for the handover itself, written for both sides of a sale. The steps follow Roblox's game ownership transfer documentation, which is the authority on the mechanics. Check it before you start, because Roblox updates its interface and rules. For why the transfer is allowed and what it does not settle, read what the rules say about buying and selling Roblox games.
Before you start#
Roblox lists the prerequisites for both sides. Verify your email address, and upload any private module scripts and InsertService assets the game uses to the group that will receive it. If the game uses packages owned by a user instead of a group, you may need to recreate them or swap in packages the group owns.
Roblox also requires the person who starts the transfer to be able to publish games to the receiving group. In a sale, that means the buyer adds the seller's account to the buyer's group with a role that can publish games, and should remove that role once the handover is finished. A Roblox staff reply on the announcement thread says a role with "Edit & publish all group experiences" should be enough. Settle these items in the written agreement:
- The buyer owns the Roblox group that will receive the game. Roblox's steps move a game to a group, not to a personal account, and the seller can start the transfer only after the buyer has given the seller's account a role that can publish games there.
- The group exists well before transfer day. Developers reported in early 2025 that groups created days or weeks earlier were missing as a destination. On February 18, 2025, Roblox staff said a bug had kept some groups out of the dropdown and that fixes would roll out over the following days.
- The person who will release the game again meets Roblox's release requirements, such as the age check Roblox requires to release a game to ages 16 and up. They apply to release actions, and the game stays closed to the public until it is released again.
- Both sides agree which game is changing hands, by name, game ID, place ID, and URL, and exactly what else is included: source files, the community Discord, social accounts, and art assets. Roblox moves the game, not these.
- The seller exports analytics and records the monetization settings before the transfer, and the buyer keeps the figures they verified during diligence.
- API keys, webhooks, and outside services are listed, each with a named person responsible for re-issuing it.
- The timing avoids the game's busiest days, because the game is closed to the public and its servers shut down once the transfer is accepted.
- Payment is secured first. With escrow, that means the buyer has funded it and the platform shows it as funded. The buyer also sets aside time for the inspection that follows, because escrow's inspection window is limited.
The safe order#
The order matters more than any single step, because acquisition scams commonly depend on breaking it.
- Both sides sign the written agreement.
- Payment is secured. On Romarket, where escrow is used, the buyer funds Escrow.com and the seller waits for the funded status before touching anything.
- The seller starts the Roblox ownership transfer to the buyer's group.
- The buyer accepts it and sets up permissions in the group. The game stays closed to the public until its new owner releases it again.
- The buyer inspects the game against the agreement inside the inspection window.
- The buyer accepts the handover on the payment provider or reports a problem. If the buyer does neither, the payment is released automatically about 24 hours after the window ends. The agreement should say whether the game is re-released before or after payment is released.
If anyone pushes to change this order, treat the pressure as information about the deal.
For the seller: starting the transfer#
According to Roblox's documentation:
- Go to Creations in Creator Hub and choose the game.
- In the left navigation, open Publish Settings, then Game details.
- Select Initiate ownership transfer.
- Read the Transfer Details dialog carefully, acknowledge it, and select Next.
- Choose the group to transfer the game to. You must be able to publish games to that group, so the buyer has to give your account a publishing role in it first.
- Verify the transfer by entering the game name.
- Select Initiate transfer. The Content Settings page now shows the pending group.
You can keep editing the game until the receiving group accepts. Edits made before the group accepts carry over; edits made after it accepts, while Roblox processes the transfer, do not. To cancel a request that has not been accepted, use Cancel transfer request on the Content Settings page. A pending request expires after seven days.
For the buyer: accepting the transfer#
- Open the game page, either from the transfer request notification or from the overview link the seller sends you.
- Read the Transfer Details dialog carefully, acknowledge it, and select Next.
- Verify the transfer by entering the game name.
- Select Accept transfer.
- When the transfer completes, set up the permissions you need. Release the game to the public again once you are satisfied with the handover.
Accept only when the agreed payment state is in place. If you are paying through escrow, that is when the platform shows the escrow as funded. On Romarket, the deal workspace tracks the agreement, the escrow status, the transfer, and the inspection in one place.
What happens when the transfer is accepted#
Per Roblox's documentation, once the receiving group accepts, Roblox revokes the public's access to the game and closes all of its servers. The process typically completes in a few minutes but can take longer for complex games. Roblox also documents these effects:
- The game keeps its game ID, place ID, and URL.
- Roblox removes credit card information when a game is transferred.
- The receiving group gets the revenue from existing private server subscriptions, and that revenue does not follow any group or game revenue splitting. New subscriptions do respect splits.
- Discovery is not affected as long as the game's title stays the same, the new group owner is not a moderated account, and the game is released again. It can still be affected for up to 24 hours after the new owner releases the game.
- After receiving a transferred game, the new owner must wait 30 days before transferring it again.
Verify after the transfer#
The game stays closed to the public after the transfer, so the buyer can inspect it before the public sees it. The inspection is time-limited. Under Romarket's terms, the escrow inspection period defaults to 72 hours for a full purchase and can be set between 24 and 168 hours for a specific transaction, and if the buyer raises no dispute, funds are released automatically about 24 hours after it ends. Prepare these checks before transfer day, work through them inside the window, and report a problem before it closes instead of letting it lapse:
- The game is in the buyer's group, with the same game ID, place ID, and URL.
- The buyer can edit and publish every place in the game.
- Every pass, developer product, and badge from the listing is present, priced correctly, and works in a live test.
- Private modules and packages load, and nothing in the game reports missing assets.
- The buyer can see analytics and monetization settings, and revenue is going to the intended group.
- API keys are re-issued where needed, and old credentials are retired.
- The seller and any former collaborators no longer hold access they should not keep.
- The off-platform items in the agreement have arrived: source files, the community server, social accounts, and art.
Then release the game to the public and watch players and revenue against the numbers you verified before the purchase.
Common mistakes#
- Transferring before payment is secured. Roblox documents cancelling a request that has not been accepted, but not reversing one that has, and the new owner cannot transfer the game again for 30 days.
- Moving the game into another group of your own first. A seller who does this receives a transferred game, and Roblox's 30-day wait before transferring it again then applies to the seller. Do it at least 30 days before the sale, or not at all.
- Treating a personal account as the destination. The transfer targets a group. Never offer a login in its place.
- Forgetting the pieces Roblox does not move. Private modules, packages, API keys, and outside services each need their own handover.
- Letting the request expire. A request that is not accepted within seven days lapses. Separately, a Roblox staff reply from January 28, 2025 says that after a denied or cancelled request the wait before another is 7 or 30 days, depending on the type of rejection. Line up both people before the seller starts.
- Accepting on a payment screenshot. Confirm the payment state with the payment provider or the platform, never an image.
- Running out the inspection window. If the buyer neither accepts nor reports a problem in time, the payment is released anyway.
Not legal advice
This page describes a process. The transfer is a technical mechanism: it does not settle ownership of IP, payment terms, or eligibility, which belong in the written agreement. For a significant deal, have a lawyer review that agreement, and check Roblox's current documentation before you start, because the steps and rules can change.
The checks that come before a handover are in the due diligence checklist, and the price side is covered in how to buy a Roblox game and how to sell a Roblox game.