Migrate

Move from Drupal to Kaleta.

Kaleta reads your Drupal 9, 10 or 11 site through its JSON:API: articles become news, basic pages become pages, tags, authors and images come along, and the old addresses redirect with a 301. Claude then reworks the pages in your design system as drafts, and you publish when it looks right.

Built-in importer (Drupal JSON:API)

A day or two for a typical business website

Download Kaleta Read the comparison

What comes across.

Articles become news, basic pages become pages
Tags, and authors each mapped to a user you choose
The article image, the summary and the meta description where the site has them
Unpublished content as drafts – with an optional sign-in
Images, downloaded into Media in one step after the import
A 301 redirect from every path alias (or /node/number) – and links on the site that still point to an old address are rewritten
Repeating content (team, references, services) as Kaleta collections, with Claude

What does not.

Other content types, custom fields and views beyond what collections cover
Blocks, menus and the theme – rebuilt in Kaleta
Comments
User accounts and permissions – no accounts are created
Editorial workflows – Kaleta has drafts and roles, no approval steps
Custom modules and integrations

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 Drupal – switch on the core JSON:API module. Published content needs no sign-in.
Fetch – in Kaleta open Administration → Import and export → From another system → From Drupal, enter the site address and choose Fetch and show preview. For unpublished content, type a sign-in (user:password with HTTP Basic authentication switched on in Drupal, or an access token) – it is used only for this fetch and is not stored anywhere.
Preview and mapping – the preview counts articles, pages, tags, images and authors and lists what it cannot convert. Under What becomes what you choose what becomes news, pages and tags, and which user each author’s content belongs 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.
Rebuild with Claude – connect Claude and run the ready-made task migrate_site: it reworks the imported 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 Drupal 9, 10 and 11 Kaleta reads the content through the core JSON:API module – no export file needed. An older Drupal site 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.

No. Published content needs none; a sign-in for unpublished content is used only for the fetch and not stored anywhere.

Will I lose my search rankings?

Not if old addresses keep working. The path aliases redirect to the new pages, and the migration report checks every old address before you switch the domain – Claude can add any redirect that is missing.