Import from RDCMan, mRemoteNG, or Royal TS

If you’re already running another connection manager, RDPMaster can import your profiles. The import covers the fields RDPMaster knows about (host, port, username, domain, display name, group). Per-tool quirks below.

Microsoft RDCMan (.rdg files)

RDCMan is the closest match to RDPMaster’s data model and the cleanest import.

1. In RDCMan, open the group or root containing the connections you want.
2. File → Save As → .rdg. RDCMan writes an XML file.
3. In RDPMaster: Settings → Import → From RDCMan. Browse to the .rdg file. Click Import.

A preview shows every profile that will be added (with conflicts highlighted if the display name already exists). Click Confirm to commit, Cancel to abort.

Passwords are NOT imported — RDCMan stores them encrypted in a way that’s tied to the RDCMan binary, which is licensed differently. You’ll re-enter passwords on first connect; RDPMaster then saves them to Credential Manager.

mRemoteNG (.xml files)

mRemoteNG’s confCons.xml format includes credentials encrypted with the (now-CVE’d) mRemoteNG static key. RDPMaster’s importer extracts username, domain, host, port, display name, and group — not the password — and discards the encrypted credential blob entirely.

1. In mRemoteNG, File → Export → Save as XML. Confirm the location.
2. RDPMaster: Settings → Import → From mRemoteNG. Pick the .xml. Click Import.

If you have hundreds of connections, the preview gets long — there’s a search box at the top.

Royal TS (.rtsz archive or exported .json)

Royal TS doesn’t expose a plain XML, but you can export a subset of connections to JSON:

1. In Royal TS, select the connections you want to export.
2. Right-click → Export → JSON (selected items). Pick a destination.
3. RDPMaster: Settings → Import → From Royal TS JSON. Pick the file.

The importer maps Royal TS’s Connections[].Host, Connections[].Port, Connections[].Username, Connections[].Domain, Connections[].Name to RDPMaster’s profile fields. Any Royal TS dynamic credential references (e.g. credentials inherited from a vault) drop on import — you’ll set credentials manually after import.

Generic CSV

If your existing tool isn’t listed, dump your connections to CSV with these column headers (case-insensitive, order doesn’t matter):

DisplayName,Host,Port,UserName,Domain,Group
Web server,10.0.0.42,3389,administrator,,Production
Lab box,labbox.example.com,3389,labadmin,LAB,Lab

Then Settings → Import → From CSV.

What gets preserved across imports

Field	RDCMan	mRemoteNG	Royal TS	CSV
Display name	✅	✅	✅	✅
Host	✅	✅	✅	✅
Port	✅	✅	✅	✅
Username	✅	✅	✅	✅
Domain	✅	✅	✅	✅
Group	✅	✅	partial	✅
Password	❌	❌	❌	❌
RD Gateway settings	✅	partial	partial	❌
Custom display res	❌	❌	❌	❌
Redirects (drives/audio/etc)	❌	❌	❌	❌

Passwords always require re-entry on first connect for security reasons. Custom display resolution, redirects, and per-connection RD Gateway settings are set to the RDPMaster default on import — adjust them per-profile after import if needed.

Reverse direction

We don’t currently export back to RDCMan / mRemoteNG / Royal TS formats. If you need to leave RDPMaster, copy %APPDATA%\RDPMaster\profiles.json — it’s plain readable JSON.