Move From txAdmin

If your server has run on txAdmin, you do not have to start your history again. The project owner can upload txAdmin’s database backup, and MonoAdmin brings over the players, their bans, their warnings, the note txAdmin kept for each of them and your whitelist. You read a preview of what the file holds first, nothing is written until you confirm, and importing the same file again is safe.

This page covers how to get the file, what is and is not imported, how to run the import, how it combines with players MonoAdmin already knows, and what works differently from txAdmin afterwards.

Only the project owner can import. No role can be given it, and the screen does not appear for other members. Starting the import may ask you to confirm it is you again.

Get the File From txAdmin

In txAdmin, open Master Actions and choose Backup Database. Your browser downloads a file named playersDB.json. That file is everything MonoAdmin needs.

If you cannot reach txAdmin’s web page, the same database is on the server machine at txData/<profile>/data/playersDB.json, where <profile> is the name of your txAdmin profile.

• Backups from txAdmin 5.2 and later are accepted: their database version is 3, 4 or 5 (txAdmin 8 still writes version 5). The panel refuses any other version and says so.
• The file can be up to 512 MB of JSON. Your browser compresses it before sending it, and the upload can be up to 64 MB once compressed. A larger file is refused.
• No single entry of the file can be over 1 MiB. An entry here is one player’s record, one ban or warning, one note, or any other single value in the file. A file with an entry over the limit is refused as a whole.
• Reading the file has a time limit of 90 seconds. A file that is too large or too tangled to read in that time is refused.

What Is Imported

From txAdmin	What arrives in MonoAdmin
Players	The name, identifiers, hardware tokens, first seen, last seen and playtime. txAdmin keeps no name history, so only the name it has now comes across.
Bans	Active, expired and revoked bans, each with its reason, its end time and the name of the txAdmin admin who issued it. A revoked ban also keeps who revoked it and when.
Warnings	Each with its reason and the admin’s name. A revoked warning stays revoked.
Notes	The one note txAdmin keeps for a player becomes a staff note, in the General category. It is written by the txAdmin admin who last edited it, and dated from that edit. Each line of the note becomes a paragraph.
Whitelist	Players txAdmin marks as whitelisted and people it approved who have not joined yet go on the approved list. Requests still waiting for an answer become requests, keeping their Whitelist IDs. See below.

The Whitelist

txAdmin keeps its whitelist in two places: a player who has joined since being approved is marked as whitelisted on their record, and an approval for someone who has not joined yet waits in a separate list. The import reads both, and the requests waiting for a decision.

• Whitelisted players go on the approved list by their Rockstar license. The entry shows the name txAdmin saved, the source From txAdmin and “txAdmin” as who added it.
• Approvals go on the approved list by the identifier txAdmin has for them, when it is a kind the approved list holds: license, license 2, Cfx.re account, Discord, Steam, Live or Xbox Live. Any other approval is skipped, and the preview counts it with the skipped rows. The entry shows the name txAdmin saved, the txAdmin admin who approved it and the date they approved it.
• Requests become requests, with the Whitelist ID txAdmin gave them, so a player who was told R7KQM is still R7KQM on MonoAdmin. The application page needs the player’s own link, with a key in it, which they are given the next time they try to join; the ID alone does not open it. An ID that is not in the right format gets a new one. If another player in your project already has the same ID, the request gets a new one and the result counts it as renumbered. A player who already has a request is counted as already imported.
• Entries already on your approved list are not added twice.
• Your whitelist mode is not changed. The import fills the lists and tells your game server nothing. Choosing a mode is your decision, under Settings > Whitelist. See Whitelist.

What Is Not Imported

From txAdmin	Why
Kicks	txAdmin does not keep them.
txAdmin’s logs, admins and settings	MonoAdmin brings over player data only. Your txAdmin admins are not turned into MonoAdmin members: their names come across only as text on the bans, warnings and notes they wrote. Your txAdmin Allowlist Mode is not imported either: you choose MonoAdmin’s mode yourself.

