Start with the practical answer
A representative Migranetix analysis provides the useful estimate. It identifies the supported source path, record counts, structures, dependencies, exceptions, and destination gaps instead of pricing from a page count alone.
Use the Drupal to WordPress scope to confirm the direction, then calculate an estimate from the application.
Price the workstreams that produce acceptance evidence
| Workstream | What changes effort |
|---|---|
| Core content | Bundles, fields, users, terms, comments, menus, media, and relationships |
| Module data | Paragraphs, Field Collections, Webforms, Views, commerce, custom entities, and tables |
| SEO continuity | Aliases, historical redirects, metadata, languages, files, sitemaps, and monitoring |
| WordPress preparation | Post types, taxonomies, fields, blocks, plugins, templates, permissions, and hosting |
| Validation and cutover | Dry runs, reconciliation, sampling, fixes, delta, launch, rollback, and stabilization |
The main cost drivers
Effort rises with bundle and field diversity, multivalue or compound fields, deep entity references, file volume, private assets, Paragraphs, custom modules, multiple languages, historical URLs, inconsistent source data, and strict validation or cutover windows.
The Drupal import guide shows how these dependencies affect the transfer plan.
When fixed packages fit
A fixed package fits when the source, destination model, included records, transformations, limits, validation, exclusions, and acceptance criteria are bounded. Complex module behavior, custom destination development, remediation, third-party licences, and changing scope need separate treatment.
Information needed for a useful estimate
Provide Drupal version, access method, bundle and record counts, field inventory, users, terms, comments, files, languages, modules, Paragraphs or custom entities, URL and redirect counts, WordPress readiness, cutover constraints, and required acceptance evidence.
For a legacy installation, use the Drupal 7 guide to complete discovery.
Common exclusions to confirm
Confirm whether the estimate includes WordPress design and development, theme recreation, plugin licences, module-feature replacement, content rewriting, manual cleanup, accessibility remediation, hosting, DNS, security hardening, training, post-launch support, and third-party integration work.
Reduce avoidable migration cost
Remove obsolete content with approval, fix broken references, choose final WordPress structures early, secure representative access, define redirect ownership, freeze late schema changes, and agree on acceptance checks before full transfer.
Do not cut the dry run or validation that exposes expensive production defects. The redirect and SEO guide helps bound launch work.
Calculate the estimate from analyzed scope
Connect the source and destination, review discovered data and mappings, and use the estimate to decide whether the scope fits self-service execution or needs a bounded package. Recalculate when the source model, destination, included data, or acceptance requirements change.