Skip to content

How to transfer website ownership, piece by piece

Indiemaker · Updated 17 November 2026

In short

You transfer website ownership one part at a time: code and content, database, hosting, DNS, the domain registration, email, analytics and payment accounts. Move them in the order that breaks least, with the domain and billing last. Take a full backup first, rotate every credential after, and release escrow only when the buyer controls every part alone.

What does it mean to transfer website ownership?

There is no single account called "the website". When people ask how to transfer website ownership, what they are moving is a set of separate accounts at separate companies, each with its own login, its own billing and its own transfer process. Miss one and the buyer owns a site they cannot fully run, or the seller keeps paying for something they no longer own.

So the first job is an inventory. Before any transfer starts, the seller writes down every part, where it lives and whose name and card are on it. That list goes into the sale agreement, and the buyer ticks it off line by line.

What are the parts, and how does each one move?

Part What it is How it usually changes hands Detail
Domain registration The right to the name Change of registrant, account push or registrar transfer Transfer a domain
DNS The records that point the name at servers and email Rebuilt in the buyer's DNS account, then nameservers repointed Below
Hosting The server or platform the site runs on Account or project transfer where the host allows it, otherwise a migration to the buyer's account The host's docs
Code and content Theme, plugins, application code, media files Repository transfer, or files copied in the migration Transfer a WordPress site
Database Posts, users, orders, settings Exported and restored, or moved with the hosting account Below
Email Mailboxes, forwarding and the sending service New accounts under the buyer, records updated in DNS Below
Analytics and search Traffic history and search performance data Buyer added with full rights, seller removed after Transfer Google Analytics
Payment accounts The processor that takes money Usually a new account in the buyer's name Transfer a Stripe account

Each platform sets its own rules, and they change. For any named service, read its current help page on the day rather than relying on a summary, including this one.

What order should the parts move in?

Move things in the order that breaks least if a step goes wrong. This matches the sequence in how to take over hosting, domains and payment accounts.

  1. Back up everything. Files, database and repository, taken before anything changes and stored somewhere the buyer controls.
  2. Code and content. The buyer receives the repository or the full file set and confirms they can build or restore the site from it.
  3. Hosting and database. Either the hosting account changes hands, or the site is migrated into the buyer's own account and tested on a temporary address.
  4. Third-party services. Email sending, forms, search, CDN, comment tools, ad networks, affiliate programmes. The buyer opens their own accounts and swaps credentials one service at a time.
  5. Rotate every credential. Admin passwords, API keys, database passwords, SSH keys and webhook secrets, including the ones the seller says are unused.
  6. DNS. Build the zone in the buyer's DNS account, copy every record, check it resolves, then repoint the nameservers.
  7. Payments. Complete the processor changeover and run a live test charge and refund.
  8. Analytics and search tools. Add the buyer as owner, confirm, then remove the seller.
  9. Domain registration. Move it once DNS is stable.
  10. Walk the list. The buyer confirms each line from their own logins.

The domain feels like the asset, so buyers want it first. It is safer near the end: a domain moved early can point at a server the buyer cannot log in to.

How do you move DNS and email without downtime?

Separate DNS from the registrar and do DNS first. Lower the TTLs on the existing records to 300 seconds a day before the move, so that a mistake can be corrected in minutes instead of hours. Copy every record exactly, including the ones nobody remembers adding.

Email is where sites quietly break. Mailboxes on the seller's hosting stop when that hosting stops. Sending services need their authentication records, SPF, DKIM and DMARC, in the new DNS zone before the cutover, or password resets and order receipts start landing in spam.

What does not transfer at all?

Some things do not move between owners in an asset sale, however cooperative the seller is.

  • Payment processor accounts are usually tied to the legal entity and the person who passed identity checks. Plan for a new account and a customer migration.
  • Ad network and affiliate accounts are often personal to the account holder. The buyer applies in their own name and replaces the tags and links.
  • Licences for themes, plugins, fonts and stock images may be single-owner. Check each one, and budget to rebuy.
  • Lock periods. Under ICANN's rules, a registrar can refuse a registrar transfer within 60 days of a domain's registration or a previous registrar transfer, and a change of registrant can start a 60-day lock of its own. Check the dates during due diligence.

Where the deal is a share sale, the company keeps its accounts and far less has to move. That is a different transaction with its own risks, and worth settling before transfer week.

How should the handover run inside a sale?

On Indiemaker, payment and handover run through Escrow.com: the buyer's money is held until the transfer is done. The inventory becomes the checklist that release depends on.

Before: agree the list, the order and a transfer window with both sides available. The existing guidance on this site puts the whole sequence at two to five working days.

During: the seller hands over one part at a time and the buyer confirms each from their own login. Nothing is "done" because the seller says so.

After: the buyer sets their own recovery email and two-factor authentication on every account, starting with the registrar, DNS and hosting, because those three can take the whole site with them. Put the buyer's card on every renewal. Keep the seller reachable for the agreed handover period, and ask for a short written runbook covering deploys, backups and whatever breaks most often.

If the seller stops responding before the list is complete, the money is still in escrow. That is the point of doing it this way.

Sources

Related: how-to-take-over-hosting-domains-and-payments, stack-transfer, transfer/domain, transfer/wordpress-site

When you are ready to read real listings.

Everything on sale, on the same fields, from $1,000 to $500,000.