Skip to Content
Director GuideDownload Registrations

Downloading Registrations

Before you can pair your tournament in SwissSys, you need to get your registered players out of ChessRoster. The export produces a SwissSys-compatible file (.sjson) that you open directly in SwissSys to start pairing.

Prerequisites

  • You must be logged in as a tournament director or organizer admin.
  • The export only includes players with a Completed registration status. Pending payments, incomplete registrations, and withdrawn players are excluded automatically.

How to Export

Open the tournament page

Navigate to your tournament on chessroster.com  and open its detail page.

Find the organizer tools bar

A subtle admin bar with a primary-color left border appears at the top of the page for users with director access. Choose Download SwissSys file in the bar. On narrow screens it is inside the three-dot menu (⋮) on the right side of the bar.

Select “Download SwissSys file”

Choose Download SwissSys file. A dialog opens with an Export Format dropdown — SwissSys 11 (SJSON) is currently the only option.

Click Export

If you want SwissSys to show each player’s official name, tick Use USCF names (replaces registration name with USCF name for players with a valid USCF ID). Players without a valid USCF ID keep their registration name.

The Export Tournament dialog with the SwissSys 11 (SJSON) format, the Use USCF names checkbox, and the Cancel and Export buttons

Click Export. Your browser downloads a .sjson file named after your tournament.

Open in SwissSys

In SwissSys, use File → Open and select the downloaded .sjson file. Your tournament sections and players load automatically.

What the Export Contains

For ordinary player formats, the file includes one record per completed player, organized by section. In Teams Only Fixed Roster with Team roster registration, it exports one whole-team competitor per complete roster instead of the individual member rows. The members retain their own registrations, payments and financial records in ChessRoster. Fields included depend on what data was collected at registration:

FieldSource
Player nameRegistration form (formatted for SwissSys)
Rating / Pairing numberRegistration rating, sorted by rating descending
Primary federation IDUSCF ID (USCF events), CFC ID (CFC-only events), or FIDE ID
Secondary federation IDFIDE ID (if available alongside primary)
Membership expirationUSCF or CFC expiration date
Chess titleGM, WGM, IM, WIM, FM, WFM, CM, NM (if on record)
Sex / GenderFrom USCF or CFC player data
State / ProvinceFrom USCF or CFC player data
EmailFrom registration
PhoneFrom registration
TeamRoster or label affiliation, or a mapped answer; uploaded codes are used for matching names
ClubFrom custom registration questions (if configured); uploaded Club codes are used for matching names, otherwise the answer uppercased
Birth dateA full date of birth on record, else a question mapped to Birth date, else a birth year; a year-only value is written as YYYY
City, Zip, AgeFrom custom registration questions (if configured)
Reserved byesHalf-point and zero-point bye requests
Section assignmentMatches the section selected at registration

Only players with a Completed registration status who have not withdrawn are included. Players who started but did not finish registration, who have pending payments, or who have withdrawn are excluded automatically.

Team Rosters and Question Scope

Completed rosters supply their team name, code, rating and member board assignments to pairing and export. Explicit board assignments take precedence; initial unset boards are assigned by rating. Review later board changes before exporting. Forming-team reservations are not completed players.

Mapped Team questions use the answer saved once on the team profile. Mapped Player questions use each player’s registration answer. A team label identifies a player’s school or club without creating a captain or reserved roster seats. See Team Registration for registration modes and format choices.

Team Codes and Names

When an organizer uploads a list for a registration question mapped to Team, players select the team name and the export uses the supplied code, uppercased. SwissSys uses that code to identify the team and keeps the uploaded name as its display name. The same team receives the same code across sections.

Team names without a matching uploaded entry receive generated codes that are unique across the tournament, including against uploaded codes. This prevents different teams in separate sections from sharing an export code before you merge sections in SwissSys.

See Upload Team Codes for SwissSys to configure the list. This correction is in ChessRoster and does not require a SwissSys update; the existing file-format version requirement still applies.

Club Codes

A question mapped to Club can use an uploaded Code and Name list too. The export matches the player’s answer to the list by name, then by code, and writes your supplied code, uppercased. See Upload Club Codes for SwissSys.

Birth Date Precision

The Birth date column uses the most precise value available: a full date of birth (YYYY-MM-DD), then a mapped registration answer, then a birth year. If only a year is known, the file contains just YYYY; ChessRoster does not invent a month or day.

After Importing

Once you have opened the file in SwissSys, you can begin pairing as normal. After each round, sync your tournament back to ChessRoster — or upload a web report — so players see live results and standings.

Troubleshooting

The Download SwissSys file option is not visible.

You need tournament director or organizer admin access. The admin bar only appears for users with edit permission. Contact your organizer admin to confirm your role.

A player I expected is missing from the file.

The export includes only completed entries appropriate to the pairing format. Open the tournament management page and check the Registrations tab to confirm payment and completion. Pending payments or incomplete forms exclude a player. In roster Teams Only Fixed Roster, look for the complete team competitor rather than individual members; review team completion on the Teams tab.

The export reports conflicting Team codes or names.

The error identifies the affected registration questions and sections. Ask an organizer administrator to edit those questions’ uploaded Team lists: give different teams different codes, and use one code for the same team across all sections. Re-upload the corrected lists, save the tournament, then export again. See Resolve Conflicting Team Codes.

The export shows “Some teams are not in this file yet”.

The export still downloaded, but the warning lists teams that could not be included, with a reason for each. Fix the listed teams (for example, finish their rosters) and choose Export again after fixing these teams.

The export reports a conflicting Club code.

One club name in an uploaded Club list has two different codes. The message names the registration question and its sections. Edit that question’s Club list so each club has one code, re-upload it, save the tournament, and export again. See Upload Club Codes for SwissSys.

SwissSys does not recognize the file.

Ensure you are using SwissSys version 11.74 or later. Older versions do not support the .sjson format.