---
title: "Migrate from WordPress or Wix"
description: "Migrate from WordPress or Wix to Éclair: URL inventory, content and image transfer, 301 redirects, DNS switchover and Search Console."
url: "https://eclair.academy/en/paths/expert/migrate-wordpress"
lang: "en"
author: "Thierry Gustin"
published: "2026-11-02"
updated: "2026-11-02"
---

# Migrate from WordPress or Wix

> **Key takeaways** — To migrate from WordPress or Wix, first list every URL from the sitemap, decide what moves, recreate the content with smart paste or with Claude through the MCP connector, upload the images again, then create a 301 redirect for each old URL. Next, switch the DNS over, make the site visible, submit the sitemap and monitor Search Console.

To migrate from WordPress or Wix to Éclair, prepare it like a house move: you take inventory, sort, carry things over, then forward the mail. This lesson gives you a seven-step method to keep your search rankings: URL list, sorting, transferring content and images, 301 redirects, DNS switchover and checks in Search Console.

> **Before you start** — Time: 1 hour of reading and preparation, then a migration time that depends on the number of pages. Prerequisites: access to the old site's admin and its Search Console, Éclair installed on the new hosting ([Install Éclair step by step](https://eclair.academy/en/paths/beginner/install-eclair)) and the basics of [SEO with Éclair](https://eclair.academy/en/paths/intermediate/seo).

## What you'll be able to do

### 📍 Take inventory

Every URL of the old site, page by page.

### 🚚 Move the content

Smart paste, Markdown or Claude through the MCP connector.

### 📈 Keep your rankings

301 redirects, titles, descriptions and Search Console monitoring.

## The migration plan in one table

| Step | What you do | Where |
| --- | --- | --- |
| 1. Inventory | list every URL from the sitemap | old site, spreadsheet |
| 2. Sorting | keep, merge or drop each piece of content | spreadsheet, Search Console |
| 3. Content | recreate pages and posts | **Content**, MCP connector |
| 4. Images and categories | upload the images again, recreate the categories | **Media**, **Categories** |
| 5. Redirects | one 301 per old URL, titles and descriptions carried over | **Redirects**, SEO tab |
| 6. Switchover | DNS, HTTPS, site visible to search engines | host, **Settings** |
| 7. Checks | sitemap, 404 errors, rankings | Search Console, Bing |

## Step 1: take an inventory of every URL

