Why should your business control its hosting and data?

09.11.2026 Published by:

Control over hosting means access to the service, independent backups and the ability to change provider. How should a business prepare its domain, websites and email for a move?

A website, email service and booking system can run for years while the organisation has little visibility into its hosting. A move then raises basic questions: who controls the domain, where are the backups, and can the data be recovered? Having your own hosting should first mean control over the service and the ability to move it.

What does owning your hosting mean?

A business does not necessarily need a physical server. It needs access to its account, a clear maintenance owner and a way to obtain its complete data. Domain registration, hosting, email and technical support are separate services. The organisation should know who controls each one and how responsibility can be transferred.

Shared hosting may suit a simple website. A managed VPS offers an environment tailored to an application, with responsibilities for updates, monitoring and backups agreed in advance. Owning hardware adds responsibility for its availability and operation. Choose the model around the workload and the team that will maintain it.

Who should have access, and who is responsible?

Organise access before you need to change supplier. The business should be able to regain control of its services when the person handling them day to day is unavailable. This does not require a shared password for the whole team. Use individual accounts, limited permissions and multi-factor authentication wherever the service supports them.

  • Domain: check the registrant details, renewal date and who can access the registrar account.
  • DNS: establish who manages the website and email records and who approves changes.
  • Hosting: confirm how files, databases and configuration can be exported and how the service can be ended.
  • Email: include message and folder history. Contacts, calendars and local archives may need separate exports.
  • Backups: agree the scope, retention period, independent storage location and restore procedure.
  • Maintenance: assign responsibility for updates, monitoring, incidents and checks after changes.

What did the migration involve?

The project covered three websites, including a cinema booking service, plus the history of 21 mailboxes and a separate catch-all account. Files, databases, scheduled jobs, email configuration and traffic routing had to be coordinated.

Loading the website on the destination server was only one step. During cutover, the old server forwarded web requests to the new environment so new entries would not be written independently to two databases.

The technical scope and verified result are described in our project: migrating three websites and email history for a cultural institution.

Why should a backup be independent and tested?

We secured copies before the migration. A restore test for the three websites and their databases passed, covering 236 tables, HTTP 200 responses and media checks. A full functional restore test of all email was a separate scope and was not completed as part of that test.

For a business, the useful questions are what the backup contains, where it is held and who can restore it. A copy outside the active environment reduces dependence on one hosting account. A restore exercise provides stronger evidence than a successful backup notification alone.

Email includes years of business history

Creating replacement addresses is not the same as moving email history. Folders, dates, message flags and mail arriving during the copy all matter. We separated the unique catch-all history from links to other mailboxes to avoid copying the same collections twice. Capacity limits and differences in folder names also required attention.

The final imapsync run on 19 October 2026 completed successfully for 22 entries: 21 mailboxes and the system account. It reported more than 35,000 messages already present at the destination and no source messages missing according to the tool. Messages were not deleted from either side.

That result establishes the scope of IMAP synchronisation. External email delivery and website payments or bookings require separate functional checks. Domain transfer and DNSSEC preparation are also separate stages.

How can a business prepare to change provider?

Inventory websites, databases, mailboxes, scheduled jobs and integrations. Confirm domain and DNS access and identify services hosted elsewhere. Prepare backups and a destination test plan before switching traffic.

The cutover plan should identify the authoritative location for new writes, the final delta-copy step and the conditions for rolling back. An older database may not contain new orders or bookings, so a rollback must protect those records too. Check forms, email and the main business workflow as well as the home page.

Control also needs a maintenance plan

Updates, backup checks and incident handling continue after a move. A clear division of responsibilities supports everyday operation and makes a future change of supplier easier. That independence matters more than the server label itself.

Explore our Linux server administration and technical support. Tell us about your environment and deadline so we can scope the inventory, backup and verification work.

Technical references

The official WordPress migration guide covers website files, databases and site addresses. The imapsync documentation explains IMAP migration and its limitations, including contacts and calendars, which it does not migrate. These resources do not replace a complete environment restore plan.

About the author

Leszek Iwaniec is the owner of Projectic. He works on online store implementations, custom applications and technical support. On the blog, he describes problems and solutions involving PrestaShop, Laravel and system integrations, drawing on the team’s project experience.

Szafy serwerowe i laptop, ilustracja migracji / Server racks and laptop, migration illustration

Illustrative image. It does not show the infrastructure of the institution described.

Back