Skip to the main content
{}

Website takeover

Have your existing website managed by one technical contact.

Your website was built by another agency, or your current developer is no longer available. Jordy investigates how it runs, what access is available and what can responsibly be taken over. We then agree on management, maintenance and any improvements.

What we review before taking over

01

Technology and current condition

We document the CMS or framework, versions, themes, plugins, source code and setup. Known issues and important visitor journeys are recorded so it is clear what can stay and what needs attention first.

02

Access, accounts and licences

We identify who manages the domain, hosting, repository and external accounts. Your authority and available rights are checked. Missing access or licences are discussed before responsibilities are accepted.

03

Backups and checks before changes

We review available backups and what is needed to roll changes back. A restore test or separate test environment is included when feasible within the agreed scope and technology.

04

Hosting, domain and integrations

Taking over management does not automatically require moving your hosting. If a move is needed, we review DNS, mailboxes, certificates and external integrations and agree the steps and responsibilities in advance.

05

Preserve useful content and features

Pages, URLs, images, forms and existing measurement are documented. We agree which visitor journeys will be checked after handover and how any URL changes will be handled.

06

Clear follow-up arrangements

You receive a summary of the current setup, outstanding access questions, risks and recommended next steps. The initial takeover, recurring maintenance, hosting and new development are scoped separately.

Understand the website before taking responsibility for it.

A takeover starts with a review. This helps identify unknown dependencies or missing access before changes begin. If a component cannot responsibly be supported, we discuss the available options first.

  • 01An existing website does not automatically need to be rebuilt.
  • 02You can keep your current hosting provider when the agreed work is feasible in that environment.
  • 03Tasks, contact points, costs and any response times are agreed in advance.

Our approach

From an existing website to a clear handover

Scope and responsibilities are clarified first. We then build and verify the solution in controlled steps.

  1. Introduction

    Share your website address, its technology if known and why you want to switch. Describe what is not working well today.

  2. Review and proposal

    We examine the available information and access. You receive a proposal for takeover, necessary fixes and any further support.

  3. Prepare the handover

    Accounts, licences, backups and contact with the current manager are coordinated. Any migration and rollback approach are planned separately.

  4. Check and follow up

    We check the agreed pages, forms and integrations. You receive the responsibilities, checks performed and outstanding items.

Website takeover questions

Can you take over a website built by another agency?

Yes, if you are authorised to transfer management and the technology can responsibly be supported. We begin with the website, accounts, available source code and arrangements with the current provider.

Do I need to move my hosting or domain?

Not automatically. We assess whether the existing environment supports the agreed work. If a migration is needed, hosting, DNS, mailboxes and responsibilities are reviewed first.

Can you take over a WordPress website?

Yes. We review the WordPress installation, theme, plugins, versions, licences and backup options. This determines a suitable takeover and follow-up scope.

What if I do not have all the access yet?

Explain which accounts you do and do not manage. We identify the access needed and who can transfer it. Missing access can block parts of the takeover, so we agree how to address it first.

Is maintenance included in the takeover?

The initial takeover and recurring maintenance each have a defined scope. Updates, backups, monitoring, small changes and any response times are included only when agreed.

What does a website takeover cost?

It depends on the technology, available access, current condition and any migration. The review leads to a defined proposal. Hosting, licences, remedial work and new features are listed separately.

Have Codegenie take over your website?

Send your website address and describe the current situation and support you need. Mention missing access, but do not share passwords or customer data.