Statamic
WordPress to Statamic migration cost: how to scope it
There is no fair price list for this, because two sites with the same page count can differ hugely. Here is how to measure yours in an afternoon, so that the quotes you get are about your site.
By itmarkerz Technologies. Updated 30 October 2026.
Count these first
If you have shell access, WP-CLI gets you most of this in minutes. Otherwise a plugin list and an export from the admin will do. The rightmost column shows how to get each one.
| What to count | Why it moves the cost | How to get it |
|---|---|---|
| Content types | Each custom post type and its fields becomes a collection and blueprint | wp post-type list --public=true |
| Posts and pages | Volume matters less than variety, but it sets QA and import run times | wp post list --post_type=post --format=count |
| Custom fields | Field groups map to blueprints. Repeaters and relationships need thought | Your ACF or field plugin's export |
| Page-builder pages | Often the largest line, because layouts stored as shortcodes or builder data rarely transfer cleanly | Sample ten pages, and look at their raw content |
| Active plugins | Each one is replaced by a Statamic feature, an addon, custom code, or dropped | wp plugin list --status=active |
| Forms | Rebuild them, and reconnect where submissions go | List each form and its destination |
| Users | Editors need accounts and roles. Member or customer accounts are a bigger question | wp user list --format=count |
| Languages | Translations need mapping across sites, and redirects per language | Your translation plugin's settings |
| Media | Files move, but references inside content have to be rewritten, and old sizes dealt with | Upload folder size, and a sample of old posts |
| URLs | Every indexed URL needs a home or a redirect | Your sitemap and a Search Console export |
wp post-type list --public=true
wp post list --post_type=post --format=count
wp post list --post_type=page --format=count
wp plugin list --status=active
wp user list --format=countThe part that surprises people
It is usually page-builder content. A post written in the block editor is structured, and Statamic’s Importer addon has special handling for Gutenberg. A page built with a visual builder is often a pile of shortcodes or builder data, and the migration becomes a redesign of that page’s structure. If most of your important pages are like that, budget for rebuilding them, not importing them.
The other surprise is plugins that quietly do something the business relies on: a redirect list, a schema output, a form routed to a CRM. Go through the active plugin list and, for each one, write down what would break if it vanished.
What a migration quote should include
- A content model, agreed before any design or import.
- A trial import, with a sample reviewed by the people who will edit the site.
- A decision on each active plugin: replace, rebuild or drop.
- A full URL list, with a redirect for every address that changes.
- Titles, descriptions and structured data carried across, and compared before launch.
- The Statamic licence in your name, either directly or by transfer.
- Hosting that meets the Statamic requirements.
- A rollback plan for launch day.
If a quote leaves one out, ask who is doing it. The cheapest proposals often save money by skipping the redirect work, and you discover it later in Search Console.
Is it worth doing?
A migration replaces known costs with a one-off project and different running costs. It makes sense if upkeep and plugin conflicts are costing you regularly, or if your developers already work in Laravel. It rarely makes sense just because a WordPress site feels old. Statamic vs WordPress covers that decision, and the Statamic cost calculator shows the running costs once you have quotes.
How we price this
We quote after seeing the export and plugin list, and we don’t publish a price band. Our Statamic development page describes the process. Send us your counts if you would like an approach and a way to price it. We have no public Statamic migration case study on this site. Most of our work is delivered under NDA, so many projects cannot be named.
For SEO detail, see our WordPress to Statamic SEO checklist.
Questions
How much does it cost to migrate from WordPress to Statamic?
We can't give an honest general figure. The fixed part is the Statamic licence, which is $349 for Pro, and free during development. The rest depends on what your counts show on this page. We quote after seeing an export and the plugin list.
Is there an official import tool?
Yes. Statamic's Importer addon (statamic/importer) imports entries, taxonomy terms and users from CSV and XML files, and has field mapping and special handling for Gutenberg content. Page-builder content and shortcodes generally still need attention.
Will we lose our search rankings?
Nobody can promise they won't move. You limit the risk by keeping URLs where possible, mapping every old URL to a redirect, carrying titles and descriptions across, and comparing the two sites before going live. Our guides on the SEO side cover this in detail.
Can we move WooCommerce too?
Treat that as a different project and question. Statamic has no equivalent of WooCommerce built in, so a shop usually stays on a commerce platform.
More on Statamic
- Statamic cost in 2026: licence, build, maintenanceCurrent licence prices and a calculator for your own build and hosting figures.
- Statamic vs WordPress: a side-by-side comparisonFrom an agency that builds on both, including when WordPress is the better pick.
- Statamic vs Craft CMS: pricing, stack and fitPrices, limits and requirements side by side, with sources.
- How to choose a Statamic agency: 10 questions to askWhat partner badges mean, and the questions that separate agencies.
- Statamic hosting requirements: what your server needsPHP, extensions, version ranges, caching and what to ask a host.
Send us your counts
Your plugin list and a content export are enough to start. We will come back with an approach and a way to price it.
We reply within one business day (IST).