Run the Import

1. Open Settings > Import from txAdmin. The last screen of the guided setup has a Coming from txAdmin? link to the same place.
2. Drop playersDB.json on the screen, or choose it from your computer. The file is compressed in your browser and sent, and MonoAdmin reads it and builds a preview. Nothing is added to your players or punishments yet.
3. Read the preview (below).
4. Press the confirm button. It names what will happen, such as how many players and active bans will be imported. If you have not confirmed it is you recently, the Confirm It’s You window asks for your password, plus a code from your authenticator app if two-factor is on. Then the import is queued.
5. Wait. The import runs on MonoAdmin’s side in small batches, and the screen shows a progress bar. You can leave the page and come back: the import carries on.
6. When it finishes, the screen shows how many players, bans, warnings and notes were written, how many whitelist entries and requests were added (and how many requests had to be renumbered, when there were any), and a short message tells you it is done. Every import stays in a history list at the bottom of the screen, with its file name, who ran it, when and the key counts.

Choose Discard instead of confirming to throw the upload away. Nothing was written, so nothing is undone. An upload that nobody starts is discarded after 24 hours, and the screen shows the time. Uploading a new file replaces the earlier upload that was never started.

Read the Preview

The preview is worked out against your project’s current data when you upload, so it tells you what would happen, not only what the file holds:

• Players: how many are new to your project and how many MonoAdmin already knows.
• Bans: how many are active, expired and revoked.
• Warnings and Notes.
• Already imported: bans, warnings and notes that an earlier import brought in. They are skipped.
• Revocations to apply: bans you imported before that the file now shows as revoked in txAdmin.
• Identifiers dropped: a player keeps at most 64 account identifiers and 96 hardware tokens, counting everything MonoAdmin already holds for them from the game and from earlier imports. A player with an unusually long list keeps the first ones, and the preview counts what the file itself would leave out as Identifiers beyond the limit. A value MonoAdmin already holds is never removed to make room.
• Whitelist: “{n} whitelisted players and {m} pending requests will be added. Your whitelist mode isn’t changed.” The first number counts the entries that are not on your approved list yet. The second counts the requests from players who have none yet.
• Skipped rows, each with the reason in words: an entry with no identifier MonoAdmin can match on, an entry that is not shaped the way txAdmin writes it (this includes a whitelist approval of a kind the approved list cannot hold), or an action that is neither a ban nor a warning.

Stop an Import

Choose Stop while an import is running, and confirm. It stops after the batch it is on, and what was imported so far stays. To finish the work, upload the same file again: what is already there is skipped. An import that fails partway behaves the same way.

Only one import can be queued or running in a project at a time. You can upload a file while another import runs, but starting the new one is refused until the other one ends.

Importing Again

You can import a newer backup whenever you like, for example after txAdmin has gained bans since the first import. It works as a sync:

• Players are merged again, as described below.
• Whitelist entries already on your approved list, and requests from players who already have one, are skipped.
• Bans, warnings and notes imported before are recognised by their txAdmin reference and skipped, so nothing doubles. A note you changed in txAdmin after the first import is not imported a second time.
• A ban you imported earlier and have since revoked in txAdmin is revoked in MonoAdmin too, and the change is pushed to your server.

How Players Are Merged

MonoAdmin recognises a txAdmin player by their Rockstar license. If your project already has that player, the two records are combined:

Part of the record	What the merged player keeps
Name	The name MonoAdmin already has.
First seen	The earlier of the two dates.
Last seen	The later of the two dates.
Playtime	The larger total. txAdmin usually runs the same server, so its total already includes the time MonoAdmin has seen.
Identifiers and hardware tokens	Everything MonoAdmin already has, plus txAdmin’s new values, up to 64 account identifiers and 96 hardware tokens in all. Values that are already there only get their dates refreshed. What would go past the limits is left out and counted. Nothing MonoAdmin already holds is removed.

