A website migration is a move of content, design, email, and search equity from one place to another. The design might stay, or you might rebuild a layout you have the right to use. The mistake is to treat the move as a file copy and hope Google understands.
Decide what must survive
List the URLs that already receive visitors, the pages other sites link to, and the pages that rank. Those addresses need a new home or a redirect. A blog of two hundred posts is not “something we will add later” if those posts are the reason the domain has any authority.
Write down email too. A beautiful new site with a dead inbox is a failed launch. DNS for the website and DNS for mail are related and they are not the same record.
Build beside the live site
The new site should be finished on a staging address. Forms, checkout, and the editor are tested there. The current site stays in front of customers until the staging site is actually done. Big-bang rebuilds on the live domain are how a business spends a weekend offline.
If the project includes a cloned design, we confirm you own it or you are allowed to reproduce it. A reference you admire is not automatically a design we will copy.
Launch day is a checklist
Backup. Point the domain only when staging is approved. Force https. Redirect every old URL that matters, one to one where you can. Submit the new sitemap in Search Console. Check analytics. Send one real form and, if you sell, one real test order.
Then watch for a few days. Broken redirects show up in the crawl, not in the celebration.
Who should do this
If you are moving onto Hostinger, changing from a website builder to WordPress, or leaving a shop platform for Shopify, Uplaps can take the whole milestone. No advance. The scope names the URLs, the email, and the design before we touch the live domain.
If the site is already down, start with maintenance. Stabilise first. Migrate second.