Migrate

Move from Joomla to Kaleta.

Kaleta reads your Joomla 4 or 5 site through its own Web Services API: articles become news with their categories, tags, authors and images, and old addresses redirect with a 301. The API token you type is used only for that fetch and never stored. Claude then reworks the pages in your design system as drafts.

Built-in importer (Joomla API)

A day or two for a typical business website

Download Kaleta Read the comparison

What comes across.

Articles become news – the text before “Read more” becomes the intro
Categories as news categories, tags as tags
Authors (names only), each mapped to a user you choose
Unpublished articles as drafts, archived ones as published
The intro or full-text image and the meta description
Images, downloaded into Media in one step after the import
A 301 redirect from every old address – and links on the site that still point to an old address are rewritten
Pages that are not articles, imported by the site’s address

What does not.

Modules, menus and the template – the look and the menu are rebuilt in Kaleta.
Custom fields and the content of other extensions (forms, galleries, shops) – use Kaleta built-ins where they exist.
Registered users and access levels – no accounts are created.
Trashed articles – they are skipped.
Exact old addresses – the API does not give them; Kaleta uses the best guess /category-path/id-alias, so check the redirects with the migration report.

Step by step

How the move works.

No command line. Test everything on a subdomain first; the old site keeps running until you switch the domain.

Prepare Joomla – switch on the Web Services plugins (System → Plugins → Web Services). Then under Users → Manage → the user → Joomla API Token tick Enabled; the user must be allowed to read articles, categories and users.
Fetch – in Kaleta open Administration → Import and export → From another system → From Joomla, enter the site address and the API token and choose Fetch and show preview. The token is used only for this fetch and is not stored anywhere.
Preview and mapping – the preview counts articles, categories, tags, images and authors and lists what it cannot convert. Under What becomes what you choose what becomes news, categories and tags, and which user each author’s articles belong to.
Import – it runs in batches, so it survives the time limits of shared hosting. Then download the images into Media with one button, while the old site is still running.
Pages and layout with Claude – bring in pages that are not articles with Import from a website, connect Claude and run the ready-made task migrate_site: it reworks the pages in your design system as drafts, and you check the previews.
Check and switch – run Check the move before going live in Import and export: every old address is checked against the new site. Fix what it finds, publish, and point the domain to Kaleta.

Rebuild with Claude

Let Claude redo the pages.

Connect Claude, give it an old page – its address or saved HTML – and it rebuilds it as a draft from Kaleta sections, in your design system. You review the preview and publish.

How Claude works with Kaleta

Here is our old Services page. Rebuild it in Kaleta with our colours, keep the texts and redirect the old address.

Done – the Services page is saved as a draft with a 301 redirect from the old address. Here is the preview link.

Keep your rankings

An SEO checklist for the switch.

Redirects do most of the work. These few steps do the rest.

Keep the same domain and switch it over only when the new site is ready

Open your most visited old URLs and check they redirect to the right page

Set titles and descriptions for your main pages

Submit the new sitemap (/sitemap.xml) in Google Search Console

Set the company details – search engines get them as structured data

FAQ

Moving questions.

Is there an importer?

Yes. For Joomla 4 and 5 Kaleta reads the content through the site’s own Web Services API – no export file needed. A site on Joomla 3, or one without the API, comes in with Import from a website by its address: up to 3,000 addresses with their images, respecting robots.txt, blog posts as news, and 301 redirects from the old addresses.

Is my API token stored?

No. It is used only for the fetch and not stored anywhere. You can switch the token off in Joomla once the import is done.

Will I lose my search rankings?

Not if old addresses keep working. Joomla’s SEF addresses differ from site to site, so run the migration report before the switch: it lists every old address that does not lead anywhere, and Claude can add the missing redirects.