Contents
An audit before a redesign or migration establishes what really exists (content, data, URLs, extensions, integrations, traffic) and what must survive the switchover. It lets you choose between fixing the current site, redesigning it or migrating it, and prepares the switch without losing data or search rankings: URL inventory, redirect plan, test copy and acceptance test plan.
Rebuilding a site or changing technology is risky when you go in blind: forgotten content, URLs that drop out of Google, an essential extension that does not exist in the new version. An upfront audit turns these surprises into a work list.
What the audit must establish
| Inventory | Why |
|---|---|
| Pages and URLs, with their traffic | Know which pages matter and prepare redirects |
| Content and media | The real volume to carry over, attachments, downloadable files |
| Data | User accounts, orders, messages, history: structure and volume |
| Extensions and modules | What exists in the target version, what must be replaced or dropped |
| Customizations | Hand-edited code, invisible until you look for it |
| Integrations | Payments, CRM, email, third-party tools to reconnect |
| Hosting | What the target needs: PHP version, database, disk space |
| Search | Pages that bring traffic, inbound links, tags to keep |
Fix, redesign or migrate: the decision grid
| Situation | Usual recommendation |
|---|---|
| Maintained software, slow or fragile site | Fix: updates, cleanup, performance |
| Unmaintained software, but a recent version exists | Migrate to the maintained version, carrying over the data |
| Dated design, content and structure to rethink | Redesign, keeping the URLs that matter |
| The site has become a management tool (bookings, accounts, processes) | Consider a custom application, as for the La Bulle guesthouse |
A real example: 397,614 posts to carry over
A car club’s forum ran on phpBB 3.2.1, a version no longer supported, with extensions added over the years. The audit started with the inventory: 3 modified core files, 46 active extensions, 2,477 members, 28,409 topics, 397,614 posts and 143,780 attachments totaling 80 GB. It concluded that a migration to phpBB 3.3.19 was possible without a redesign, provided the extensions were handled one by one.
The migration followed the plan from the audit: a protected, non-indexed test copy with outgoing email turned off, an official upgrade with no changes to the core, 29 extensions brought back (updated or replaced with maintained versions), a dated log of every change, and an acceptance test plan handed to the club before the switch. Details are in car club forum.
Preparing the switchover
- A protected test copy, not indexed, with outgoing email turned off.
- Data migration and volume checks: same number of accounts, posts and files.
- A 301 redirect plan for every URL that changes.
- An acceptance test plan: the list of journeys to test, approved with you.
- A final sync at switchover, then closer monitoring for the first days.
Process and pricing
The audit before a redesign or migration builds on the full audit at $2,200 (€1,990)excl. VAT: inventory, risks, a reasoned recommendation and a costed plan, with a 2-hour debrief. For a very large site or several sites, it is quoted after a 30-minute call. If the decision leans toward a custom application, the estimator gives a first range.
Frequently asked questions
Does a redesign hurt search rankings?
It can, when URLs change without redirects, pages that drew traffic disappear, or content is rewritten without regard for what worked. The audit lists the pages that matter and prepares the 301 redirects before the switch, not after.
How long before launch should the audit happen?
Before you even choose the solution. The audit is there to decide between fixing, redesigning or migrating: doing it after signing a redesign means discovering the constraints halfway through the project.
Can we migrate without taking the site down?
Yes, in most cases. The new site is prepared on a protected test copy, the data is carried over a first time, then a final sync happens at switchover. Downtime is then limited to a few minutes or a few hours.
My CMS is no longer maintained: do I have to rebuild everything?
No. Upgrading to a maintained version of the same software is often possible and much cheaper than a redesign. The audit tells you whether it is feasible, what will be lost and what must be replaced.