Skip to the main content
Menu

Migrate from

Moving off Elementor?

The Page Builder module replaces Elementor and imports pages built with it. The Clearframe theme replaces Hello Elementor.

In the library. Built and tested. A site that needs it pays $0 to build it. $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.

Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format. Run the import as a check first: it reports everything it could not carry before it changes anything.

The Duck arms folded, a wry knowing look

How the move goes

  1. Step 1: Pick a theme

    Any Hostless Duck theme built from the theme kit works. Coming from Hello Elementor, Clearframe is the plain frame made for this, and its importer reads the Elementor kit's site settings (colours, fonts, header and footer options).

  2. Step 2: Import the pages

    Give Page Builder the WordPress export file (.xml) or a saved Elementor template (.json). Pages and posts built with Elementor arrive as layouts.

  3. Step 3: Read the report

    Every widget or setting it could not carry, and every value it had to guess, is named in the import report.

Widgets that map

  • Heading
  • Text editor
  • Image
  • Button
  • Icon box
  • Image box
  • Spacer
  • Divider
  • Video
  • Icon list
  • Accordion
  • Toggle
  • Tabs
  • Testimonial
  • Counter
  • Progress bar
  • Basic gallery
  • Image carousel (as a grid)
  • Social icons
  • HTML
  • Menu anchor
  • Call to action, from Elementor Pro
  • Gallery, from Elementor Pro
  • Form (as a note of its fields), from Elementor Pro

A widget not on this list keeps its words and links as plain content and is named in the report.

What comes across

Every page and post built with Elementor in a WordPress export, and pages saved as templates: sections, columns and nested sections; flexbox containers nested inside each other; column and container widths per screen size; padding, margin, background colour and picture with its veil, border, corner radius, shadow, least height, text alignment and hidden-on-screen-size settings. Elementor's four built-in global colours follow the theme's palette and its global fonts the theme's fonts; custom global colours keep their own value. A widget with no equal here keeps its words and links as plain content and is named in the report.

Read on a best guess

These settings are stored in a form Elementor does not document fully. The importer reads them on a best guess and says so in its report each time it meets one:

  • column gap sizes
  • flexbox container direction, alignment, gap, wrap and padding defaults
  • stacking on phones

Not supported

Animations, motion effects, positioning, shape dividers, gradients (the first colour is kept), custom CSS and class names, video backgrounds, uploaded SVG icons, fonts loaded from elsewhere, reversed order in containers, and theme-builder templates such as headers, footers and pop-ups. Pictures keep the old site's address until uploaded here. Forms must be rebuilt in Contact Forms Core. Scripts, frames and styles inside Text and HTML widgets are removed. Not yet verified against a live export: the fixture is synthetic and some settings are read on a best guess, each named in the import report (column gap sizes; flexbox container direction, alignment, gap, wrap and padding defaults; stacking on phones).

What Page Builder does not do at all:

  • Not yet: Drag and drop, and editing on the page itself: the editing screen is plain forms, and a change is seen on the page after saving. A live visual editor needs a script-driven editor, which this module does not ship.
  • Not yet: Animations, motion effects, sticky and absolute positioning, shape dividers, masks, video and slideshow backgrounds: none. An Elementor gradient keeps its first colour. The importer names each one it meets.
  • Not yet: Custom CSS and custom class names per element: a layout can never carry a style rule, only checked values.
  • Not yet: Site parts built with Elementor Pro's theme builder (headers, footers, single-post and archive templates, pop-ups): set the header and footer in the theme; the Popup & Opt-in Builder module makes pop-ups.
  • Not yet: Carousels, sliders and lightboxes: an image carousel becomes a grid, a slider's slides are shown one under another, and a gallery picture opens as the full-size file.
  • Not yet: Counting up in the Counter: the number is shown at once.
  • Not yet: Icons: 37 built-in line icons, not an icon font. Social links show a short text mark, not the networks' logos.
  • Not yet: Fonts loaded from elsewhere: a font is matched to the closest built-in family of the same kind, made of fonts already on visitors' devices.
  • Not yet: Global colours and fonts changing a whole site from one place inside the module: imported globals follow the theme's palette and fonts instead, which are changed under Customize.
  • Not yet: A panel inside the page editor: Core's editor has no place for a module to add to, so a layout is edited on this module's own screen, one link away from its page.
  • Not yet: Edge-to-edge sections on a theme not built from the theme kit: there a layout is as wide as the theme's content column.
  • Not yet: The Form widget building forms itself: it shows a form made in the Contact Forms Core module, by its number. An imported Elementor form arrives as a note of its fields, to rebuild there.

Hello Elementor's settings

Not yet verified against a live export: this importer has only been tested on sample files we wrote from the documented format.

Clearframe brings over
Hello Elementor’s own header and footer options: site logo or title, tagline, menu and copyright shown or hidden; the default, inverted or centred header arrangement; boxed or full width; header and footer background, title and menu colours; logo width; where the menu collapses; the copyright text. And the kit’s site settings: the four site colours and colours the owner added (followed wherever a setting points at them), page background, text, link, heading and button colours, body, heading and button fonts (as the nearest built-in family), sizes, weights and line spacing, button rounding and the content width.
It does not bring over
The pages themselves: they are brought across by the Page Builder module’s importer, not by this one. A header or footer built in Elementor’s Theme Builder (not with Hello’s own options). The kit’s form-field, image and lightbox styles, custom CSS, and anything set for single widgets. Sizes given as a share of the screen; see-through colours; a font, weight or colour of its own for one heading level; the fonts themselves; the logo and menus. Each is named in the import report when the file has it. Not yet verified against a live export: the fixture is synthetic, and the names of the kit’s site-wide colour, type and button settings are inferred from Elementor’s documented data format.

Clearframe live demo

The small print

Elementor and Hello Elementor are another company's products, named here only to say what Hostless Duck can import from. Hostless Duck is not affiliated with, endorsed by or sponsored by their makers, and uses none of their code, styles or wording.

Is Elementor 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.

The Duck giving a thumbs-up