How to import an existing HTML website into Elementor

Migrating a static HTML website into WordPress with Elementor sounds like a big job, and done the wrong way it is. Done page by page with a converter, it is mostly mechanical. Here is the approach that keeps it manageable and gives you real, editable Elementor pages at the end.

Set up the WordPress side first

Before converting anything, get the destination ready: a WordPress install with Elementor active, your fonts registered (Site Settings → Custom Fonts) if the original used web fonts, and your brand colours set as Global Colours if you want the imported pages to adopt them. Doing this first means you judge each converted page against the real site, not against fallback fonts and placeholder colours.

Convert one page at a time

Do not try to import the whole site in one action. Work through it page by page, and within a long page, section by section. Each converted unit is easy to verify; a whole site at once is not. Converting in slices also means you do not drag the old site header, footer and cookie banner into every page.

For each page: open its HTML, make sure the CSS is inline or in a style block, and paste it into the converter in Native components mode. Headings, text, images, buttons and layout become native Elementor widgets and containers, with spacing, colours and typography carried onto real controls.

Handle the shared header and footer once

A static site repeats its header and footer in every HTML file. In WordPress you do not want them in the page content — you want them as a theme header and footer (or Elementor Theme Builder templates) built once and applied everywhere. So when you convert a page, use the copy root in the Structure map to grab only the main content of that page and leave the header and footer behind. Build those separately, one time.

Images and links need attention

• Images: upload them to the Media Library and reference the real URLs, and they import with no manual step. Local file paths and Base64 images cannot become attachments, so they arrive as empty placeholders — each keeping its alt text as a caption so you know what to upload.
• Internal links: a static site links between .html files. After import, update those to point at your new WordPress URLs. This is the one tedious part of any migration and there is no way around it, but it is quick per page.
• Forms and menus: a form submit action does not carry over — connect it to an Elementor Form on your site. Navigation becomes a real WordPress menu.

What converts well, and what you redo

Layout, spacing, colours, typography, images, icons and structure convert faithfully. Scripts are stripped, so any JavaScript-driven behaviour is rebuilt with native widgets. Hover states and animations are re-applied in Elementor. Knowing this split up front turns the migration into a predictable checklist rather than a series of surprises.

A migration order that works

1. Build the shared header and footer once.
2. Convert the home page, then the main landing pages, then inner pages.
3. For each page, set a copy root to grab the content, paste, then fix internal links and images.
4. Rebuild interactive pieces (sliders, tabs) natively.
5. Save reusable sections — a feature grid, a CTA band — to the template library as you go, so later pages become assembly rather than construction.
6. Set up redirects from the old .html URLs to the new ones so you keep your search rankings.

Worked this way, importing an HTML website into Elementor is a steady, page-by-page process with an editable WordPress site at the end — not a rebuild, and not a pile of uneditable code blocks.