Skip to content
Orvenant
Orvenant

Website redesign & migration

Website redesign and migration, planned around what works

Website redesign and migration with content, URLs and business continuity planned together. Improve the experience while protecting the journeys people and search engines already use. For Joomla and WordPress sites, we compare the upgrade and modernization routes before choosing one.

Change the site without losing the paths people use.

A redesign touches more than color and layout. Customers may rely on familiar pages, search engines know existing URLs, and internal teams depend on forms, publishing and reporting. We start with an inventory of those working parts. The aim is to make the new site clearer while making conscious decisions about what to preserve, improve, combine or retire. That is especially important when the redesign also changes CMS or hosting.

Treat design and migration as one project.

The exact scope depends on the current site and the target platform. These workstreams need one coordinated plan.

Current-state review

We inventory important URLs, content, media, integrations, forms and customer journeys. Search Console and analytics data can inform priorities when available, but numbers are checked against business value. We record content that needs an owner decision rather than quietly moving every old page.

Experience and content plan

Navigation, page hierarchy and visual patterns are designed around the new offer and the audience's questions. Each retained page gets a destination and a content action: keep, rewrite, combine or remove. Design reviews use realistic copy and mobile layouts rather than empty boxes.

View Website design

Cutover and verification

Moved pages receive relevant redirect mappings. We test canonical URLs, metadata, structured data where appropriate, internal links, forms and key journeys before launch. The release plan names rollback triggers and the checks to repeat after DNS or deployment changes.

Modernizing a Joomla or WordPress site

A redesign of a Joomla or WordPress site includes a platform decision: upgrade the current CMS, move to a fresh installation, keep the CMS for editors behind a new public website, or rebuild on another platform.

Joomla migration & upgrades

Upgrade or migrate a Joomla 3, 4 or 5 site to Joomla 6, starting with an assessment: version paths, extension and template checks, a rehearsal and a rollback plan.

View Joomla migration & upgrades

Joomla to modern stack migration

Moving a Joomla site to a modern stack with its feeds, users and URLs, when an upgrade is no longer the right route.

View Joomla to modern stack migration

WordPress development

A better maintained WordPress site, a headless publishing setup or a complete migration, with each dependency treated as a decision.

View WordPress development

What should survive the change?

A page with little traffic may still answer an important customer question. A high-traffic page may attract the wrong audience. We review both search evidence and customer value before removing content. We also decide who approves rewritten facts, when old URLs can disappear and whether current analytics data can be compared fairly with the new setup. No migration can promise unchanged rankings, but the risks can be made visible and managed.

Rehearse the move before changing traffic.

A target environment lets us check pages, redirects, forms, media, accessibility and editor workflows before public cutover. We verify representative URLs from outside the hosting system and confirm that staging restrictions do not leak into production. If the CMS changes, editors test their common tasks with migrated content. The cutover checklist assigns each check to an owner and records what to do if it fails.

Keep a record after launch.

The team receives the redirect map, known exceptions, content decisions and post-launch monitoring tasks. Search engines may process the new structure over time, so we monitor indexing and errors rather than treating launch day as proof of success. Ongoing content, maintenance and optimization can be scoped separately from the redesign delivery.

Some of the teams we have worked with.

Across talent, fitness, mobility, payments and local commerce.
RandstadClassPassVeezuRushpaySupport Black Owned

Questions before we start.

Will a redesign preserve our search traffic?

No one can guarantee that outcome. We reduce avoidable risk by inventorying valuable content and URLs, mapping relevant redirects, preserving useful information and checking technical signals before and after launch. We also monitor real indexing and enquiries once the new site is live.

Do we have to replace our CMS or domain?

No. We assess the current CMS and domain against your goals. A redesign can keep both, or include a carefully planned migration when there is a strong reason. Changing several systems at once increases coordination and recovery work, so we make that tradeoff explicit.

What should our team prepare?

Access to the current site, a list of important customer journeys, known integrations and someone who can approve content and removals. Search and analytics access is useful if available. Sensitive credentials should be shared through an agreed secure mechanism, not by ordinary email.

A DIRECT CONVERSATION

Bring us the problem. We’ll work through the next step.

Share what exists today and what you want to change. We can discuss the scope, dependencies and a practical way forward.

Privacy settings

Each option stays off unless you allow it. Enquiry contents and contact details are never sent to Google.

Optional measurement

Google Analytics cookies measure visits and pages, traffic sources and campaigns, approximate location and devices.

Google signals adds age, gender, interest and cross-device reports, and Google may also use this data to personalize ads. Requires Analytics.

Withdrawing stops future collection and removes this site’s accessible Google cookies. It does not erase information already received by Google. Privacy notice · Cookie notice