Receive
Collect ownership records, exports, inventories, account roles and support references.
Ownership · evidence · acceptance
Free supplier and domain handover pack.
Turn a supplier change, ownership move or project close into a practical acceptance record for domains, DNS, hosting, repositories, connected services, recovery and access removal.
Build the handover packBuild evidence before sign-off
Record what arrived, then verify that it works.
A file or login is not automatically a successful handover. Use current provider screens, exports, test restores, named access and agreed acceptance checks to support each answer.
Received & verifiedThe receiving team checked usable evidence
Received, not verifiedMaterial arrived but still needs testing
OutstandingThe item or evidence has not arrived
Not applicableOut of scope with a recorded reason
An acceptance sequence
Receive, verify, then remove old access.
Keep a short overlap where it is safe and contractually permitted. The receiving team needs time to prove control and recoverability before the outgoing route disappears.
Verify
Sign in with named access, inspect evidence, restore a sample and rehearse an approved change.
Close
Accept known exceptions, rotate or revoke old access, and retain the final record.
Keep the handover safe
Record where evidence lives—not the secret itself.
The pack is designed for ownership, status and references. Use the organisation's approved password manager, vault and secure transfer process for sensitive material.
Keep secrets elsewhere
Never paste passwords, API keys, private keys, auth codes, tokens, recovery codes, payment-card data or unnecessary personal information here.
Test before revoking
Verify named access, deployment, monitoring, billing and recovery before removing the only working supplier route.
Contracts still govern
Transfer rights, data return, retention, deletion, licence assignment and exit support depend on the contract, providers and applicable law.
Current primary guidance
Check the provider and contract before making the move.
Registrar rules, service features and contracts differ. These official sources explain the main ownership, supplier-access and end-of-contract questions behind the pack.
ICANN information for domain registrantsRegistrant responsibilities, registrar management, renewal and transfer resources
ICANN guidance on Auth-CodesWhat a domain transfer code does and how registrants obtain one
NCSC supply-chain control guidanceSupplier access, least privilege, monitoring and removal when no longer required
NCSC supplier assurance questionsContract exit, service transfer and secure return or deletion of data and assets
ICO controller–processor contract guidanceEnd-of-contract return or deletion, copies, backups and continuing safeguards
Common handover questions
Supplier and domain handover FAQ.
Does this tool transfer our domain or supplier accounts?
No. It creates a checklist and acceptance record from your answers. Transfers, role changes and access removal must happen through the relevant registrar, provider and contract process.
Should we paste passwords or domain transfer codes here?
No. Put sensitive values in an approved password manager, vault or secure exchange. In this pack, record the account name, owner and where authorised evidence is held.
Is receiving an export enough to accept a handover?
Usually not. The receiving team should confirm scope and dependencies, inspect the material and run proportionate access, deployment or restore checks before sign-off.
When should the outgoing supplier's access be removed?
Use the agreed contract and acceptance plan. In many handovers, access is removed after the receiving team has verified control and recovery, with evidence retained and urgent support routes understood.
Need an independent handover review?
Turn the pack into an orderly, testable transition.
ACA Tech Solutions can help UK organisations inventory domains and services, verify access and recovery, plan cutover and document unresolved supplier risks.