Do you need to hand over the website to a client, change developers or transfer the business to a new owner? A search for “transfer WordPress website ownership” often refers to two different processes: transferring the ownership account or technically moving the website to another hosting provider.
A proper migration also includes the domain, email accounts, licences, backups, SEO tools and administrative access. If any of these elements are missing, the website may remain online but become difficult to manage.
Before you begin, you need to work out which version of WordPress you are using and which resources need to be handed over to the new manager.
“Transferring ownership of a WordPress site”: what does it really mean?
The term ‘property’ does not have the same meaning on WordPress.com as it does on a WordPress installation hosted on a personal or business server.
WordPress.com
On WordPress.com, the site migration can be initiated by the current owner from the dashboard. The path is generally Settings, General, Transfer site. During the process, you will be asked for the new owner’s username or email address.
The new owner receives a notification and must authorise the transfer. The transfer of a domain purchased on WordPress.com, however, follows a separate procedure. Generally, the new owner must already be an administrator of the site.
WordPress.org and independent hosting
On a self-hosted WordPress site, there is no single button to transfer ownership. Control depends on the set of accounts and linked services:
- domain and registrar;
- hosting and billing panel;
- WordPress administrator users;
- databases and website files;
- premium themes, plugins and licences;
- Google Analytics 4, Search Console and Tag Manager;
- business email, backups and SSL certificates.
For this reason, simply transferring the WordPress password is not enough. The new owner would be able to manage the website, but would not be able to renew the domain or make changes to the server.
Before the migration, prepare your inventory and backups
The handover must start with the documentation, not with changing login details. Create a shared file on Google Drive or Notion containing the list of accounts, deadlines, technical contacts and outstanding tasks.
It also specifies who approves the changes, which service each supplier manages, and which access rights need to be transferred. This document avoids the need to rely on memory and reduces problems during handover.
Please provide at least the following information:
- domain name, registrar, expiry date and transfer code, if the domain is being transferred to a different account;
- hosting, active plan, billing details and access to the control panel;
- WordPress users, administrative email addresses and FTP or SSH access;
- themes, plugins, licences, API keys and associated external services;
- Analytics, Search Console, Tag Manager and advertising tools;
- backups, staging environment, SSL certificate, CDN and email accounts.
Do not send passwords in a plain email or in an unsecured document. Use separate personal accounts and, where possible, a password manager. The new account holder must be given individual access details, not credentials shared with the whole team.
Carry out a full backup before making any changes. Save files, databases, configurations, media and important settings. If the transfer involves an e-commerce site, also retain orders, customers and products in accordance with the agreed procedures and in compliance with data management obligations.
A useful backup isn’t just one that exists on the server. It’s one that you can download and restore before delivery.
How to transfer a WordPress site to a new hosting provider
If the website remains on the same hosting provider, it may be sufficient simply to transfer the login details and change the administrator. When the server changes, however, a full technical migration is required.
The safest procedure is as follows:
- Set up the new hosting and check that it supports the version of PHP, the database and the resources required by the website.
- Create a copy of the entire installation and import it into the new environment. You can use a migration plugin, or do it manually using FTP, phpMyAdmin and server management tools.
- Update the database credentials in the file
wp-config.php. If the domain changes as well, update the website addresses and replace the old URLs in the database using a suitable tool, such aswp search-replace, whilst avoiding manual changes to the serialised data. - Test the website using a temporary address or a staging environment. Check logins, pages, images, menus, forms, plugins and restricted functions.
- Only update the DNS and nameservers after testing. Install or verify the SSL certificate, clear the cache and regenerate the permalinks.
If the domain changes as well, the Guide to changing your WordPress domain correctly distinguishes between moving a website and changing its web address. For a more detailed step-by-step guide, you can also refer to this A guide to migrating a WordPress site.
The SEO aspect requires attention. Keep URLs the same wherever possible. If any URLs change, draw up a mapping of old and new pages and set up the relevant 301 redirects. Avoid redirecting all old URLs to the homepage.
To avoid losing traffic and contacts, be sure to follow the SEO migration guide for WordPress. A migration does not simply transfer files and databases. It must preserve the structure, content, tracking information, internal links and conversion paths.
Transferring access rights, roles and administrative tools
The handover is only complete when the new owner is able to carry out their duties without relying on the former administrator.
Create a personal WordPress account for the new manager and assign the appropriate role. The Administrator role allows you to manage settings, users, themes and plugins. Do not use this role for every contributor: those who write content can be assigned the Editor role, whilst those who work on pages can be given more limited permissions.
Transfer or add the new account holder to the linked platforms as well. Check Google Analytics 4, Search Console, Tag Manager, Google Ads, Meta Business, cookie consent tools and email marketing services. Make sure they are not linked to the freelancer’s or agency’s private email account.
Premium licences may be subject to different restrictions and conditions. Elementor Pro, SEO plugins, backup tools and commercial themes must be linked to the new account where the contract so stipulates. Do not assume that a personal licence can be transferred.
Once you have received written confirmation of the handover, remove any access details that are no longer required. First, check that the new owner has verified all services. Deleting the sole technical account straight away may block the website and make it difficult to regain access.
Final checks following the transfer
Once the website is live on the new platform, don’t just stop at the homepage. A website may appear to be working correctly but still contain errors in its forms, tracking or indexing.
Check the main pages on both desktop and smartphone. Test the menus, site search, links, buttons, contact forms, telephone number, automated emails and quote requests. If you use WooCommerce, complete a test order and check the shopping basket, payment, emails and order management.
From an SEO perspective, check the following:
- HTTPS certificate and redirects between www and non-www;
- 404 errors and 301 redirects;
- XML sitemap and robots.txt file;
- 'noindex' tags remaining from the staging environment;
- canonical, title, meta description and structured data;
- Link to Search Console and the presence of the main pages.
Also check your conversion tracking. A module that does not send the event to GA4 may make an advertising campaign appear ineffective. Check for clicks on mobile devices, form submissions, purchases and contact requests.
Over the following days, compare traffic, rankings and conversions with previous data. If the conversion rate drops, start by analysing mobile, landing pages and forms. The problem may be a technical change, not the market.
Frequently Asked Questions about transferring a WordPress site
Can I transfer just the WordPress administration?
Yes, provided the website remains on the same hosting service and the domain name does not change. You will need to create a new administrator account, transfer the associated tools and remove the previous access details once verification is complete.
Do I need to transfer the domain as well?
Only if the domain is to be transferred to another registrar or to a new account. If it remains with the same provider, you can transfer the day-to-day management without technically moving it.
Does moving mean you lose your ranking?
Not necessarily. The risk increases when URLs change, redirects are missing, the site is blocked by ‘noindex’, or sitemaps and crawling are interrupted. Backups, testing and a URL map help to minimise errors.
Is one plugin enough to migrate a website?
For simple websites, it can help with copying files and databases. It does not automatically transfer contracts, domain names, licences, advertising accounts, email accounts or management responsibilities. Manual checking is still required.
Structured data for FAQs
Conclusion: a comprehensive delivery protects your investment
Transferring ownership of a WordPress site means handing over a complete system, not just a password. The domain, hosting, accounts, data, licences, SEO and tracking must all be transferred in an orderly manner.
Prepare an inventory, create a verifiable backup, test the new environment and document every access. If the project involves e-commerce, campaigns or organic traffic, a professional migration will prevent downtime, lost requests and a drop in visibility.
