Import from JoomLeague 3

Import from the old JoomLeague for Joomla 3 must preserve historical data and transform it into a Joomla 6 compatible schema.

There are two supported ways to bring an old database into JoomLeague 6:

1. Online migration tool — converts a raw JoomLeague 3 SQL dump into a JoomLeague 6 compatible SQL file.
2. SQL import in the component — loads that converted SQL file into your site, table by table.

The usual flow is: run the online tool first, then import its output with the in-component tool.

1. Online migration tool

Address: migrate.klucon.cz

The tool takes an exported SQL dump of an old JoomLeague 3 database and returns a converted dump that matches the current JoomLeague 6 schema.

Steps

1. Export the old database (or just the #__joomleague_* tables) as an SQL file.
2. Open migrate.klucon.cz and upload the SQL file.
3. Wait for the phases to finish (provision, sanitize, import, migrate, validate, export).
4. Download the resulting ZIP with the converted migrated.sql.

What it does

• runs in an isolated, temporary staging database per job;
• normalises the table prefix to a neutral #__ placeholder;
• converts MyISAM to InnoDB and old charsets to utf8mb4;
• fixes zero/empty dates to NULL;
• maps old country values to the new country code dictionary;
• adds the tables and columns that only exist in JoomLeague 6;
• sets the target JoomLeague version on the migrated data.

Privacy

Each job uses its own temporary database that is dropped and deleted after the export. Uploaded data is not kept.

2. SQL import in the component

Location: JoomLeague → Dashboard → Tools → SQL import

This tool imports a JoomLeague SQL dump (for example the migrated.sql from the online tool) into the current site, one table at a time, with per-table progress.

Steps

1. Open JoomLeague → Dashboard → Tools → SQL import.
2. Choose the SQL file and click Analyse file.
3. Review the detected tables and their record counts.
4. Click Start import — each table is imported in turn and marked with a green check or a red cross.
5. When finished, click Finish to return to the dashboard.

Notes

• The importer detects the dump prefix automatically and rewrites it to your site prefix.
• Tables are imported in a fixed order so relations resolve correctly.
• The version table is intentionally skipped so the imported dump can never overwrite the installed component version marker.

Importing replaces data

Importing overwrites the existing JoomLeague data in the affected tables. Always back up your database before running an import.

Typical issues in old data

• MyISAM tables;
• older utf8mb3 charset;
• missing columns such as published;
• zero or empty dates;
• text stored as language constants;
• missing relations and indexes.

The online migration tool handles all of these automatically.

Legacy language constants

If an imported value looks like a language constant, it must not be replaced with hardcoded translated text.

The output layer should render it through Text::_().

New code must not create new legacy constants. New constants use the current COM_JOOMLEAGUE_* naming.