A ban or warning belongs to the player whose license is on it. If it has none, MonoAdmin looks for a player who already holds one of its other account identifiers, and if there is none, it creates a player from the identifiers on the entry. That player is named as txAdmin saved the name, or after the identifier when txAdmin saved only an ID. An entry with no usable identifier at all is skipped, and the preview counts it.

What Works Differently

• Ban type. Every imported ban takes your project’s Default ban from Settings > Overview: sticky or not sticky. Check it before you import. Sticky Bans and Linked Accounts explains the two. With Sticky, an imported ban holds the identifiers and hardware tokens txAdmin kept with it. With Not sticky, it holds only the account identifiers, like a ban that is not sticky made in the panel. MonoAdmin does not add linked accounts at import.
• Hardware tokens. On a sticky ban, catching someone on hardware tokens alone needs two matching tokens in MonoAdmin. txAdmin’s default is one. A player txAdmin caught on a single token can therefore get through, unless an account identifier matches too.
• Linked accounts. MonoAdmin works out links between players as they join, not at import. An imported player’s Linked tab fills in over time.
• Warnings. Imported warnings are stored as finished, so players are not shown them when they join. txAdmin still shows its own pending warnings while it runs.
• Names and tags. The Issued by line of an imported ban or warning shows the txAdmin admin’s name as plain text, because it is not tied to a MonoAdmin member. An entry that has no admin name shows “txAdmin”. Imported bans, warnings and notes carry a From txAdmin tag.
• The whitelist stays as you set it. Importing never turns it on or changes its mode, so who can join does not change until you choose a mode under Settings > Whitelist. Imported entries carry a From txAdmin tag on the approved list.
• Nothing is announced. Importing sends no live notices or Discord messages for each item and adds nothing to Staff Activity scores. Audit Logs gets one entry when the import starts and one when it finishes.

Running Both

txAdmin keeps its own bans and its whitelist for as long as it runs, and importing changes nothing in txAdmin. MonoAdmin enforces its own copy. The two do not stay in step by themselves: a ban issued in one tool is not sent to the other. If you keep txAdmin running, lift a ban in both places when you want it gone, and import again when you want MonoAdmin to catch up with txAdmin.

The whitelists need care. If txAdmin’s allowlist and MonoAdmin’s whitelist are both on, a player has to pass both. In txAdmin, open Settings > Allowlist and set Allowlist Mode to External Allowlist Resource (or Disabled), so that MonoAdmin’s whitelist is the only check. MonoAdmin warns you when it thinks txAdmin’s allowlist is on. See Whitelist.

If the Import Is Refused

What you see	Why	What to do
The file is not a txAdmin database backup (playersDB.json)	The file is not JSON, or it lacks the lists of players and actions txAdmin writes	Download the file again from Master Actions > Backup Database, and upload that file unchanged.
The database version is not supported	MonoAdmin reads versions 3, 4 and 5 only, and refuses a newer version it has not seen	Contact MonoAdmin support at hello@monoadmin.net if your txAdmin is a current release.
That file is too large to import. The limit is 512 MB for the file, and 64 MB once it is compressed.	The file is over 512 MB of JSON or 64 MB compressed	The panel refuses a file over the limits before sending when it can. Download a fresh backup from Master Actions > Backup Database rather than a copy that was edited or damaged. If it is refused again, contact MonoAdmin support at hello@monoadmin.net.
Part of that file is too large to import	One entry of the file is over 1 MB, which a backup txAdmin wrote does not have	Download a fresh backup from Master Actions > Backup Database and upload it unchanged. If it is refused again, contact MonoAdmin support at hello@monoadmin.net.
Reading that file took too long	Reading the file took longer than 90 seconds	Download a fresh backup and try again. If it is refused again, contact MonoAdmin support at hello@monoadmin.net.
Another import is running, or another file of this project is being read	One import runs at a time, and only one file is read at a time	Wait for it to finish and try again.

For where the uploaded file is kept and for how long, see Data, Privacy and Retention. If bans do not seem to work after an import, start with Troubleshooting.