How to Transfer a Website After a Sale (Checklist)

The deal is agreed and the money is in escrow. Now comes the part that decides whether both sides walk away happy: the handover. A clear, ordered transfer avoids downtime, lost income and disputes. Use this checklist whether you are the seller or the buyer.

Before the transfer starts

• Confirm the payment is secured. The seller should only begin once the escrow service itself confirms it holds the buyer's money.
• Agree the order of steps and who does each one.
• Agree the inspection period and what counts as complete for each asset.
• Make a full asset list, including what will not transfer and what the buyer must set up themselves.
• Take a full backup of the site, database and important files before anything moves.

Step 1: Analytics and Search Console

Add the buyer as an owner or administrator of Google Analytics and Search Console first. This lets the buyer watch traffic during the rest of the handover and keeps the history in place. Once the buyer has full access and confirms it, the seller can remove themselves at the end.

Step 2: Domain name

Two common ways:

• Same registrar: the seller pushes the domain to the buyer's account at the same registrar. This is usually quick.
• Different registrar: the seller unlocks the domain, disables privacy if needed, and gives the buyer the transfer (authorization) code. The buyer starts the transfer at their registrar. This can take several days.

Note that many registrars do not allow a transfer to another registrar for a period after registration or a previous transfer. Check this early.

Before moving the domain, write down the current DNS records so the site and email keep working.

Step 3: Hosting and files

Choose one approach:

• Transfer the hosting account, if the host allows it and the account holds only this site.
• Migrate the site to the buyer's hosting: copy files and database, set up the site, test it on the new host, then point the domain to it.

For WordPress sites, a migration plugin or a manual copy of files and the database both work. For custom code, transfer the repository and document the environment settings.

Step 4: Email and DNS

• Recreate any email accounts on the domain, or confirm the buyer's own email setup.
• Update DNS records carefully: the site, email (MX), verification records and anything else that was in place.
• Check that contact forms still deliver to the right inbox.

Step 5: Monetization

• Ad networks: accounts usually belong to the publisher. Keep the seller's ads running until the buyer's own account is approved, then swap the ad code. Agree how income during the switch is shared.
• Affiliate programs: some allow account transfers, others require the buyer to join and replace links. Make a list of programs and their links.
• Payment processors and stores: for SaaS and stores, follow each provider's process. Customer subscriptions often cannot be moved simply, so plan this carefully.

Step 6: Content and assets

• Images, logos, design files and fonts with licences.
• Content documents and drafts.
• Plugin and theme licences that can transfer.
• Any videos, downloads or digital products.

Step 7: Email list and social accounts

• Export the email list and import it into the buyer's email platform, or transfer the account where allowed. Respect the platform's rules and the law on consent.
• Transfer social media accounts using each platform's own ownership or admin features. Change recovery emails and phone numbers.

Step 8: Tools, contractors and suppliers

• Transfer or cancel subscriptions to tools.
• Introduce writers, developers, virtual assistants and suppliers who will keep working.
• Hand over documented processes.

Step 9: Buyer's checks

The buyer confirms, for each asset:

• it is in their name and under their login,
• passwords and recovery emails are changed,
• the site loads correctly on the new setup,
• tracking and income are working,
• backups exist on their side.

Step 10: Release the money

When every agreed item is complete and checked, the buyer approves release in the escrow service, and the seller receives the payment. If something is missing, the buyer raises it in writing before the inspection period ends.

Step 11: After the transfer

• The seller removes their remaining access.
• The seller provides any agreed support for the agreed period.
• Both sides keep records of the transfer for their files.
• The seller marks the listing as sold and closes any other listings.

A sample transfer timeline

Every deal is different, but a typical small website handover follows a pattern like this. Agree your own version in writing before any money moves.

• Day 0: The agreement is signed, and the buyer pays into escrow. The seller receives confirmation from the escrow service, not from the buyer.
• Day 1: The seller shares the asset list and adds the buyer to analytics and Search Console. The buyer confirms they can see the same numbers as during due diligence.
• Days 1 to 3: The site files and database move to the buyer's hosting, or the hosting account itself changes owner. The buyer tests the copy on a temporary address before DNS changes.
• Days 2 to 5: DNS points to the new hosting. Both sides check that pages, forms, email and checkout work.
• Days 3 to 10: The domain moves to the buyer's registrar account. A push within the same registrar is often instant; a move between registrars can take several days.
• Days 5 to 14: The buyer opens their own ad, affiliate and payment accounts. The seller keeps their accounts running and passes on income as agreed until the buyer is approved.
• Inspection period: The buyer checks each item against the asset list and then releases the payment.
• Support period: The seller answers questions for the agreed time, often 30 days.

Writing the timeline down helps both sides. The seller knows when to expect payment, and the buyer knows when each asset should arrive.

Building the asset list

The asset list is the backbone of a smooth transfer. It should name every item the price includes, who holds it today, and how it will move. A simple table works well:

Attach the list to the written agreement. If something is not on the list, assume it is not included, and ask about it before paying.

Common transfer problems and how to avoid them

• Domain stuck in a transfer lock: check the registration and transfer dates early.
• Site down after DNS changes: copy every DNS record before changing anything, and lower the TTL a day ahead.
• Income gap: keep the seller's monetization running until the buyer's accounts are approved.
• Missing licences: list paid themes, plugins and fonts and check their transfer terms.
• Lost history: move analytics access rather than starting new properties.

Selling? Prepare your asset list before you list: start your listing. Buying? Browse businesses for sale.

Frequently asked questions

How long does a website transfer take?

Simple sites can be handed over in a day or two. Domain transfers between registrars and complex migrations can take a week or more.

Should the domain or the hosting move first?

Usually analytics access first, then hosting or migration, then the domain, so the site keeps working throughout. Agree the order with the other side in advance.

What if an ad network account cannot be transferred?

That is common. The buyer applies for their own account; the seller keeps the ads running until it is approved, as agreed in writing.

Can the seller keep a copy of the content?

Not usually. The agreement should say the seller deletes their copies and will not republish the content elsewhere. Duplicate content can hurt the buyer's search rankings.

Who pays for the domain transfer fee?

It depends on the agreement. Registrar fees are small, and many buyers simply cover them because the domain will renew in their name anyway.

When should the buyer release the escrow payment?

Only after every agreed asset is in the buyer's name and working.