Converting legacy data to 6.2
Conversion is not an update
JoomLeague 6.2 is not compatible with JoomLeague 6.1.x. Its database schema is a completely new, sport-profile-driven design. Do not:
- Install 6.2 as a direct update over an existing 6.1.x installation.
- Copy files, extensions or templates from 6.1.x into 6.2.
- Import a 6.1.x database or SQL export directly into a 6.2 installation.
Doing either will not produce a working site.
Use the external conversion service
Supported legacy SQL dumps are processed through the dedicated conversion service:
The service performs an external extract-transform-load process and produces a new package for the universal 6.2 schema. It never updates the source website. Import the generated package only into a separate, clean 6.2 test installation and review the included conversion report before relying on the result.
Availability for a particular legacy release is determined by the converter's current source-detection and validation report. A successful data conversion does not make old extensions, templates, overrides or database tables compatible with 6.2.
Prepare the source safely
- Export a complete supported legacy database from a consistent backup point.
- Retain the original export unchanged and keep its media backup separately.
- Use a separate Joomla/JoomLeague 6.2 target with no valuable existing records.
- Back up that target before importing, even if it is only a test site.
- Check the converter's detected source family and warnings. A
.sqlextension alone does not establish that a source is supported.
An Akeeba JPA archive is not the same as a SQL dump. Restore it in an isolated compatible environment if necessary to inspect/export its database; do not expose the restored site publicly or upload JPA to an unrelated SQL importer.
Inspect the conversion output
The generated migration ZIP contains data and reports, not the Joomla CMS and
not a normal installable extension. Inspect manifest.json, report.txt and
migration.sql. Preserve the package and report together so target records can
be traced to their source.
Review skipped/unmapped entities, incomplete results, role mappings and media references. Warnings need investigation; a successful download does not certify the converted data.
Import into the clean target
- Install the full current JoomLeague 6.2 package normally.
- Extract the converter ZIP; do not upload it to the extension installer merely because it is a ZIP.
- Open JoomLeague Data Import and upload the generated
migration.sql. - Read the result and any conflict diagnostics.
- Inspect Migrations, Database Tools and Diagnostics.
- Verify the imported data before publishing menu items.
See Import and maintenance tools. Never upload the original legacy SQL directly to this screen.
Repeated imports and conflicts
Compatible catalogue repeats preserve existing records and can fill missing profile defaults. RC2 refuses incompatible sport IDs, UUIDs, catalogue ownership or profile bindings rather than silently attaching data to another sport.
Repeated import is not a universal merge or repair tool. Other entity IDs and local edits still require review. Investigate conflicts on a backed-up copy; do not delete catalogues, disable constraints or edit IDs until an upload succeeds.
Verify converted data
| Area | Compare with the source |
|---|---|
| Inventory | Competitions, seasons, projects, clubs, teams, people and matches |
| Scores | Regulation time, extra time, shootouts, awarded results and winners |
| Participation | Entries, memberships, positions, lineups and officials |
| Detail | Events, statistics, dates, times and historical descriptions |
| Media | Available files, paths, logos, photographs and placeholders |
| Frontend | Representative reports, tables and person histories as a guest |
Preserve season/team context and distinguish clubs from their individual teams. Missing source information is not a licence to invent values. Media references do not prove that the image files have been transferred.
Conversion of Joomla articles, accounts, template overrides and third-party extensions is not automatically implied by conversion of sporting data.
Already imported data on RC1
Read Updating to RC2. Its automatic result correction uses preserved legacy data and can overwrite manual edits to affected supported football results. It does not require a full migration rerun or automatically repair every previously missing catalogue record.
Before switching a public site
Keep the old site and final backup available, account for records created since the source export, verify media and URLs, and plan a consistent rollback. Obtain the owner's approval before switching. RC2 remains a testing release.
