Skip to content

Administration

Move from WordPress.

Upload a WordPress export: posts become news, pages can go straight into the builder, menus, WooCommerce products and Polylang or WPML languages come along, images move to Media and old addresses redirect.

Administration → Import and export with Import from WordPress open

Administration → Import and export with Import from WordPress open

Administration → Import and export → WordPress.

  1. In WordPress go to Tools → Export and download the XML file.
  2. Upload it in Kaleta and check the preview – it warns about shortcodes of plug-ins that cannot be converted.
  3. Run the import.

What happens

  • Posts become news, categories and tags come along (nested categories are flattened).
  • Pages become pages – optionally straight into the builder – hidden from navigation.
  • Menus go into the draft look, with links to the new addresses; they change the site only when you publish the look.
  • WooCommerce products become a product catalogue – code, price, availability, parameters and pictures – and product categories become collection categories in every language, with redirects from their old addresses.
  • A multilingual site (Polylang or WPML) arrives as linked language versions, and its old /en/… and ?lang= addresses redirect.
  • Images are downloaded into Media.
  • Redirects are created for all old addresses, including /?p=123.

Comments and user accounts are not transferred; imported news belongs to whoever runs the import, or to an existing user with the author’s e-mail address.

You can run the import again – whatever it already converted is skipped. Claude can run the same import with the import_wordpress tool, in resumable batches; everything then arrives hidden, and pages laid out with Breakdance, Elementor, Oxygen or Divi are listed for rebuilding.

Other platforms, or no export

Administration → Import and export → Import from a website brings in any site by its address – Wix, Webnode, Jimdo, Squarespace, Joomla, Drupal, or WordPress without an export.

  • Kaleta finds the pages in the sitemap, or follows the site’s links when there is none (up to 3,000 addresses), and shows what it found before importing. It respects the old site’s robots.txt and pauses between requests.
  • Each page becomes a hidden builder page with its images in Media; blog posts become news.
  • The old addresses redirect to the new pages.
  • The header, footer, menus, cookie bars and forms of the old site are left out – the pages take your site’s look, and Claude can rework them.

Running it again skips what is already there. Claude does the same with the import_website tool.

SEO data and custom post types

  • SEO plugins: titles, descriptions and noindex from SmartCrawl, Yoast SEO and Rank Math go into the SEO fields of the news items and pages. A title made only of the plugin’s variables is skipped – the site builds it itself. The plugins’ redirects are not part of the export: import the Redirection plugin’s CSV export in Redirects (up to 5,000 rows, wildcard rules and 410 Gone included), or let Claude move them.
  • Custom post types (CPT UI, ACF, Secure Custom Fields) become collections with item pages. Each field becomes a collection field, its type guessed from the values, and the items keep their old addresses. Repeaters, galleries and relationships are left out – the preview names them.

Check the move before going live

Administration → Import and export → Check the move before going live: enter the old site’s address. Every old address is looked up on this site – missing pages, pages not published yet, redirect chains, and pages that lost their description, form or images – followed by the checks of the whole site. Nothing is changed. Claude runs the same check with migration_report.

Still stuck?

Ask on GitHub or write to info@kaletacms.com – the guide gets better with every question.