Website migration: a guide for business owners
Table of Contents
A website migration is any change to a site’s platform, domain, hosting, or URL structure that alters how search engines find and index its pages. Handled badly, it can cost a business rankings built over years. ProfileTree plans every migration around one document, a map that sends each old page address to its replacement on the new site.
For business owners in Northern Ireland, the Republic of Ireland and Great Britain, a migration rarely starts as a technical project. It usually follows a business decision, such as a new brand name or a rebuild after years of patching an old site. This guide explains what counts as a migration and the checks that protect your search traffic, so you can judge how much of the work to do in-house and when to bring in website development support.
What a website migration is and what it is not
A website migration is a change to the technology, structure, location, or address of a site that affects how search engines crawl and index it. Crawling is search engine software visiting your pages, and indexing is the search engine storing them so they can appear in results. Publishing a new page or rewriting copy does not qualify, because a migration moves the foundations underneath pages that search engines already know.
The common types of migration
Migrations usually fall into one of six types, and a single project often combines two or more of them:
- Moving to a new server or hosting company while keeping the same domain and the same URLs.
- Moving from HTTP to HTTPS, which encrypts the connection between a visitor’s browser and the site.
- Changing the domain name, for example after a rebrand or a merger.
- Switching content management system (CMS, the software you use to edit the site), such as moving from a legacy platform or a website builder to WordPress.
- Restructuring URLs, such as renaming folders or removing dates from blog addresses.
- A redesign that removes, merges, or renames pages.
Combining types raises the risk, because two changes at once make the cause of any problem harder to find. A new domain combined with a redesign is the hardest case, since every URL changes and much of the content changes with it.
Changes that do not count as a migration
Editing homepage copy, adding a new service page, updating plugins (add-on software that extends a WordPress site) and changing the colour scheme are routine updates, provided no URL changes. The distinction matters because the casual approach that suits a routine update causes real damage when someone applies it to a platform move. If a change alters any URL that search engines have already indexed, treat it as a migration and plan it as one.
Why a badly planned migration costs rankings and enquiries

The main risk is lost search visibility, and with it the enquiries that visibility brings in. A site that has ranked for several years holds that value in its URLs, its internal links, its page titles, and the links other websites point at it. A migration can break all of these at once if nobody maps the old site to the new one.
Google’s guidance on moving a site describes a move as the job of passing signals from old URLs to new ones, and it says that ranking changes during a move are normal and settle over time. The trouble starts when pages disappear without a redirect. These are the problems that most often follow a poorly planned migration:
- Error pages (404s), where an old address shows a “page not found” message instead of forwarding the visitor to the new page.
- Old sitemaps, the files that list a site’s URLs for search engines, that send crawlers to addresses that no longer exist.
- Duplicate content, when the old and new versions of a page are both live and indexed for a period.
- Mixed content warnings after a move to HTTPS, when images or scripts still load over the insecure connection.
- A noindex instruction, which tells search engines not to list a page, left in place from the test site.
For an SME that relies on its website for leads, each of these has a direct cost. A service page that now returns an error produces no enquiries, and nothing on the new site shows that it is missing unless someone checks.
When a business needs to migrate its website

The trigger for a migration is usually a practical business problem, and the problem decides which type of migration you need. Naming it at the start keeps the scope honest, because a hosting move that quietly gains a redesign becomes a much riskier project.
The platform no longer does the job
Old bespoke builds and early website builders often reach the point where maintaining them costs more than moving. If you pay a developer for routine edits, or the platform will not connect to the booking or customer relationship management (CRM) software your business now uses, the move is probably overdue. A current platform such as WordPress lets your team edit its own content and add integrations without bespoke development each time.
Hosting is holding the site back
Shared hosting plans that suited a new site often struggle once traffic grows, and slow page loads and repeated outages are the usual signs. A hosting move keeps the domain and the URLs the same, which makes it the lowest-risk type of migration. Moving to managed hosting, where the provider looks after updates and backups for you, also takes routine site care off your desk.
A rebrand or a new domain
A domain change is one of the riskiest migrations, because it asks search engines to transfer everything the old address has earned to a new one. Every old URL needs a permanent redirect to its equivalent on the new domain, and every internal link needs updating. Businesses that change name after a merger often underestimate how long this takes, and our guide to redirecting an old domain covers the setup in more detail.
A redesign that changes the URLs
A redesign counts as a migration as soon as it removes pages, merges them, or changes their addresses, even when the domain stays the same. This is where many SMEs lose rankings, because the new site is planned around how it looks and nobody records what the old site ranked for. The work of protecting rankings during a redesign starts before the designer opens a file.
Three ways to migrate a website

