Skip to content
Contentrain
Contentrain Migrate

Move a WordPress site to Astro, checked against the original

Contentrain Migrate turns a WordPress content site into an editable Astro project in your own GitHub: layouts as Astro components, content as models you can edit, addresses kept or redirected, and every move checked against your original.

migrate.contentrain.io

# WordPress content site → Astro project

✓ Layouts as Astro components

✓ Posts, pages and media as editable models

✓ Addresses kept or redirected

✓ Checked against your original

→ delivered to your own GitHub

What you get

A finished Astro project, not a copy of your pages

Your layouts become Astro components, your content becomes Contentrain models you can edit, and the finished project lands in your own GitHub. Your content, addresses and search titles stay as they are, and an address that has to change redirects. The design is rebuilt as a modern version of your site, from your colors, fonts and logo.

  • Posts, pages, media and menus as editable models
  • Content, page structure, addresses and SEO kept
  • A modern design from your colors, fonts and logo, not a pixel copy
  • A project you own, in your GitHub
your GitHub repository

.contentrain/models/

.contentrain/content/

src/layouts/*.astro

src/components/Seo.astro

src/pages/…

astro.config.mjs

# content as models,

# layouts as Astro components

How it works

From your URL to your GitHub in four steps

Start with a free report on what your site has and what is holding it back. You see the scope first. Online payment is not open right now, so one fixed price for the whole site comes as a quote by email, and nothing is charged until you accept it. Once you accept and your site is connected, the move runs on our servers and you can follow it live.

  • Free discovery, no account needed
  • One fixed price per site, quoted by email
  • Usually 30 min to 6 h, depending on load, size and structure
From your URL to your GitHub

1 Free discovery: what your site has

2 Offer: the scope and one fixed price

3 The move runs; follow it live

4 An Astro project in your GitHub, with a report

# no account needed for discovery

The checks

Every move is checked against your original

Every delivery comes with its own report, including anything left to finish. If an automated check cannot pass on its own, the move shows it is being completed and we email you when it is ready.

  • A delivery report with every move
  • Anything left to finish is listed, not hidden
Delivery report

Checks

✓ Content, page by page

✓ Search and addresses

✓ Three screen widths

390 · 768 · 1280

✓ Nothing private leaks

✓ Ready to edit

✓ A clean Astro project

Left to finish

# listed in the report, not hidden

Your WordPress

Your WordPress site is only read, never changed

Migrate reads what your site shows the public and, if you add one, what an application password opens. You can revoke it at any time. Your domain stays where it is until you point it at the new site.

  • Read-only access you can revoke
  • The optional Bridge plugin is yours to install and remove
  • Your domain moves only when you move it
WordPress → Migrate access

# read-only, revocable

✓ Public pages and media

✓ Application password (optional)

✓ Bridge connection key (optional)

No remote call creates, edits

or deletes posts, settings,

files, users, plugins or themes

# revoke in your WordPress profile

Is it for me?

Built for content sites on WordPress

Migrate is for blogs, company sites and landing pages. A site whose shop is its business gets no offer, because a static site cannot run a shop. Comments, forms and search each get a choice in the offer: managed by Contentrain Studio, an adapter on the static site, or kept on WordPress.

  • Blogs, company sites and landing pages
  • Membership systems stay on WordPress
  • The offer names what stays before you order
Your offer · what stays

# blogs, company sites, landing pages

Contact form

Studio, a form service or

a link to WordPress

Membership plugin

Move without the membership

system

Shop pages

They stay on WordPress;

your offer says so

After delivery

Edit in Git or in Contentrain Studio

Your content lives as structured models in your repository. Edit it in Git, or connect Contentrain Studio for a visual editor with review and history. Host the project anywhere that serves static sites.

  • Structured models in your repository
  • Studio as the optional visual editor
  • Any static host
Edit in Git or in Studio

# in Git

.contentrain/content/…/en.json

# or connect Contentrain Studio

Open the site in Studio

✓ Bring over your comments

✓ Move your images to Studio Media

✓ Check it on your live site

# host it on any static host

Common questions

Do you touch my WordPress?

No. Migrate only reads your site: what it shows the public and, if you add one, what an application password opens. You can revoke it at any time. The optional Bridge plugin runs on your WordPress only if you install it, and you can remove it afterwards.

Will my new site look the same?

Your content, page structure, addresses and SEO are kept, and an address that has to change redirects. The look is modernized: the design is rebuilt from your colors, fonts and logo, so the new site is a modern version of yours, not a pixel copy. How far each page’s layout differs from the original is measured and listed in your delivery report.

When do I see the price?

After the free discovery. Online payment is not open right now, so one fixed price for the whole site comes as a quote by email, and nothing is charged until you accept it.

How long does it take?

Discovery usually takes under a minute. Once you accept the quote and your site is connected, the move takes 30 minutes to 6 hours, depending on system load and the size and structure of your site. You can follow it live.

What about comments, forms and search?

They run on a server today. The offer lists each one with its choices: managed by Contentrain Studio, an adapter on the static site, or kept on WordPress.

Where do I host it?

Anywhere that serves static sites. The project is yours, in your GitHub.

Start local. Scale to Studio.

Build a governed content layer before content becomes product debt.

Start locally with the MIT packages. Add Studio when teams need review, roles, structured editing, managed delivery, or deployment control.

Open Studio