Transfer guides

Hand over the account, not the password

Short, provider-specific guides for freelancers moving domains, hosting, email, DNS, repositories, and analytics into the client’s control.

Domains

GoDaddy domain

A GoDaddy domain handover is usually a choice between an internal account move and a transfer to your client's registrar. Start by deciding which one your...

Read the handover →

Namecheap domain

A Namecheap domain handover is cleanest when your client already knows where the domain should live next. If it stays at Namecheap, treat it as account...

Read the handover →

Cloudflare domain

A Cloudflare domain can mean two different things: the registrar record and the Cloudflare zone that serves the site. Handing it to a client works best when...

Read the handover →

Hosting

Hostinger site

A Hostinger hosting handover is mostly about a WordPress website moving from your hPanel to your client's active hosting plan. It doesn't automatically carry...

Read the handover →

SiteGround site

A SiteGround handover transfers the website rather than the whole hosting plan. That distinction matters because your client needs room to accept the site,...

Read the handover →

WP Engine site

A WP Engine handover uses the language of sites and environments. For a client project, that usually means checking production, staging, development,...

Read the handover →

Vercel project

A Vercel handover is a project transfer between teams, not a copy of a deployment. Your client's team becomes the place where builds, domains, environment...

Read the handover →

Email

DNS

Repositories

GitHub repository

A GitHub repository handover should leave the client with ownership of the code and leave you with only the access they still need. The transfer is a real...

Read the handover →

Analytics