The right method depends on the size of the site and on how much risk the business can carry if something goes wrong. A like-for-like move between hosts suits the first two methods, while any change to URLs or domains needs the planning that only the third provides.
| Method | Suits | Plans redirects | Main risk |
|---|---|---|---|
| Manual migration over FTP | Developers and confident site administrators | No, redirects are set up separately | Missed files or a broken database connection |
| WordPress migration plugin | Like-for-like WordPress moves to a new host | No | File size limits and settings that do not carry across |
| Web development team | Domain changes, platform changes and redesigns | Yes, as part of the project | A team that skips the audit before it starts |
Manual migration over FTP
FTP (File Transfer Protocol) is a way of copying files directly between your computer and a server, and FileZilla is the best-known free program for it. A manual migration gives you full control over every file and setting, but it is also the most demanding method and the easiest to get wrong.
The work runs in a set order. You take a backup of the current site, including its database (where a WordPress site stores its content and settings), upload the files to the new server, import the database, and update the site’s connection details. Only after testing the site on the new server do you point the domain at it by changing the DNS records, the settings that tell the internet which server a domain uses. If you have never worked with server files and database exports, choose another method.
A WordPress migration plugin
For WordPress sites, a migration plugin copies the whole site without direct access to the server. You install the plugin on the existing site and create a backup, then install the same plugin on the new site and restore the backup there. Some free versions cap the size of the site they will move, and our article on file size limits in WordPress migration plugins explains how to deal with that.
Plugins work best for like-for-like moves, where the platform and the URLs stay the same and only the host changes. They do not plan redirects or check rankings, so on a platform change, they cover only the file transfer.
A web development team
For most SMEs, a team with migration experience is the safest route for anything beyond a straightforward hosting move, particularly when the domain or platform is changing, or the move comes with a redesign. The fee for specialist help is usually small next to the value of the pages that produce leads.
A team that handles migrations properly audits the current site before touching anything and builds the new site on a private staging copy. It maps every valuable URL to its replacement and tests the redirects before launch. After launch, it submits the updated sitemap to Google and Bing and watches the crawl and ranking data for the months that follow.
ProfileTree is a Belfast web design and digital marketing agency, founded in 2011 and based at the McSweeney Centre. Our development team carries out migrations for businesses across Northern Ireland, the Republic of Ireland and Great Britain, and each one starts with a record of what the current site ranks for.
“A website migration on a site that already ranks needs the care of an operation. Keep the URLs where you can, keep what Google already rewards, and change what is holding the site back. Most of the damage I have seen done to business websites in Belfast happened during a rebuild or a move that nobody measured, which is why ProfileTree measures every migration before and after,” says Ciaran Connolly, founder of ProfileTree.
How to protect your SEO during a website migration

Protecting search traffic is the part of the project that needs the most preparation, and it is the part a plugin cannot do for you. Google’s guidance sets out the core sequence: prepare and test the new site, map old URLs to new ones and add redirects, then submit the new sitemap and monitor the move. For a printable version of these steps, use our step-by-step migration checklist.
Record a baseline before anything moves
Before a single file moves, record which pages win organic traffic and leads, and which URLs have links from other websites (backlinks). Google Search Console and your analytics show the first, and a backlink checker shows the second. This baseline tells you what needs protecting and lets you prove after launch whether anything has been lost.
The baseline is also the moment to fix existing problems, such as broken links or duplicate pages. Fixing them now means the new site does not inherit them.
Map every old URL to its new address
A 301 redirect is a permanent instruction on the server that sends visitors and search engines from an old address to a new one and passes the old page’s signals across. Every URL with organic traffic, backlinks, or internal links pointing at it needs a 301 to its closest equivalent on the new site. Google recommends keeping redirects in place for at least a year, and avoiding chains where one redirect leads to another.
The standard working document is a spreadsheet with each old URL in one column and its new URL beside it. Sending every old page to the homepage is a tempting shortcut, but it throws away most of the value, because the homepage rarely answers the question the old page answered.
Test on a staging site and lift the noindex at launch
Never carry out a migration on the live site. A staging site is a private copy where you can check every page and redirect before visitors or search engines see it, and while it is in staging it should carry a noindex instruction or sit behind a password.
The noindex has to come off the moment the new site goes live. Leaving it in place is one of the most damaging migration mistakes, because it tells search engines to drop pages that were ranking the day before. On launch day, check the search engine visibility setting in WordPress and the equivalent setting in your SEO plugin.
Tell Google and Bing about the move
Once the new site is live, add the new XML sitemap in Google Search Console and remove the old one. If the domain has changed, use the Change of Address tool in Search Console as well. Google says that tool is not needed for a move from HTTP to HTTPS or between the www and non-www versions of the same domain.
Bing Webmaster Tools has its own site move tool, and submitting the sitemap there matters as much as it does in Google. Microsoft’s Copilot draws its web answers from Bing, so a migration that Bing has not picked up can also cost you visibility in AI answers.
Watch the data for the months after launch
Google says that most pages on a small or medium-sized site take a few weeks to move in its index, and larger sites take longer. Check Search Console every week for the first month for crawl errors and pages dropping out of the index, then compare traffic and enquiries with your baseline. Some movement in rankings is normal during this period. A steady fall in indexed pages, or a run of 404s on pages that used to rank, means a redirect or a setting needs fixing.
Data protection when your hosting moves country

