Why player mapping matters

Tournament rows must connect to club members before the import can be committed. This is what keeps tournament history, league points, prizes, and profile stats attached to the right player.

How automatic matching works

The import tries to map every player row before you review it.

1. Exact club member id wins when provided.
2. Exact email wins when the email matches one club member.
3. Unique exact name is accepted when only one club member has that name.
4. Fuzzy name matches can be suggested, but you should review them carefully.

What the club member statuses mean

• Club member - the person already exists in the selected club.
• Will be invited - the email belongs to an existing platform user who is not yet in this club. The import creates an invited club membership.
• To be imported - the person is not already a club member and was not matched to an existing platform user by email. If an email is present, the import creates the user/member invite. If no email is present, the import creates a no-email guest member.

Imported members with an email address use the normal club invitation flow, so the invite email is sent by the existing club invite email webhook when that webhook is configured and enabled. No-email guest members cannot receive an invite email.

Using the Map Players step

1. Review each tournament player row.
2. Use the checkbox to decide whether the row should be imported.
3. Use the Club Member Picker to search by name or email.
4. If the row is wrong or should not be imported, uncheck it.
5. Continue only after every checked row is mapped.

The Club Member Picker includes existing club members and members that will be created from the file, including people without an email address.

Historical result imports

If a tournament has checked player rows with positions, the import treats that tournament as historical results.

• Position 1 becomes WINNER.
• Other positions become ELIMINATED.
• The tournament is created as CLOSED.
• Knockout timestamps are generated from the tournament end time so leaderboard placement logic works normally.

Knockout references

Knockout references are optional. Use knocked_out_by_email when possible, or knocked_out_by_name when email is not available. The value must match another checked player row in the same imported tournament. If it cannot be resolved, the import is blocked so the reference can be fixed or removed.

How prizes are preserved

For historical imports, the prize column is treated as the final amount paid to that player.

The importer creates fixed amount payout rows from the imported positions and prizes. This prevents normal percentage payout logic or rounding settings from changing the amounts after import.

For example, if your file says first place won 130, second place won 65, and third place won 20, those exact amounts are preserved.

When the import is blocked

• A required tournament field is missing.
• A player row references a tournament key that does not exist.
• A checked player row is not mapped.
• The same club member is mapped twice into the same tournament.
• A historical tournament has missing or duplicate positions.

If you imported the wrong file

The import tool does not currently replace an existing season automatically. If you imported the wrong file, delete the imported tournaments or manually correct the affected records, then import again.

Avoid importing the same spreadsheet twice into the same league unless you intentionally want duplicate tournaments.