What does a website migration freelancer do?
A website migration freelancer changes where or how your site lives without breaking what already works. “Where” means hosting or domain; “how” means platform, framework or URL structure. The visible part is the new site. The part that decides success is invisible: redirects, DNS records, email routing, form endpoints, analytics and the signals Google has built up about your pages over years.
Most migration damage is not dramatic. A site stays online but loses a third of its search traffic because old URLs return 404 errors. Emails stop arriving because MX records were not copied. A contact form sends to an address on the old server. Nobody notices for weeks. A good website migration freelancer is paid to notice all of this before it happens.
At BtechWaleTech, another of us leads the SEO and hosting side, including AWS setups and Search Console. One of us handles rebuilds and data exports, and the third of us plans the switch window and runs the checklist so each step is signed off.
- Inventory: every URL, DNS record, integration and account
- Backup: full files and database, with a tested restore
- Map: each old URL to its new address
- Build or copy: the new home for the site, on staging
- Switch: DNS change with redirects live at the same moment
- Monitor: Search Console, 404s and traffic for several weeks
Types of website migration and how risky each one is
Not every move carries the same risk. The more that changes at once, the more work the redirect map and checks need, and the longer Google takes to settle.
Hosting only (same domain, same URLs)
Lowest risk. Files and database move, DNS points to the new server. Search engines see the same pages at the same addresses, often with no measurable change.
HTTP to HTTPS
Low risk if every HTTP URL redirects to its HTTPS twin, internal links are updated and mixed content is removed.
Domain change
Medium risk. One-to-one redirects plus Google’s Change of Address tool in Search Console. Expect some fluctuation for a few weeks.
Platform change
Medium to high risk. URLs often change shape, templates change, and content can be lost in export. Needs a full map and page-by-page comparison.
Structure change or site merge
Highest risk. Pages are combined, renamed or removed. Every decision about which old page maps to which new page affects rankings.
Our advice is to change one thing at a time where possible. Moving host, then platform a month later, makes any traffic change easier to diagnose than doing both on one night.
When should you hire a website migration freelancer?
Hire a website migration freelancer when anything other than the server is changing, or when the site earns meaningful enquiries or sales from search. The cost of a careful plan is small next to months of lost leads.
Common triggers we see: a site builder subscription that keeps rising while the site stays slow; an old PHP site nobody can safely edit; a WordPress install with dozens of plugins and repeated malware; a rebrand to a new domain; hosting that was bought by a former developer in their own name; or a business that wants its site on a cloud account it controls. Each is a good reason to move, and each needs a slightly different plan.
You may not need anyone if your site is a handful of pages with no search traffic worth protecting and you are simply changing host. In that case, a host’s free transfer and a quick check of email and forms may be enough. If you are unsure, send us the domain and we will tell you honestly which category it falls into.
Step one for any website migration freelancer: the URL and account inventory
Every migration starts with a list of what exists. Memory is not enough; sites collect pages, PDFs, image URLs and landing pages for old campaigns that nobody remembers but that still receive links and visits.
We build the URL list from three sources and merge them: a full crawl of the live site, the pages report in Google Search Console, and landing pages from analytics over the past year. Pages that appear in Search Console but not in the crawl are often orphans with backlinks, which are exactly the ones that disappear silently in a careless move.
The account inventory matters just as much: registrar, DNS host, hosting, email provider, SSL, CDN, form tools, payment and booking integrations, analytics tags, and who holds each login. We record the current DNS zone in full, including MX, TXT, CNAME and verification records, before touching anything.
- Crawl of the live site, including PDFs and images
- Search Console pages and top queries export
- Analytics landing pages for the last twelve months
- Backlink targets from Search Console links report
- Complete DNS zone export
- List of integrations, webhooks and form endpoints
How do you make a 301 redirect map for a website migration?
Put every old URL in one column and its closest new equivalent in the next, then implement each row as a single 301 redirect. “Closest” means the page that answers the same question, not the home page. Redirecting everything to the home page is treated by Google much like a missing page and throws away the value those URLs had.
Rules keep the map clean. Redirect in one hop, so there are no chains of A to B to C. Keep query strings only where they matter. Retire truly obsolete pages with a 410 or a 404 rather than forcing an unrelated redirect. Keep images and PDFs that earn traffic at the same path, or redirect them too. And keep the redirects in place long term; Google’s guidance is at least a year, and we simply leave them.
For platform moves where URL patterns change systematically, such as from dated blog URLs to plain slugs, we use pattern rules backed by a tested sample, then spot-check the exceptions by hand. The final map is a spreadsheet you keep, useful for any future move.
Backups and staging: the website migration freelancer’s safety net
Before anything is moved, take a complete backup of files and database, store it somewhere other than the current server, and prove it can be restored. An untested backup is a hope, not a plan. For WordPress and similar systems we also export content in a portable format, so it survives even if the database cannot be restored cleanly.
The new site is built or copied onto staging first, blocked from indexing. We then compare old and new page by page for the URLs that matter most: title, meta description, H1, main content, internal links, canonical tags, structured data and images. Differences are either fixed or deliberately accepted and written down.
Forms, checkouts, logins and any integration that sends data somewhere else are tested on staging with real submissions. That is where hidden dependencies surface, such as a form script that posts to a file on the old server or a payment callback URL registered to the old domain.
DNS, email and SSL: the parts of a migration people forget
Email breaks more often than websites during migrations. If your email is hosted with a separate provider, its MX records, plus the SPF, DKIM and DMARC records that stop your mail landing in spam, must exist at the new DNS host before nameservers change. We copy the full zone, then compare it line by line after the switch.
A day or two before the move, we lower the TTL on the records that will change, so the switch spreads quickly. The old server stays live and unchanged until traffic has clearly moved, which is how visitors avoid downtime while DNS updates reach every network.
SSL certificates are issued on the new host before or at the moment of switching, and HTTPS redirects are confirmed. If you are transferring the domain to a new registrar too, remember that most domains cannot be moved within 60 days of registration or a previous transfer, and the transfer needs an authorisation code from the current registrar. We schedule that separately from the site move.
Switch day: the order a website migration freelancer follows
The switch is timed for your quietest period, often late evening IST or a weekend morning. Content edits on the old site are frozen a day earlier so nothing is lost between the final export and the switch.
- Final backup and content delta export from the old site
- Redirect rules deployed on the new site and tested with a URL sample
- Staging noindex removed; robots file checked
- DNS records or nameservers updated
- SSL confirmed on all hostnames, with and without www
- Forms, checkout and email tested on the live domain
- New XML sitemap submitted in Search Console
- For a domain change: Change of Address submitted, both properties verified
We stay on WhatsApp throughout the window, and all three of us know the plan, so a question at 10 pm gets an answer. If a critical check fails, the plan includes a rollback: point DNS back to the untouched old server and try again once fixed.
After the switch: monitoring what Google sees
The weeks after a migration matter as much as the night itself, and a website migration freelancer who disappears after switch night has done only half the job. Google recrawls gradually, so problems appear in Search Console over days, not minutes.
We run a crawl of the old URL list against the live site to confirm every redirect lands on a 200 page, check Search Console for new 404s, redirect errors and pages “crawled, currently not indexed”, and compare impressions and clicks for the top pages week on week. Some movement is normal for domain and platform changes; a steady fall on specific pages usually points to a missing redirect or lost content, and those get fixed first.
Keep the old hosting account alive for a few weeks if you can, and do not let the old domain expire after a domain change. Its redirects are what pass your history to the new site. After a rebuild, our two months of free maintenance cover this monitoring period.
A platform migration is a rebuild with a strict rule: nothing that earns traffic is lost. Content, metadata, images, internal links and structured data move across; design and code are replaced.
From Wix or other site builders
Builders do not export working site code, so pages are recreated and content copied carefully. The domain can usually be moved out and pointed at your new hosting.
From WordPress
Posts, pages, media and metadata export well. Plugin-generated pages and shortcodes need manual attention so nothing renders as raw code.
From an old custom PHP site
Often the database is the real asset. We extract content, rebuild templates and redirect any odd URL formats the old code produced.
Between store platforms
Products, variants, customers and orders move; passwords do not. Product and category redirects protect years of search history.
If you are leaving a builder, our Wix to custom website page covers that route in detail. For store moves, see freelance Shopify developer.
How much does a website migration freelancer cost in India?
It depends on what changes. A hosting-only move for a small site is a modest line item that we quote after seeing it, because the amount of work depends on databases, email setup and integrations. A domain change adds mapping and Search Console work. A platform change is priced like a new build: a static site from ₹10,000, an SEO website from ₹20,000, an online store from ₹50,000 and a custom web app from ₹60,000.
Across the market, migration quotes vary widely because the scope varies. One quote may cover copying files; another includes the inventory, redirect map, email records and weeks of monitoring. Ask each website migration freelancer to list exactly which of those steps are included before comparing numbers.
The cheapest option in the long run is usually the careful one. Recovering lost rankings after a migration without redirects can take months of paid SEO work, while mapping them properly takes a day or two up front.
For ongoing technical work after the move, see technical SEO freelancer.
How long does a website migration take?
A simple hosting move can be done within a few days including preparation, with the switch itself taking an evening. A domain change usually takes a week or so of preparation. A platform rebuild follows the build timeline: one to two weeks for a static site, three to five for a large SEO site, four to eight for a store.
Add a monitoring period on top of every one of these. Search Console data takes time to reflect the change, and we watch it for several weeks before calling the migration complete. Domain transfers between registrars add their own waiting period, which we schedule so it never blocks the site move.
Red flags when hiring a website migration freelancer
A few answers tell you quickly whether someone understands migrations or just copies files.
- No mention of redirects until you ask
- Plans to redirect all old pages to the home page
- No backup plan, or a backup kept only on the server being replaced
- No questions about your email provider or DNS records
- Wants the new hosting or domain registered in their own name
- Promises zero ranking change or guaranteed rankings
- No monitoring after the switch
A careful website migration freelancer will talk about crawls, redirect maps and Search Console before talking about the new design. If you are hiring for broader development work, our guide to hiring a web developer covers contracts and payments.
Worked example: an engineering supplier leaving an old PHP site
This is a hypothetical scenario to show the method. Imagine a pumps and valves supplier with a twelve-year-old custom PHP site: about 300 URLs, including product pages with query-string addresses, a few dozen PDF datasheets that other sites link to, and email hosted with a separate provider. Search brings most of its dealer enquiries.
Week one builds the inventory from a crawl, Search Console and analytics, which surfaces forty product URLs the owner had forgotten. The redirect map converts query-string product URLs to clean slugs, keeps every PDF at its existing path, and retires a handful of discontinued products to their category pages where a close match exists. The DNS zone is exported, including the email records.
The new static site is built on staging from the database content, then compared page by page. On switch night the TTL is already low, redirects go live with DNS, and test enquiries confirm forms reach the sales inbox. For the following weeks, Search Console and a recrawl of the old URL list are checked weekly. A rebuild like this would start from the static plan at ₹10,000, with mapping listed separately.
Website migration freelancer services across India
Migrations are remote work by nature: DNS, hosting panels, repositories and Search Console are all online, and switch windows are coordinated on WhatsApp. We work with businesses in Nashik, Aurangabad, Solapur, Gwalior, Jabalpur, Bhopal, Mangaluru, Hubballi-Dharwad, Jamshedpur and Faridabad, and the method is the same in every city.
Many of the sites we move were built years ago by a local developer who has since moved on, often with hosting or the domain held in that person’s name. Recovering those accounts is frequently the first job, and we guide you through the registrar’s ownership process where needed.
Sites with overseas audiences get the same plan, with switch windows timed for their quiet hours. See our country pages for how billing and calls work abroad.