A useful estimate starts after the site is understood. A small page count can still hide custom post types, forms, search, multilingual content, memberships, or an editorial workflow that must be rebuilt.
The scope drivers that change the work
Distinct page types require different content rules, components, responsive states, and QA.
Migration is different when content is clean and structured versus inconsistent, duplicated, or partly manual.
Structured content, taxonomies, relationships, and filters need a deliberate destination.
Delivery, spam protection, CRM, analytics, search, media, and email paths must still work.
Language structure, translation workflow, metadata, and URL conventions expand the map.
Transactions, customer data, memberships, and application state require deeper discovery.
Redirect verification, accessibility, content review, analytics, monitoring, and handoff determine confidence.
How to get a useful estimate
- Share the live URL and describe the recurring problem.
- Identify the content types, integrations, and publishing roles.
- Mark any store, membership, LMS, marketplace, or application behavior.
- Separate must-preserve workflows from features open to change.
- Use the audit to define a fix, modernization, or migration scope.
Our migration checklist helps you prepare the inventory. If you are still deciding whether a rebuild is justified, start with the maintenance-versus-migration matrix.