Small Business Website Hosting Is Only Part of What You Need
Compare small business website hosting by checking the code, live site and domain. See a real client setup and learn what to confirm before you move.
By Samer Shaker
Your new web designer needs to change your hours, but you only have a hosting bill. Small business website hosting gives your site a place to run. Before you choose or move a host, find out where the site files live and who controls your web address.
A real client setup shows why these are separate jobs. Knowing the parts helps you judge a quote and plan a move without leaving your new team short of access.
Key Takeaways
- Before buying hosting, list where your site files, live site and domain are held, so a new team knows what to move.
- A code folder does not prove you control the site. Confirm that you can grant access and recover each key account.
- Keep your old host until the new site works. Test key pages and forms before you end the old plan.
- Have the quote name who fixes faults and makes page edits. Do not treat a hosting fee as a promise of both.
Site files, hosting and the domain do different jobs
The code holds the site's files, the host runs the site, and the domain is its web address. A handover needs to cover all three.
My client work includes All Auto Repair & Auto Glass, Everglade Heating and Air, and Hair Palette Beauty Salon. The record below describes their setup, not a test of how fast their sites load.
From our work: In my client work, the setup is recorded as follows. Each of those three client sites has its own GitHub repository with its full change history (180, 120 and 20 commits), its own Vercel deployment and its own custom domain registered through Cloudflare (WHOIS checked 2026-10-07). Those are the three things a handover has to cover: the code, the hosting and the domain.
A repository is a folder that tracks changes to code. A commit is a saved change. A deployment is a version of the site put on a host. The tools in this example have these separate roles:
| Part | Tool in this setup | What to settle before a handover |
|---|---|---|
| Site code | GitHub | Who can grant access or transfer the files? |
| Live hosting | Vercel | Who can run the site and manage the bill? |
| Domain | Cloudflare | Who can renew the name and recover the account? |
This setup is an example, not a shopping list.
When choosing a quote, first confirm the plan can run your site. Use your account list to name who grants access and helps if a login is lost. If you need page edits and form fixes, choose a quote that covers those jobs. Do not assume a hosting fee includes page edits and form fixes; check the support scope.
Separate site files do not prove owner access
Before relying on a future move, check whether the business owner has access to the code folder and hosting project.
The record from our work proves that those parts exist.
It does not prove that each client can reset each login. It also does not prove contract rights or a tested handover.
For your site, make a short account list with your current team. Note the service name, who runs it, who pays and how you get back in. Keep passwords out of that list. Use each tool's invite process to give a new team access.
Then settle rights in writing. Before reusing paid tools or designs, ask your next team to check the applicable licenses and contract terms. Your next team needs both a clear scope and the files it can use.
You do not need to learn code for this. You need a clear answer to a business question: if your current contact leaves, who can keep the site running?
Moving the code does not move the whole site
Plan the code transfer and the hosting transfer separately, and confirm which steps your setup needs. Give each task an owner, and include any tools that send leads or take bookings.
GitHub's transfer guide says the person moving a repository needs administrator access. This lets that person manage it, not just view files.
Vercel's project transfer guide, updated in 2026, lists a processing time of 10 seconds to 10 minutes.
That is not a promise about how long your whole move takes. It is not a measure of client downtime.
Vercel lists builds, settings and the code link among the parts that move. Some settings have exceptions. These include certain environment variables, which are saved values the site needs to run. Have the next developer review those before the move.
Think about the full path of a lead. A visitor fills in a form, and the message should reach your inbox. Moving the page is not enough if that last step fails. Include a marked test lead in your handover plan, with no real customer data.
You can change hosts and keep your web address
A host move does not have to change your web address. The domain, its routing settings and the host do different jobs.
The registrar is the firm where you register your domain. DNS records point the name to the right services. Ask your developer to check email-related DNS settings alongside the website settings.
Cloudflare's Registrar guide says its registered domains must use Cloudflare DNS. That rule sets where you manage the DNS records. Confirm where your website will be hosted separately from the Cloudflare DNS requirement.
For a move with the same page addresses, Google advises you to test the new host before changing DNS. Give your developer the full DNS record list so the website change does not leave email out of the plan.
Moving the domain to a new registrar is another task. Do not add it to the host move unless you need it. Have the team review transfer rules first, rather than canceling the old service and hoping the name follows.
Test the new site before ending the old plan
Keep the old host until the new site serves pages correctly. Google's same-address move guide puts testing before the switch and monitoring before shutting down old hosting.
Use this sequence when planning small business website hosting changes:
- Have the new team set up a test copy. Open the main pages, photos and forms on it. Test bookings in a safe mode if your site has them.
- Have the developer remove test settings that block search engines before the move starts. A private test site and a public live site need different settings.
- Have the person who manages DNS point the site to the new host. Record what changed and keep a plan to undo the change.
- Monitor the new and old hosts. Confirm that visitors and Google can get the pages from the new host before ending the old plan.
Google's hosting move guidance also warns that its crawl rate can drop for a time. A plan to monitor the move is more useful than a promise of no search impact.
Frequently Asked Questions
What should a small business hosting quote include?
A useful quote names the hosting service, renewal cost and support scope. It should say who handles faults, backups and page edits. Have the team list any move or setup work apart from the ongoing fee, so you can compare the full job.
Does paying for hosting mean I own my website?
Check the contract for code and design rights rather than relying on the hosting bill. Confirm domain-account access separately from the hosting payment. Get the rights in writing and confirm how you can gain access to the files and key accounts.
Can I keep my domain when I change hosts?
Yes, a host change can keep the same domain and page addresses. DNS records point the name to the new host. Confirm who can edit those records, preserve email settings and test the new site before making the switch.
Does a GitHub transfer move my live website too?
Treat the code and hosting project as separate items in the transfer plan, and confirm the steps for each. Your team must handle the live site, its settings and linked services too. Include forms, booking tools and account access in the move plan, not just the code files.
When should I cancel my old hosting?
Cancel after the new host serves the site correctly and the move has been checked. Google's guidance says to monitor both hosts before retiring the old one. Leave room in the plan for tests and fixes rather than tying cancellation to the first file transfer.
Bring the whole site to your next hosting call
Before choosing small business website hosting, bring your site address and account list to the call. Add the jobs you want off your desk, such as page edits or fixing forms.
Have the quote cover today's work and a future handover. You should know who can change the code, run the site and renew the domain. If you want help with the site and its content, send that list through our service page.