ANODA Discuss your product

WordPress Migration Services

ANODA moves your WordPress archive and useful plugin workflows to a simpler stack, so writers keep publishing without builder repairs while valuable URLs and content survive the switch.

Discuss your migration Explore our work
A steel robotic arm clamped to a small white table slides an orange section from a cluttered old white ceramic page block into a slim new frame.
Custom scope
Fixed or phased, set in the proposal
Every plugin accounted for
Replaced, rebuilt or retired
Permalinks preserved
Old URLs redirected and tested
Not a host move
Your content leaves WordPress

In short

Your WordPress content on a simpler stack, with every plugin's job accounted for.

What's included

  • Content export
  • Taxonomies and media
  • Shortcodes and blocks
  • Plugin replacements
  • Redirects
  • Editor handoff

Answers you'll have before anything moves

  • Keep WordPress, or leave it?
  • Which plugin features do we still need?
  • Where will editors write after the move?

Where it stops

WordPress Development

Builds and improves sites that stay on WordPress.

Migrate from WordPress

Moves the content off WordPress to a simpler stack.

Not included

  • A redesign, content rewrite or host-to-host move
  • A like-for-like swap for every plugin

Years of posts moved, and nothing left running on plugins

What you keep, from the plugin inventory to trained writers.

Discuss your migration
  • A white ceramic shelf of small lidded boxes in two rows, one box graphite, one lifted out onto the ground with its lid off.

    Content and plugin inventory

    Post types, taxonomies, media, shortcodes and every active plugin, each with its fate.
  • A ceramic pegboard of white pegs, two pulled out onto the ground and steel pieces fitted in their place, one peg graphite.

    Replacement plan

    What each plugin did, and what takes over: a component, a service or nothing.
  • A loose stack of ceramic sheets fed through a steel press, coming out as a neat row of upright cards, one graphite.

    Migrated content

    Posts, pages, categories and media imported, shortcodes converted, links rewritten.
  • A white ceramic signpost with three thin steel arrow plates pointing different ways, one plate graphite.

    Redirects and editor handoff

    Old permalinks mapped, SEO settings carried over, editors trained on the new CMS.

You receive

  • The site in your repository and accounts
  • Redirect map and test record
  • A walkthrough for your writers

Every plugin did a job. Each job gets a new owner or an ending.

WordPress’s WXR export carries content records, terms and custom fields; it does not include the media files themselves or all site configuration. We collect uploads, settings and plugin behavior separately, including shortcodes, page-builder layouts, forms, SEO, redirects and search. Before we migrate from WordPress we list each one and agree who handles it. That replacement plan stops hidden plugin jobs becoming missing forms, broken archives or another developer queue after launch.

  • Inventory

    Post types, custom fields, categories, tags, authors, media, shortcodes, page-builder layouts and every active plugin listed, with the URLs that earn traffic. Needs Admin access, a recent database backup, analytics and search console.

    Done when Every plugin and content type is marked replace, rebuild or retire, and you have approved the list.

  • Model and stack

    The new home chosen — often Astro with a headless CMS or content in Markdown — and categories, tags and custom fields mapped into it. Needs Who writes, how often, and what they must be able to publish alone.

    Done when The CMS, the mapping of categories, tags and custom fields, and the writing workflow are approved in writing.

  • Rebuild templates

    Post, page, archive and landing templates rebuilt as components, with each shortcode and block given its equivalent. Needs The theme's current look, or the changes you have approved.

    Done when Each template renders real imported posts at every breakpoint, passes keyboard and contrast checks, and meets the speed budget.

  • Import and replace

    Content imported by script, media downloaded and re-linked, internal links rewritten; forms, search and analytics replaced and tested. Needs Test access to the CRM, email and other tools the plugins feed.

    Done when Retained post and media counts reconcile with the approved inventory, retired items are documented, migrated internal links reach the new site, and forms reach the agreed destination.

  • Switch

    Permalinks redirected, SEO titles and descriptions carried over, a publishing freeze agreed, then the domain switched and errors watched. Needs DNS and host access, a posting freeze your writers know about, and one person with the final call.

    Done when Retained permalinks and feeds resolve, moved URLs redirect to relevant replacements, retired URLs return the agreed status, monitoring is live, and the WordPress install stays restorable until you sign off.

  • Hand over

    Writers walked through drafting, previewing and publishing in the new CMS; the runbook and redirect map handed over. Needs The people who write for the site.

    Done when A writer publishes a post with an image and a category on their own.

Who owns what

ANODA builds

  • The inventory of post types, taxonomies, media and plugins
  • The new stack, content model and editing workflow
  • Templates rebuilt, shortcodes and blocks converted
  • Content, media and internal links moved and rewritten
  • Redirects, SEO metadata, forms and integrations

Your team owns

  • The WordPress install and its hosting until the switch
  • Domain, DNS and email records
  • New CMS and hosting accounts, which replace the old WordPress hosting and its fees
  • Content decisions, sign-off and the go-live call
  • Writing and publishing after the handover

Platforms and tools provide

  • Your current host — backups, database access and the old install
  • The new host and CMS, and their uptime
  • Plugin and service vendors — subscriptions reviewed and cancelled or retained by their account owners after the replacement is verified

When leaving WordPress is the right step

It fits when keeping WordPress running costs more than the site's content needs. Four signs it is the right step now.

  • Upkeep eats the budget

    Plugin updates, security patches and hosting fixes take more time than new content.

  • Pages have grown slow

    A heavy theme, a page builder and stacked plugins weigh down every page.

  • The site is mostly content

    Posts, pages and forms — not a store or member area that lives on plugins.

  • The archive earns traffic

    Old posts bring search visits, so every permalink has to land somewhere.