When you migrate from WordPress or Wix, the old site's sitemap gives you the complete list. WordPress has published an index at `/wp-sitemap.xml` since version 5.5; with the Yoast SEO plugin, it's `/sitemap_index.xml`. Wix publishes `/sitemap.xml`, and its posts have `/post/…` URLs by default. This script collects every URL from a sitemap index (set `SITE` to your old site's address):

```bash
# Every URL of the old site, from its sitemap index
# (wp-sitemap.xml here; sitemap_index.xml with Yoast SEO, sitemap.xml on Wix)
SITE=https://ancien-site.fr
for map in $(curl -s "$SITE/wp-sitemap.xml" | grep -o '<loc>[^<]*' | sed 's/<loc>//'); do
  curl -s "$map" | grep -o '<loc>[^<]*' | sed 's/<loc>//'
done | sort -u > anciennes-adresses.txt
wc -l anciennes-adresses.txt
```

Import this file into a spreadsheet, then add the traffic of the last few months to each row. In Search Console, the **Performance** report, **Pages** tab, exports in one click: you'll know which URLs really matter.

## Step 2: decide what moves

For each URL, choose: **keep** (same topic, new page), **merge** (two weak posts become one good one) or **drop** (outdated content). Then note the new URL. In Éclair, pages live at the root (`/a-propos`, with subpages such as `/services/creation-site`, four levels at most), and posts live under the blog's URL, `/blog/…` by default, which can't be empty.

| Old URL | New URL in Éclair |
| --- | --- |
| WordPress, post `/2024/03/choisir-son-velo/` | `/blog/choisir-son-velo` |
| WordPress, category `/category/conseils/` | `/blog/conseils` |
| WordPress, page `/a-propos/` | `/a-propos`, with nothing to create: an automatic 301 removes the trailing slash |
| Wix, post `/post/choisir-son-velo` | `/blog/choisir-son-velo` |

A WordPress post published at the root can also become an Éclair page to keep exactly the same URL, at the cost of the post features: date, author, category, RSS feed, related posts. For dropped content with no equivalent, don't redirect to the home page: Google advises against sending unrelated URLs to a single page.

## Step 3: transfer the content

### Smart paste

Open the old page in your browser, or in the WordPress editor, copy the text, then paste it into an empty paragraph in Éclair's editor. Headings become subheadings (H1 and H2 become H2, down to H4), and paragraphs, lists, quotes, tables, code blocks and separators become blocks. Bold, italics and links come along; images don't. Pasting plain text also recognizes Markdown headings (`#` to `####`) and lists starting with `-`, `*` or `•`.

> **Pasted links point to the old site** — A copied link keeps its original URL, often an absolute one. Replace internal links with the new URLs using the editor's link search (`Ctrl+K`): you'll avoid unnecessary redirects.

### With Claude and the MCP connector

If your site is connected to Claude or ChatGPT ([Connect Claude to your site](https://eclair.academy/en/paths/ai-mcp/connect-claude)), which requires an HTTPS address, even a temporary one, paste the old text into a conversation and ask for a draft. The `create_draft` tool accepts the title, the body in Markdown, the URL, the SEO title, the meta description, “Key takeaways”, the focus keyphrase, the category, a FAQ and an image already in the media library.

```text
Here is the text of a page from my old site (URL: /services/creation-site/).
Create a draft page in Éclair:
- keep the title, subheadings and text as they are, in Markdown;
- URL: services/creation-site;
- SEO title and meta description: reuse these: “…” and “…”;
- don't make up any information, and point out what's missing.
[paste the text here]
```

The draft arrives in **Content**, never published: you review it, complete it and publish it. The connector can't upload images; it chooses from those in the media library, and it accepts at most 60 changes per hour per app.

## Step 4: images and categories

Download the originals from the old site's media library or, for WordPress, from the `wp-content/uploads` folder via FTP. Drag them into **Media**: JPG, PNG, WebP or GIF, 20 MB and 40 megapixels at most, SVGs refused. Éclair shrinks them to 2000 px, creates the WebP versions and removes the EXIF data. Fill in the alt text as you go, or use **Describe with AI** if the assistant is turned on ([Images and the Éclair media library](https://eclair.academy/en/paths/beginner/images-media-library)).

Then recreate the categories in **Categories**, with their description and SEO title: they become pillar pages, at the URL `/blog/<category>`.

## Step 5: how do you migrate from WordPress without losing rankings?

Everything relies on 301 redirects and on carrying over the titles. In **Redirects**, add each old URL with its new destination and the type **301 — permanent (recommended)**. You can paste a full URL: Éclair only keeps the path, without a trailing slash. Chains are shortened automatically (A to B, then B to C, gives A to C), and the **Hits** column shows which old URLs are still in use.

An old URL with a trailing slash or uppercase letters takes two hops: Éclair first normalizes it (301), then applies your redirect. Google follows these two hops easily, since its crawlers accept [up to ten](https://developers.google.com/search/docs/crawling-indexing/http-network-errors). Two limits to know:

- URLs with parameters, such as `/?p=123`, can't be redirected one by one: only the path counts, and this one displays the home page;
- on Nginx, the official configuration itself returns a 404 for missing images; to redirect old images, add `try_files $uri /index.php$is_args$args;` to the static files block.

For each piece of content, also carry over the old site's SEO title and meta description (Yoast SEO fields or Wix SEO settings) into the editor's **SEO** tab. A filled-in SEO title is used as is; if it's empty, Éclair applies the format from **Settings › SEO › Title format**. Finally, check the scores in the **Analysis** tab.

## Step 6: switch the domain over

1. Build the site on a temporary address and, in the meantime, uncheck **Visible to search engines** in **Settings › SEO**: everything switches to `noindex`.
2. If your registrar allows it, lower the time to live (TTL) of the DNS records one or two days before the switchover.
3. Point the domain to the new hosting, then turn on the HTTPS certificate.
4. If the site was built in another folder or with another host, copy the whole Éclair folder to the right place, then change the address in **Settings › General**: internal links follow.
5. Verify the address from the **Security** page, then check **Visible to search engines** again.
6. In Search Console, keep the property verified: if the old site carried the verification tag, paste it into **Settings › SEO**. Submit the `/sitemap.xml` sitemap. If the domain changes, also use Google's Change of Address tool.

## Step 7: check after the migration

```bash
# For each old URL: final status code, number of redirects, destination
while read -r url; do
  curl -s -o /dev/null -L -w "%{http_code} %{num_redirects} %{url_effective} <- $url\n" "$url"
done < anciennes-adresses.txt
```

Each line must end with a 200 code, after one or two redirects, on the right page. In the following weeks, monitor Search Console's **Pages** report and the redirects' **Hits** counter. Google recommends keeping redirects for at least a year: in Éclair, they stay until you delete them. Finally, test the contact form, search and the legal pages.

## Key points

- To migrate from WordPress or Wix, always start from the complete list of URLs, taken from the sitemap.
- Smart paste keeps the text's structure but not the images, which you upload again to **Media**.
- Claude, through the MCP connector, creates complete drafts with the URL, SEO title and meta description.
- Each useful old URL gets a 301 to its equivalent, never to the home page by default.
- After the switchover: site visible, sitemap submitted, redirects kept for at least a year.

## Going further

- [SEO with Éclair](https://eclair.academy/en/paths/intermediate/seo): automatic redirects, titles, descriptions and the sitemap.
- [40 MCP use cases, with prompts](https://eclair.academy/en/paths/ai-mcp/mcp-use-cases): more ready-to-copy prompts to rewrite and enrich your content.
- [cPanel, Plesk, DirectAdmin: the universal method](https://eclair.academy/en/hosting/cpanel-plesk-directadmin): upload the files and set up the hosting.
- Google Search Central: [Site moves with URL changes](https://developers.google.com/search/docs/crawling-indexing/site-move-with-url-changes).
- WordPress: [XML sitemaps built in since version 5.5](https://make.wordpress.org/core/2020/07/22/new-xml-sitemaps-functionality-in-wordpress-5-5/).

## Frequently asked questions

### Can Éclair import a WordPress export?

No, Éclair 1.8 has no importer. Content goes through smart paste, or through Claude and ChatGPT via the MCP connector, page by page, which means you review each piece of content.

### Do my posts have to change URL?

Éclair posts live under the blog's URL, `/blog/` by default. Either you redirect the old URLs with a 301, or you recreate the post as a page to keep the same URL.

### What happens to WordPress comments?

Éclair has no comment system, so they aren't carried over. Your readers' recurring questions can feed a FAQ in the post.

### How long should I keep the redirects?

Google recommends at least a year. The **Hits** counter then tells you whether an old URL is still in use before you delete it.