Tooladoo Free online tools for your files

Convert HY3 and CL2 files to Lenex (Beta)

Send entries or results from Hy-Tek to a SPLASH or EasyWk meet: HY3, CL2 and SDIF files become Lenex .lxf.

Opens: HY3, CL2, SD3, LXF, LEF, HYV, EV3, ZIP
Saves: XLSX, CSV, LXF, CL2, HY3

Convert

Meet file
Choose a file… or drop it here
.hy3, .cl2, .sd3, .sdi, .zip, .lxf, .lef, .xml, .hyv, .ev3, .txt · up to 150 MB
    Replace file

    A Hy-Tek export (.hy3, .cl2 or the .zip Meet Manager makes), an SDIF file (.sd3), a Lenex file (.lxf / .lef from SPLASH, EasyWk or swimrankings) or a meet event file (.hyv / .ev3).

    Options

    The preview, validation report and meet summary are always shown.

    More options

    Team code or part of the team name, e.g. NCAP. Leave empty for all teams.

    For sharing results publicly. Lenex output then uses 1 January of the matching year.

    Hy-Tek stores names in Windows-1252 (é, ü, ñ). Untick for plain ASCII (Muller instead of Müller).

    HY3 files don't store the meet's country. Empty = from the team addresses, else USA.

    HY3 files don't store the meet's city, which Lenex requires. Leave empty when the source file has it.

    Your files are deleted after processing.

    SPLASH Meet Manager, EasyWk and swimrankings.net work with Lenex files, while Hy-Tek's software exports HY3 or SDIF. When a Hy-Tek club enters a meet hosted with SPLASH, or Hy-Tek results must reach a Lenex-based system, this page converts .hy3, .cl2 or .sd3 files into Lenex 3.0.

    How to convert HY3 to Lenex

    1. Upload the Hy-Tek export: an .hy3 with entries or results, a .cl2, or Hy-Tek's .zip.
    2. Convert to is preset to Lenex .lxf.
    3. Open More options and fill in Meet city for Lenex. HY3 files don't store the city, but Lenex requires it. Set Nation for Lenex (a three-letter IOC code such as USA or CAN) if the guess from the team addresses would be wrong.
    4. Download the .lxf, a zipped Lenex file, and import or send it as the meet host asks.

    What Lenex needs that Hy-Tek files may lack

    • Meet city: missing from HY3; without the option, the result warns you.
    • Birth dates: Lenex requires one per swimmer. US exports often contain only ages for privacy; then 1 January of the matching year is used, which gives the right age for age groups based on the year of birth. The same happens if you tick Remove birth dates.
    • Whole event numbers: Hy-Tek allows lettered events such as 2C or 26A, Lenex doesn't. They get free whole numbers, and the warning shows the mapping, for example 2C → 9, so you can match them to the host's event list.
    • Diving: Lenex has no diving events. They are left out, with a warning.

    Names and sessions

    Swimmers are written with their legal first name, because federations match registrations on legal names; a preferred name from HY3 isn't used. Events are grouped into one session per meet day. When a multi-day meet has no dates on its events, everything lands in one session and the result says so.

    Checks

    Every Lenex file is checked by a validator built from the Lenex 3.0 documentation, and anything missing, such as the city, is reported. Conversions of real Hy-Tek files were compared field by field with the source. Imports into SPLASH or EasyWk couldn't be tested, so keep your original export.

    Also useful

    • Only this team under More options exports a single club from a whole-meet file.
    • Everything under Convert to adds an Excel workbook for checking entries before sending.

    The reverse direction is covered by Lenex to SDIF.

    More about what this tool reads and writes: Swim Meet File Converter.

    More with Swim Meet File Converter