A different starting point

Let's count what your WordPress site really runs on

Send us the address and the plugin list. We will come back with a useful scope — or tell you when staying on WordPress costs less.

Discuss your product Explore our work

Scope, access and who does what

Post types, the plugins to replace, the new stack and the switch window are agreed before anything moves.

Scope
Custom fixed or phased, set in the proposal
Timeline
Agreed after scope, access and dependencies
Discuss your migration

  1. You provide

    The install
    Admin access, a recent backup, and where the site is hosted.
    The plugins
    Which are active, and which ones your team actually relies on.
    The writers
    Who publishes, how often, and in which languages.
    The traffic
    Analytics and search console, so we know which posts earn visits.

  2. Who does what

    ANODA
    Takes stock of the install, rebuilds the templates, moves the content, replaces the plugins and runs the switch.
    Your team
    Grants access, decides which content and features stay, reviews each step and makes the go-live call.
    Your providers
    The current host until the switch, then the new host and CMS; replacement connections are tested before cutover, with any planned interruption agreed in advance.

  3. Boundaries

    Outside a WordPress migration
    Host-to-host moves that keep WordPress, a redesign, rewriting content, rebuilding a WooCommerce store or member site, and platform fees.
    After the switch
    Your team writes and publishes. Support, new templates and a next phase are scoped separately.

Related services

What is WordPress costing your team?

Tell us the site's address, roughly how many posts it holds, the plugins it depends on and who writes for it.

What do you need? *
Project budget (USD) *

What is your product, who uses it, and what would you like us to do?

    Within 15 minutes, we’ll reply with initial feedback and follow-up questions.

    Read more about running a website

    All articles

    WordPress Migration: common questions

    Is it worth leaving WordPress, or should we fix the site we have?

    Keep it when a large editorial team lives in the WordPress editor, the site depends on WooCommerce or membership plugins, or the pain is a tired theme that a rebuild on WordPress would fix — a WordPress rebuild may avoid the cost of replacing those workflows. Leave when the site is mostly posts, pages and forms, and upkeep, security patches and slow pages cost more than the flexibility is worth. We put that comparison in writing before anything is rebuilt.

    Which URLs, metadata and features must survive a WordPress to Astro move?

    The URLs that earn visits, including category, tag and author archives and feeds; each post's title, description and headings; alt text, featured images and captions; internal links; and the jobs the plugins did — forms, redirects, search, sitemaps and structured data. On Astro, posts become content files or entries in a headless CMS, templates become components, and each useful permalink either stays the same or gets a permanent redirect to a relevant replacement; deliberately retired content gets an agreed removal status.

    What happens to our plugins, shortcodes and page-builder layouts?

    Each gets a verdict. Plugins that shape content — SEO, forms, galleries, tables — are replaced by components or small services. Plugins that patch WordPress itself, such as caching and security, simply end with it. Shortcodes are converted to their component equivalents during import. Page-builder layouts are stored as builder markup rather than plain content, so key pages are rebuilt by hand and long-tail pages are cleaned up by script. Nothing is dropped without your sign-off.

    How do writers publish after a WordPress to Astro move?

    In a headless CMS with a familiar editor: a title, a body with headings, images and links, categories and tags, a draft, a preview and a publish button. For a static Astro site, we connect content changes to a build and deployment trigger. Preview, publishing and failure handling are configured for the chosen CMS. The CMS, integrations and build dependencies still need an owner for updates and access. Writers who prefer it can work in Markdown files instead. We set up roles and a review step if your team needs one, and the walkthrough covers the jobs they do every week, not a tour of every setting.

    Is this the same as moving WordPress to a new host?

    No. A host move copies the same WordPress install, database and plugins to another server, and the site stays on WordPress. This service is WordPress replatforming: the content leaves WordPress for a different stack, and the templates and plugin features are rebuilt there. We do not offer host-to-host moves as a separate service.

    What do WordPress migration services include?

    An inventory of post types, custom fields, taxonomies, media, shortcodes and plugins; a replacement plan; the new content model and CMS; templates rebuilt as components; content, media and internal links moved by script; forms, search and analytics replaced; redirects and SEO metadata carried over; a rehearsed switch with a way back; and a walkthrough for your writers.

    What do you need from us to start?

    Admin access to WordPress, a recent database backup or access to the host, and a list of the plugins your team relies on — not only the ones installed. Analytics and search console access, the tools the forms feed, and the people who write for the site. One person approves the new stack, the redirect map and the go-live date, and someone with DNS access is on hand for the switch.

    What do we get at handover, and can you keep working on the site?

    The site in your own repository and hosting account, the new CMS with your content in it, the inventory and replacement plan, the redirect map with its test record, a runbook for publishing and rollback, and a walkthrough for your writers. Afterwards we can add templates, continue the build on Astro, or test key paths with real readers, each scoped separately.

    What decides the scope, timeline and price?

    How many posts, pages and custom post types there are, how many plugins must be replaced, how much of the site was built with shortcodes or a page builder, languages, the forms and integrations, and how many URLs need redirects. We set a custom scope and estimate in the proposal, fixed or phased, and agree the timeline once scope, access and dependencies are clear.

    What is excluded, and what can we review before the rebuild?

    Host-to-host moves, a redesign, rewriting content, rebuilding a WooCommerce store or member site, and new platform, hosting or plugin fees are separate. The content inventory and plugin replacement plan come first. Then your writers try a complete template and publishing task in the new CMS, while we check its content, metadata and useful URL against the original. You approve the working approach before the archive move expands.