If your migration moves hosting from one country to another, for example from a US server to one in the UK, check whether the move changes where personal data is stored. Under UK GDPR, sending personal information outside the UK can count as a restricted transfer, which the law allows only on specific grounds. The Information Commissioner’s Office (ICO) explains how these transfers work in its brief guide to international transfers.
Contact form submissions and customer accounts both count as personal data. Record the change and update your privacy policy to say where data is now held, and if you are unsure whether the move affects your obligations, take advice from a data protection professional.
How long a migration takes and what sets the cost
The time a migration takes depends on the type of move and how many URLs need mapping, and a redesign that restructures URLs takes the longest because the content work and the migration work run side by side. A practical way to judge the job is to place the move in one of three risk tiers:
| Risk tier | Migration types | What it needs before launch |
|---|---|---|
| Lower | Hosting move with the same domain and URLs; HTTP to HTTPS | A full backup, testing on the new server and a check for mixed content |
| Medium | Platform change that keeps the URLs | A baseline audit, a test copy of the new site, and checks on every page template |
| Higher | Domain change; URL restructure; redesign that removes or merges pages | A baseline audit, a complete 301 redirect map, staging, Change of Address for a domain move and close monitoring after launch |
Cost follows the same factors. At ProfileTree, web development work is charged by the hour, and bringing a neglected site up to date starts from £800 to £2,000 plus VAT. A domain change, platform move, or redesign is quoted on request after an audit, because the number of URLs to map decides how big the job is.
Before you commission anyone, ask how many URLs need redirect mapping and how the team will check search performance after launch. A provider who cannot answer both before work begins has not scoped the job.
Getting help with your move
If you are planning a migration, start with the baseline described above, because every later decision depends on it. ProfileTree’s development team can review your current site and recommend the right approach before any work begins. Once the new site is live, our managed hosting and maintenance service keeps it updated and monitored, so the rankings you protected during the move stay protected.
FAQs
1. How long does it take to migrate a website?
A hosting move with no URL changes is the quickest, while a domain or platform change takes several weeks once auditing, redirect mapping, staging, and monitoring are included. After launch, Google says most pages on a small or medium-sized site take a few weeks to move in its index.
2. Will a website migration affect my Google rankings?
Some movement in rankings is normal during a migration, and Google says it settles over time when the move is handled properly. Rankings that do not recover usually point to missing redirects or a noindex tag left on after launch. Checking both against your baseline is the first job if traffic falls.
3. How do I update to new page URLs after migrating a site?
Add a 301 redirect from each old URL to its new address, then update the internal links on the site so they point straight to the new URLs without passing through a redirect. Update the canonical tags, which tell search engines the preferred version of each page, and submit the updated sitemap in Search Console. Where other websites link to your old pages, ask the most important of them to update their links.
4. Can I move my website to a new developer without losing it?
Yes, as long as you own the domain and can get a full copy of the site files and database. Before you switch, ask your current developer for administrator access and a complete backup, and make sure you hold the login for the account where your domain is registered. If the new developer is rebuilding the site at the same time, the move becomes a full migration and needs a redirect map.
5. Do I need to migrate my old content?
Content that brings in traffic or has links from other websites should move to the new site and be improved there. Pages with no traffic and no backlinks can be left behind, but give each one a redirect to the closest relevant page so that visitors who arrive from an old link still land somewhere useful.
Free Twitter analytics: what still works on X