AGENCY CHANGE · WEBSITE RELAUNCH

A fresh start. With a proper handover.

You want to change your website or the team behind it? First we find out what exists, what works and what needs to move. A clear handover prevents important details from getting lost.

Discuss your current website ↗Go to checklist

HANDOVER CHECKLIST

Six things to clarify before moving.

Ownership & access

List the owners and administrators of domain, DNS, hosting, CMS, repository and email.
Arrange individual access or a secure handover. Do not paste passwords into an enquiry form.
Check which contracts, subscriptions and licences you control and who can export the data.

Content & assets

List important pages, downloads, products and contact routes.
Keep originals of copy, images, videos and brand files; clarify which uses have been agreed.
Export content and create backups before changing systems. Check that a restore is possible.

Technology & dependencies

Identify forms, shop, bookings, payment services, integrations and scheduled tasks.
Record DNS entries and mail routing. A website move must not accidentally interrupt email.
Record software versions and who is responsible for updates and hosting.

Search & measurement

List valuable existing URLs and review available Search Console and analytics data.
Map changed addresses to relevant new pages and check redirects.
Keep analytics consent and privacy settings in scope. Compare enquiries as well as visits.

Launch & continuity

Review the new website in a protected preview before switching.
Test mobile layouts, forms, downloads and agreed functions; define the rollback procedure.
Agree who changes DNS, approves the launch and checks email and the website afterwards.

Budget & handover

Agree what can be retained and what needs rebuilding after the technical review.
Quote migration, third-party fees and optional support separately where applicable.
Record deliverables, acceptance criteria, responsibilities and outstanding points.

Improve, migrate or rebuild?

Sometimes content and navigation need attention; sometimes the platform prevents the functions you need. We assess the existing system before committing to a takeover. Required access, usable exports and the technical condition determine the scope.

Explore website relaunches ↗

A clear cutover. A named contact.

We plan the change with you and, if you wish, with your previous provider. Responsibilities and approvals are recorded. Existing rankings cannot be guaranteed; URL mapping and monitoring help identify problems early.

Website already offline? Emergency help ↗

Before you decide

Can you take over every website?

That depends on access, technology, rights and the condition of the system. We may recommend a partial migration or a rebuild. We agree the feasible route after reviewing it.

Does a relaunch cost the same as a new website?

The published website packages explain the new website scope. Content migration, existing integrations, complex data and third-party costs may add work and are specified separately. View the price list.

Do we have to book ongoing support?

No. We agree handover and responsibilities. Optional content or technical support has its own scope, frequency and price.

What would you like to change?

Public URL, goal and deadline are enough to start. Please do not send credentials or private customer data.