Migrate from
Leaving Twenty Twenty-Three? Here is what carries over.
On Hostless Duck, Wrenfield replaces the Twenty Twenty-Three theme and reads its settings. What comes across and what does not is listed below, exactly as each importer's own record states it.
What carries over, and what does not
Wrenfield
Replaces Twenty Twenty-Three. A spare white page in the device’s own sans with posts in a grid of three and square bright buttons, built on the shared theme kit. Brings a Twenty Twenty-Three site’s global styles across.
From Twenty Twenty-Three global styles
- Carries over
- The colour presets (the five named colours, changed one by one or as a whole style variation) and colours the owner added, wherever a setting uses them; page background and text colour (the header and footer follow them); link, heading and button colours, with their pointed-at colours; whether links are underlined; body and heading fonts (as the nearest built-in family), sizes given as a size preset, a fixed size or a clamp(), weights, line spacing and letter case; the six heading sizes; button rounding, text size and weight; the navigation block’s text size, weight and case; the content width and the wide width. Read from the stored global styles document, the REST answer for global styles, or the theme.json of a Site Editor export.
- Does not carry over
- Block templates and template parts: the header, footer and page layouts built in the Site Editor are separate entries and are NOT imported (the report says so every time). Styles set for single kinds of block; block style variations; extra CSS; spacing, shadow, gradient and duotone presets; sizes given as a share of the screen; see-through colours and gradients; a font, weight or colour of its own for one heading level; the fonts themselves; the logo and menus. A global styles file does not name its theme. Each is named in the import report when the file has it. Not yet verified against a live export: the fixtures are synthetic.
Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.
Each import ends with a report that names anything it could not carry.
The rest of the site
Twenty Twenty-Three is one part of a site. Hostless Duck reads a WordPress site through a connection you approve and brings content, pictures, menus, comments and many plugin settings, and reports plainly what it could not carry.
The site check reads your public pages once and lists the theme and plugins it can see, with what Hostless Duck has for each. A plugin with no replacement yet is built for your site On The Fly. How that works
The Library Effect. Built once. Every site after rides free. A part built for one site joins the library, so every plugin on your site is in the library, in the build queue, or not yet needed. Look up the others.
$0 is the cost to build, for every site after the first. Applying the part to your site is part of the move. A site on a different version or set-up of the same plugin can read Partial: a priced gap, never a rebuild.
The small print
Twenty Twenty-Three is another company's product, named here only to say what Hostless Duck can import from and what does the same job. Hostless Duck is not affiliated with, endorsed by or sponsored by its makers, and uses none of their code, styles or wording.
Is Twenty Twenty-Three the only thing your site runs on?
Give us your site's address and we read its public pages once: its theme, its plugins, and what Hostless Duck has for each. A real scan of your public pages, never a made-up result. No card.

