Website Hosts UK vs TSOhost

Start with the tsoHost-to-123 Reg transition

tsoHost is no longer operating as a separate provider in the way many long-standing customers remember. Its current website says tsoHost is now part of 123 Reg, and that customer products are being moved into the 123 Reg environment. That does not mean a customer must immediately leave, rebuild a website or transfer a domain. It means the comparison should start with the service you have today and the account relationship you want tomorrow.

For some customers, the move to 123 Reg may be straightforward: their website works, their domain and email remain where expected, and they are comfortable managing the service through the new control panel. For others, the change can be a useful moment to simplify an old setup, review renewal decisions, separate an online shop from a legacy hosting bundle or move a business website to a host that feels more aligned with what it actually needs.

Treat the 123 Reg transition as an account-review exercise, not an instruction to rebuild everything. Keep working services in place while you decide what needs attention. A domain can remain where it is, email can stay unchanged, and a website can be moved separately once its replacement has been tested.

Three sensible next steps

Most small businesses belong in Path A or Path B. A standard brochure website does not usually need a new server, a new domain registrar and a new email platform at the same time. The more components that change together, the harder it becomes to identify the cause when something goes wrong. Move only what is necessary, then make the next decision from a stable position.

Map the services before choosing a plan

“My tsoHost account” can mean far more than a web-hosting plan. A company may have a .co.uk domain, DNS records, one or more websites, mailboxes, a Microsoft 365 subscription, an SSL certificate, a website builder, a database, a virtual server or backups under the same login. Those items do not necessarily move together, and some may not move in the same way at all.

Match the new service to the job

Once you know what needs to move, the service choice becomes much easier. Website Hosts UK is not designed to make every old tsoHost or 123 Reg product look identical. It is designed to give a sensible route for the workload: a normal website, WordPress site, online store, business email setup or self-managed Linux project.

For a normal website, a more complicated product is not a better product. A VPS gives root access, but it also makes the customer or their technical partner responsible for operating-system updates, backups, firewall configuration and the software installed on it. A good comparison makes that responsibility obvious before the order is placed.

Keep domains and email as separate decisions

The tsoHost-to-123 Reg change makes it especially important to separate account access from service location. Your domain can stay at the existing registrar, your mailboxes can stay with their current provider, and only the website can move. Treat each as its own decision rather than assuming one control panel means everything must travel together.

Changing nameservers is the point where a straightforward website migration can accidentally become an email outage. Before a DNS change, export or write down the existing records. Check MX records for incoming mail, SPF for sending authority, DKIM for message signing and DMARC for policy. Make sure any third-party services such as booking tools, transactional mail platforms or verification records are represented in the destination DNS zone.

A low-risk move checklist

1. 1
   Read the account notices.
   Confirm whether the product is already managed through 123 Reg, what login is used and whether a platform or renewal change is pending.
2. 2
   Inventory the active services.
   Separate the domain, website, databases, email, SSL, backups and any server or application dependency.
3. 3
   Create the destination without touching DNS.
   Build the new Website Hosts UK service, import the site or application, and make configuration changes privately.
4. 4
   Test what customers actually use.
   Test contact forms, login, password resets, bookings, payment flow, outgoing mail and key page journeys.
5. 5
   Change the smallest possible DNS set.
   Update the web records needed for the new site, while protecting mail and other existing records.
6. 6
   Keep the old service until the result is proven.
   Review logs, take a final backup and only then cancel products you genuinely no longer need.

The useful outcome is a setup the business can explain: who owns the account, where the domain and email are managed, who can make DNS changes and who is responsible for backups. That matters more than changing every service at the same time.

Use the transition to tidy up account ownership

A provider transition can expose details that have been overlooked for years. The person who originally bought the tsoHost plan may have left the business. A developer may still be the only contact with DNS access. Renewal notices may be going to an old email address. A domain could be registered in a personal name while the business depends on it. None of these issues are reasons to panic, but they are good reasons to document the setup before making a hosting move.

Start by recording the account owner, billing contact, recovery email, domain registrant, DNS manager, website administrator and email administrator. For an ecommerce or membership site, also record the payment account, transactional email provider, analytics owner and any third-party API keys. This creates a simple ownership map that survives a staff change, provider move or forgotten password.

Then look at renewal dates separately. A domain renewal, a website-hosting renewal and a Microsoft 365 renewal do not need to be treated as one deadline. Separating the calendar prevents a rushed decision where a business transfers a domain, changes hosting and interrupts email merely because one product was close to renewal.