Migration cost quotes vary wildly because they are answering different questions. A quote for "rebuild the templates" and a quote for "migrate content, preserve SEO, and rebuild editor workflows" are not the same project, even for the same site.
Get a scoped estimate based on your actual site, not a generic range.
Use the migration cost calculatorThe main cost drivers
Page count matters less than most people expect. These factors move the estimate far more.
- Number of distinct templates and content types, not raw page count.
- Volume of custom fields, plugins, and integrations that need direct replacements.
- Whether the redirect map covers dozens of URLs or thousands.
- How much design work is included versus a like-for-like rebuild.
Typical ranges by project size
These are directional ranges for a marketing site migration, not a quote. Ecommerce, membership, or highly custom WordPress builds run higher.
- Small marketing site, under 20 pages, minimal custom fields: smaller end of the range, usually a few weeks of work.
- Mid-size site, 20 to 100 pages, blog, and a handful of custom content types: the most common project size, typically four to ten weeks.
- Large site, 100+ pages, multiple content types, heavy plugin dependence: significantly more scoping and QA time before build even starts.
What inflates cost unexpectedly
These are the items that turn a clean estimate into a much larger invoice, usually because they were not scoped upfront.
- Discovering undocumented plugin behavior that content depends on (custom shortcodes, hidden fields).
- A redirect list that was never properly inventoried, found only after launch.
- Design work bundled into what was scoped as a technical migration.
- No decision made in advance about which old content is worth migrating versus retiring.
How to get an accurate estimate
The estimate is only as good as the audit behind it. A quote given without seeing the actual WordPress install is a guess.
