Domain and Hosting Guide: Ownership, Renewals and Migration

Understand domain ownership, recurring costs, email, backups, migration checks, and handover before choosing or moving your business website.
Performance charts and analytics on a laptop screen.

Your domain, hosting, and email may appear on one invoice, but they do different jobs. Understanding what each service controls makes it easier to compare proposals, budget for renewals, and plan a website move without losing track of essential business access.

This guide explains the decisions to make before choosing a setup or migrating an existing WordPress website. It does not assume that the cheapest introductory offer is the right long-term fit.

Domain, hosting, and email: what is the difference?

The domain is the address people use to find your business online. Registration gives the registrant rights to use it for the registered period; keeping it requires renewal. Hosting provides the environment where the website runs. Email hosting handles business mailboxes and may be a separate service.

These services can be supplied together or by different providers. Before choosing, record who manages each account, how they connect, and who can make changes. A website move does not automatically require changing the domain registrar or moving email.

Keep the business in control of registration

Agree who is listed as the domain registrant, who can access the registrar account, and who receives renewal notices. Use a reliable contact address that the business controls and keep it current. If a supplier registers the name on your behalf, document how access and control will be provided.

ICANN advises registrants to renew before expiration and keep contact details up to date. Review its domain renewal guidance and your registrar’s actual terms. Do not assume a website maintenance agreement automatically covers domain renewal.

Compare the recurring cost

Ask for the initial price, renewal price, billing period, and any separate charges. A useful comparison includes the domain, hosting, email, paid software licences, backup storage, migration support, and ongoing maintenance where relevant.

  • What renews automatically, and through which account?
  • Are taxes, mailbox fees, and paid licences included?
  • What is the renewal rate after an introductory period?
  • What limits apply to storage, traffic, resources, or mailboxes?
  • What happens when the site exceeds a limit?
  • What assistance is included if the business changes provider?

Get the answers in the proposal. A low first payment is not a complete picture of operating cost.

Choose hosting around the website

A small informational site, an ecommerce store, and a membership platform can have different requirements. Describe the features, expected usage, integrations, and update process before selecting a plan. Ask whether the environment supports the current WordPress hosting requirements.

Also compare support availability, backup and restore arrangements, staging where needed, and how the provider handles an incident. Treat a published uptime target as a contract detail to understand, rather than a promise that the website will never be unavailable.

Check backups and restoration separately

A backup is useful only if the right data is included and the recovery process is understood. WordPress explains that a typical full restoration needs both the database and site files; see its backup documentation.

Ask how often backups run, how long they are kept, where they are stored, who can restore them, and whether restoration has been tested. Clarify whether email and other external services are covered. For an active store or booking site, the acceptable amount of lost data matters as much as the backup frequency.

What exactly are you moving?

Ask the proposal to name each change separately. A hosting move, a domain transfer, a DNS change, and an email migration are different jobs, even when one provider sells them together.

  • Website hosting: moving the WordPress files and database to a new hosting environment. Your domain can remain with its current registrar, and email can remain with its current provider, if the setup and service terms support that arrangement.
  • Domain registration: transferring the registration to another registrar. This does not by itself copy website files or mailbox contents. Check the applicable transfer requirements with the registrars; ICANN provides domain transfer FAQs.
  • DNS management: changing where the domain’s DNS records are managed, often through a nameserver change. Review the complete record list before switching, including website destinations, email routing, and verification records for connected services. Record who will maintain it afterwards.
  • Email hosting: moving mailboxes to another email provider. Confirm which addresses, aliases, historical messages, and other data are included. Follow the receiving provider’s settings and agree sending and receiving checks separately from the website checks.

DNS connects these services but does not contain your website files or mailbox history. Cloudflare’s email DNS documentation explains why mail records depend on the email provider. If email is staying in place, the migration scope should explicitly preserve the records and services it needs.

Before cancelling the old package, ask whether it also supplies email, DNS, backups, or licences. Keep any service still needed until the agreed replacement and checks are complete. A successful website load alone is not a complete migration sign-off.

Prepare a migration plan before changing DNS

Start by recording the existing website, hosting, domain, email, important URLs, and connected services. Agree the migration window, the responsibilities of each provider, and a rollback plan. Back up the files and database before work begins.

Validate the moved site before changing where visitors are directed. Check important pages, images, navigation, forms, secure connections, and any purchase or booking journey. Avoid changing website and email settings together unless that is part of the agreed scope.

After the change, review the public site again and check the services that depend on domain settings. If the domain or page URLs also change, plan redirects and search-related checks. The official WordPress migration guidance explains why the move should account for site files and the database.

Know where support responsibility ends

Hosting support and website maintenance are related, but they may cover different problems. Ask who investigates a server outage, who fixes a plugin conflict, who checks form delivery, and who updates website content. Define the route for urgent requests and the scope of ongoing support. Our guide to comparing WordPress maintenance services gives you questions to separate hosting coverage from website care and separately priced repairs.

Keep a handover record with account roles, renewal dates, backup locations, useful support contacts, and the agreed maintenance tasks. It should remain useful if a staff member or supplier changes.

Questions to send before accepting a proposal

  • Which accounts and services will the business control?
  • What are the initial and renewal costs for each item?
  • Will existing email remain where it is?
  • Which site functions and URLs must be preserved?
  • How will backups, validation, and rollback be handled?
  • Who approves the move and checks the public result?
  • What is included after launch, and what is additional work?

Discuss the setup before buying a plan

Explore Zevon’s domain and hosting service to discuss a setup or migration scope. If the website itself also needs a rebuild, review WordPress development and our website planning checklist.

Send a project enquiry with your existing website, the reason for the proposed change, and which services should stay with their current providers. If known, include the hosting provider, renewal deadline, required features, and preferred move date. We can use that outline to discuss the scope before you buy or cancel a plan. Share access requirements during the discussion; do not put passwords or transfer authorisation codes into an enquiry form.

In this article

Make the next move clearer.

Tell us your goal, current channels, and the problem you want to solve.

Turn insight into a practical next step.

Explore the services and working approach behind these guides.

Choose your channel

Explore Meta Ads, Google Ads, SEO, and the web foundations that support them.

Understand the process

See how Diagnose → Build → Improve turns priorities into an accountable plan.

Talk through your goal

Start with the business challenge, not a package or a promise of guaranteed results.
Scroll to Top