Enough access exists.
Control can be transferred to your company — registrant corrected, accounts moved, renewals redirected. The work is administrative where the required access exists.
AMKA Digital / Website Takeover
Your previous developer is gone. The website doesn’t have to be.
Whether they closed shop, stopped replying, or simply moved on — the site, the domain and the email they set up are assets your company can usually recover. We map what you still control, take over what is recoverable, and say honestly what is not. Nothing is rebuilt before the mapping says a rebuild is justified.
AMKA / Decision guide
Recover control in dependency order
Renewal • registrant • accountDomain & DNS
WebsiteHosting → files → admin
Email & formsProvider → inbox → delivery
Map what is recoverable, rebuildable or negotiable.
02 / Recognise the situation
Three ways companies arrive here.
The common thread: the website still works, but nobody answerable holds its keys — and one renewal notice or one needed change away, that stops being a background problem.
Unreachable
The developer stopped replying.
Emails bounce or go unanswered, the invoice history just stops, and the small change you needed has been pending for months. Nobody is angry yet — but nobody is responsible either.
A letter arrived
A renewal is due — to someone else.
The domain or hosting notice went to the developer’s inbox, or the registration turns out to be in their name. The most time-critical version of this problem, because an expired domain takes the email down with it.
Frozen
The site works but cannot be touched.
No admin login, no idea where it is hosted, no backups anyone can find. The company outgrew the site years ago and every conversation about fixing it dies at “we don’t have access.”
03 / When access is incomplete
Three possible recovery positions.
Most takeovers start with some keys missing. The mapping puts every asset into one of three positions and states it in writing, so the decisions that follow stand on facts rather than hope.
Access is gone; content survives.
The visible pages can be reconstructed from the live site. Anything behind a login — databases, order history, custom systems — may not be recoverable, and we say which applies before quoting anything.
Someone still holds a key.
Most cases resolve with a polite, documented request and settled invoices. Where they do not, registrars and MYNIC act on evidence — escalation exists, as the last resort rather than the plan.
04 / The rules we work under
Four promises, in writing before any work starts.
No forced rebuild
The recovery mapping comes first, and it is allowed to conclude that the site is worth keeping as it stands. A site whose developer vanished is not necessarily a bad site — sometimes it needs nothing but a responsible caretaker and a renewed domain in the right name.
Ownership lands with you
The domain ends up registered to your company and billed at cost — not marked up, not in our name. Your content and business data are yours, on day one and on exit. What stays ours is our platform and build system, and we publish that boundary rather than bury it.
Care is a separate decision
Taking the site over and looking after it long-term are two different agreements. Once the immediate problem is solved and mapped, Website Care is offered with its prices published — never bundled into the rescue by stealth.
Quoted after access is mapped
The takeover work is priced after the mapping, from what it actually found — never a lump sum quoted to a worried caller. The urgency in these situations is real; it is not a pricing instrument, and we decline to use it as one.
Also honest: we cannot conjure access that no longer exists anywhere, compel an unresponsive third party, or recover databases that were never backed up. Where that is the situation, the mapping says so — before money moves, not after.