Kode Builder provides website migration services when a business site has to change host, CMS, domain or protocol. Tell us the current address and where it needs to live. We propose a practical first phase and send a written estimate before work starts. A WordPress rebuild that is not mainly a move stays on WordPress development. Care after the site is stable stays on website maintenance and support.
Who this page is for
Use this page when the job is to move an existing public website: a new host, a CMS change, a domain change, or HTTP to HTTPS. The team we run day to day is in India, in Ludhiana and Jaipur. If a US meeting is needed, a few of our team members can meet you in the United States.
Application and data-platform moves to AWS stay on AWS cloud consulting. A new marketing site with no site to preserve stays on business website packages.
What a website move covers
- Inventory and backup: a list of the pages, files and database, plus a restore point before the live cutover
- CMS: a WordPress or other marketing-site move when the destination is agreed in writing
- Domain: DNS cutover and the old domain kept long enough for redirects
- HTTPS: certificates on the destination and no mixed-content forms we can see in the agreed page set
A plugin stack or theme that cannot be moved as-is may need a repair or rebuild quote first. That quote is separate from the move.
Checks before and after cutover
These checks reduce avoidable loss. They are not a promise that positions stay the same.
- URL map — important old URLs listed against the new address, including trailing-slash differences.
- Redirects — one hop from the old URL to the final URL, not a chain through several hosts.
- Canonicals — the new pages name themselves, and the old host does not stay canonical after cutover.
- HTTPS — the public URL is https, and internal links in the agreed page set match it.
- Analytics — the existing measurement tag is on the destination, and forms still submit in a test.
- Sitemap and robots — the public sitemap lists the live URLs after the move, and robots rules do not block those URLs.
- Rollback — the previous host or backup stays available until the agreed checks pass. We do not promise zero downtime.
- After launch — we watch the agreed URLs, forms and analytics for the window named in the estimate. That watch is not a ranking guarantee.
What this page does not cover
- A guarantee of zero ranking loss, or any promise that traffic stays the same
- AWS, Hadoop or data-platform migration — those stay with cloud consulting and the existing AWS resources
- Moving a product catalogue, orders or customer accounts for a shop — that is e-commerce work, quoted separately from a brochure-site move
- Monthly maintenance after the move is stable
- A public price table
How a first phase starts
- Tell us the goal — host, CMS, domain, HTTPS, or a combination.
- Written estimate — URL scope, exclusions and a cutover window before work starts.
- Rehearsal — the destination is checked before DNS points at it.
- Cutover — redirects, canonicals, forms and analytics are checked against the agreed list.
US work is quoted in USD after discovery. India package fees, when a new site is the better fit, stay on the packages page.
Request a written estimate
Tell us the current URL and where the site needs to go. We will propose a practical first phase and send a written estimate before work starts.
Frequently asked questions
No. We check redirects, canonicals, HTTPS and analytics so avoidable mistakes are less likely. Search results can still change. We do not promise zero ranking loss.
No. This page is for a public website: host, CMS, domain or HTTPS. Moving an application estate to AWS stays on the AWS cloud consulting page.
No. Tell us the current site and the destination. We propose a practical first phase and send a written estimate before work starts. US work is quoted in USD after discovery.
Yes, when the project needs it. A few of our team members can meet you in the United States. The team we run day to day is in India, in Ludhiana and Jaipur.