# Website migration assessment

Canonical: https://beyondphp.com/migration/website-migration-assessment/

Language: English

Reviewed: 2026-10-22

Migration / BeyondPHP

A clear recommendation can save you from rebuilding the wrong thing.

[Discuss your project](https://beyondphp.com/contact/)

The useful answer

A migration assessment produces a decision: what is suitable to move, what must be retained, what needs further investigation and whether a rebuild is worthwhile. It should end with a bounded scope and open questions, not an assumed commitment to migrate.

Reviewed 22 October 2026 · [BeyondPHP](https://beyondphp.com/editorial/)

## Begin with the business reason for moving

Document the problem the business is trying to solve: difficult editing, confusing navigation, inconsistent design or a specific performance issue. Record the consequences and priorities. If the real problem is incomplete product information, changing the delivery method will not fix it. The assessment should connect each proposed change to a visitor or operational need.

## Build a usable evidence inventory

Combine a page list with functional walkthroughs and available ownership records. Mark access gaps rather than treating them as absence. Analytics and search data can inform priorities when authorised access exists; missing data should remain an explicit limitation. The inventory also needs downloads, enquiry destinations, language versions and services controlled by someone outside the project.

## Receive options with clear boundaries

The output should distinguish a suitable public-page rebuild, retained operational functions and unresolved dependencies. Include assumptions, proposed URL treatment, content workload, update ownership and release requirements. Where the evidence is insufficient, recommend a narrower investigation. A useful assessment may conclude that improving the current site is more proportionate than replacing it.

A practical next step

## What to prepare.

- **Business objective** Provide the problem, desired result and any firm deadlines.

- **Ownership list** Identify domain, hosting, content and integration owners without sharing secrets in a public form.

- **Known workflows** Demonstrate how a real visitor enquiry or transaction reaches the business.

## Questions worth asking.

Does an assessment include a rebuild?

No. Discovery and implementation are separate scopes unless the written proposal explicitly combines them.

What if access is incomplete?

We record the limitation and identify the smallest additional check needed for a responsible recommendation.

Can the recommendation be to stay?

Yes. Keeping and improving an existing system is a valid outcome when the evidence supports it.

Continue with the right context

## Useful next reads.

[Migration Modernising an existing PHP website Separate public content from application features and choose a proportionate modernisation plan for an existing PHP website.](https://beyondphp.com/migration/php-website-modernization/)

[Migration WordPress to static website migration Assess which parts of your WordPress site can become a simpler public website, with content, URL and operational planning before a rebuild.](https://beyondphp.com/migration/wordpress-to-static/)

[Insights Content audit before a website redesign Decide what to retain, revise, combine and retire so a redesign improves information rather than repackaging the same clutter.](https://beyondphp.com/insights/content-audit-before-a-website-redesign/)