Sidecar Software / Independent tools

K2Bridge / K2 to Joomla 5

K2 content. Native Joomla articles.

Move legacy K2 items, category trees, tags and extra fields into a fresh Joomla 5 site.

Choose your edition →Read the migration guide

Native articles and custom fields from legacy K2 content.

01 / CHECK BEFORE YOU MOVEK2Bridge preflight with fixture counts

Know what's coming. Run the preflight check before making changes.

Native custom fields

Extra field groups, definitions and item values become Joomla fields.

Read-only source

The legacy database is only read.

Admin or CLI

Check the source and migrate from the administrator or command line.

Scope, without surprises

Move the content. Rebuild your site.

What moves

Items and article IDs, text, aliases, dates, publication state, hits and featured flags; category trees, tags and extra fields. Category and tag IDs are remapped. Authors match existing users by email; unmatched authors use the target user with the lowest ID.

What stays behind

Comment text, users/passwords, media files, galleries, menus, modules, templates, permissions and other extension data. Attachments become links only; copy image and attachment files separately. Old K2 URLs are not guaranteed.

Before you start

Fresh Joomla 5 target with no articles or existing custom fields, categories or tags of your own; SELECT access to the legacy K2 and Joomla users tables. Tested with the included fixture on Joomla 5.4.10, PHP 8.3 and MariaDB.

Real administrator migration log
Real administrator migration log
Three migrated K2 articles in Joomla 5
Three migrated K2 articles in Joomla 5
Native Joomla custom field definitions
Native Joomla custom field definitions
Migrated fixture article on the Joomla front end
Migrated fixture article on the Joomla front end

Setup

How to set it up

  1. Back up both sites and use a fresh staging target.
  2. Install pkg_k2bridge-1.0.1.zip via System > Install > Extensions.
  3. Open Components > K2Bridge Migrator and enter source database details.
  4. Run Check, resolve warnings, then Migrate.
  5. Copy media files, rebuild menus and redirects, and verify the result.

Comments are counted only, never copied or archived. Migration is not an incremental sync. Use CLI for large sources. Target changes use one transaction; use InnoDB. Restore a backup to undo a committed run.

Full installation and CLI guide

One tool. Your next move.

Choose your edition.

One-time prices in USD. Applicable taxes calculated at checkout.

Single site

$49

12 months of updates

Unlimited sites

$99

For agencies and multiple sites

Sandbox checkout - configuration pending. No live purchases.

GNU General Public License version 2 or later. Site tiers describe the commercial update offering; GPL rights are unaffected.