Skip to content

Migrate

Move from Ghost to Kaleta.

Kaleta imports Ghost’s JSON export: posts become news, pages become pages, tags and authors come along – and every old address redirects with a 301, so links and search rankings keep working. Claude then reworks the pages in your design system as drafts.

Built-in importer

An afternoon for a typical blog or business website

What comes across.

  • Posts become news, pages become pages – published, scheduled and, if you want, drafts
  • The primary tag of a post as its category, the other tags as tags
  • Authors, each mapped to a user you choose
  • Texts from the Lexical editor too: paragraphs, headings, lists, quotes, links and images
  • Feature images, excerpts and meta titles and descriptions
  • 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

What does not.

  • Members and paid subscriptions – Kaleta has no visitor accounts or payments.
  • Newsletters – a post that was only sent by e-mail comes as a draft.
  • Comments
  • The theme – the look is rebuilt in your design system.
  • Other editor cards (galleries, embeds, buttons…) – the preview counts them; the text around them stays.
  • Custom routes – routes.yaml is not in the export, so old addresses are taken as /slug/.

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.

  1. Export – in Ghost Admin open Settings → Labs → Export your content and download the .json file.
  2. Upload – in Kaleta open Administration → Import and export → From another system, choose Ghost and upload the file.
  3. Preview and mapping – the preview counts posts, pages, tags, images and authors and lists what it cannot convert. Under What becomes what you choose what becomes news, pages, categories and tags, and which user each author’s posts belong to. Ghost’s export does not carry the site address, so you enter it here – images and redirects count on it.
  4. 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.
  5. 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.
  6. 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.

Does the import change my Ghost site?

No. You only download an export file; the old site keeps running until you switch the domain over.

Do my members and newsletters come across?

No. Members, newsletters, comments and the theme are not transferred – Kaleta is a website system without visitor accounts or paid subscriptions. If they are central to your site, Ghost is the better choice.

I used custom routes. Will the redirects match?

Kaleta takes old addresses as /slug/, Ghost’s default. A custom routes.yaml is not part of the export, so check the move with the migration report and add the missing redirects – Claude can create them for you.

Can I run the import again?

Yes. Kaleta remembers what it already imported and skips it, so nothing is added twice.

Other moves

Moving from somewhere else.

All migration guides

Built-in importer

Move from WordPress to Kaleta

Read the guide

Built-in importer

Move from Blogger to Kaleta

Read the guide

Built-in importer (Joomla API)

Move from Joomla to Kaleta

Read the guide

Ready to move?

Download Kaleta, install it on a test subdomain and start with one page – about ten minutes to your first preview.