JoomLeague 6.2 Data Migration Service Updated

The data migration service at migrate.joomleague.eu has been significantly updated for the upcoming JoomLeague 6.2 release.

The new migration wizard first analyses a SQL database exported from an earlier JoomLeague installation. It then lets you review the automatically suggested mappings for:

  • sport types,
  • player, staff and official positions,
  • event types,
  • statistics.

Every suggested mapping can be changed manually before the migration starts. Unrecognised items are not silently assigned to unrelated definitions; they can instead be explicitly preserved in the migration archive.

The service accepts database exports from earlier JoomLeague generations, including versions 0.93, 1.5, 2.5 and 3.x. It produces a portable migration package intended for import into a clean JoomLeague 6.2 installation.

JoomLeague 6.2 uses a new universal database schema and is not directly compatible with the 6.1.x series. Existing data must therefore be converted with the new migration service:

Open the JoomLeague migration service

The migration service remains part of the ongoing JoomLeague 6.2 development process. Keep the original website and database unchanged, and always verify the generated package in a separate test environment before migrating a production website.

I try too migrate new migraton tool.
Assign positions
I think is missing position.
Screenshot 8 9 2026 13211 migrate joomleague eu hosted at ImgBB — ImgBB not all is available to choose.

Hi,

Thank you for reporting this. The migration service has now been updated.

If a legacy position does not have a suitable equivalent in the selected sport profile, you can now choose Preserve as a custom position. The migrator will create it as a custom position in the target sport type and preserve its use for team members and match line-ups.

The archive option remains available for positions that should not be used in the migrated installation.

The change is already deployed at migrate.joomleague.eu. Please try the migration again and let me know whether you can now map or preserve all positions correctly.