# Is business email part of website hosting? A mailbox receives and stores mail, while web hosting serves pages. Sharing a domain does not mean the services share a subscription or administrator. Moving example.com to a new web host should not casually delete the MX records used by the existing mail service. A contact form that stores an enquiry does not automatically create a company mailbox. If a form includes an email notification, decide whether the message contains the full enquiry or only a notice to review a protected record. That decision affects where personal information is copied and who can access it. Document the actual arrangement in the privacy explanation rather than assuming that a contact form is only a visual feature. For ordinary business email, keep staff-account changes separate from website content updates. Adding a new employee mailbox or recovering an account may require the mail administrator, while changing a published contact label may require the site maintainer. Naming both responsibilities prevents requests from being sent to the wrong person. At handover, confirm the owner can locate the relevant service providers and understands which channel receives customer messages. A clear division is especially valuable when the website and mailbox are intentionally hosted by different services. ## Give the mailbox and website separate definitions A business email address uses a domain name, but the mailbox service behind it is distinct from the website. The mailbox receives and stores messages and may provide applications or account settings for staff. Web hosting serves pages and related files. The two can use the same domain while being purchased from different providers and administered by different accounts. This distinction is useful during a website project. If a company already has working business email, a redesign may not need to change it at all. A developer should identify the existing arrangement before modifying domain records. Moving the website is not a reason to delete or recreate every service connected to the domain. A contact form is a third, related element. It may store an enquiry, send a notification or both, depending on the implementation. It does not automatically create a mailbox or replace a business email service. The form’s confirmation should describe the operation that actually succeeded rather than implying that several unverified delivery steps occurred. ## Protect existing email when changing web hosting Before a migration, document the relevant domain configuration and determine which records support the website and which support email. MX records are associated with routing mail to the intended provider; other mail-related settings may also need to remain in place. Do not remove records whose purpose has not been established. Limit the change to the services that are genuinely moving. If the existing mailbox provider remains, preserve the appropriate settings and account access. If email is also moving, treat that as a separate migration with its own requirements for users, existing messages, access and service continuity. It should not be hidden inside a casual instruction to connect the new website. Ask who owns the mail subscription and who can administer staff accounts. A business should retain appropriate control even if a developer assists with setup. Keep recovery and payment information private, and avoid storing mailbox passwords in a website repository or public configuration file. Documentation can name the required account without exposing its secret credentials. ## Specify how website enquiries reach the business For a form, define a reliable receipt method. If enquiries are stored in a database, identify how an authorized person retrieves them. If notifications are also sent by email, explain that separate channel and its configuration. A notification failure should not be confused with a storage failure, and a browser success message must correspond to a real confirmed operation. Test the actual workflow. Submit a controlled enquiry in the intended test environment, check the stored record and inspect any configured notification. Then distinguish those results from live deployment verification. A locally functioning form cannot prove that production secrets, storage or mail settings are correct. Consider an illustrative consultancy whose website moves to a static hosting platform while its business mail remains with an existing provider. The web pages and form endpoint change, but mailbox users and mail records can remain under the existing arrangement. The owner needs documentation for both systems, not a claim that the new website hosting now includes every communication service. Discuss recurring costs in the same terms. Domain renewal, mailbox subscriptions, optional notification services and website maintenance are separate items. Free static hosting does not make a business mailbox free. If a proposal includes help connecting an email service, distinguish that setup work from the provider’s continuing subscription and the administration of future staff changes. The final handover should allow the owner to answer three questions: where are the website files served, where do ordinary emails arrive and where can submitted enquiries be retrieved? Clear answers prevent a common source of confusion and make future changes safer without requiring the owner to manage all of the technical details personally. ## Practical checklist - Identify the mail provider - Preserve mail DNS records - Agree mailbox ownership **A concrete example:** Moving example.com to a new web host should not casually delete the MX records used by the existing mail service. **A boundary to keep clear:** A contact form that stores an enquiry does not automatically create a company mailbox. ## Your next step [Tell Orvunweb about your project](/en/start-a-project/) ## Related reading - [One-time website fees and ongoing expenses](/en/blog/one-time-website-fees-and-ongoing-expenses/) - [Domain, hosting and SSL explained](/en/blog/domain-hosting-and-ssl-explained/) - [Files and accounts to collect at website handover](/en/blog/files-and-accounts-to-collect-at-website-handover/) - [Business website service](/en/services/business-website/) - [Compare packages](/en/pricing/) ## Related services - [Business website](/en/services/business-website/) --- Locale: en Canonical: https://orvunweb.com/en/blog/is-business-email-part-of-website-hosting/ Updated: 2026-09-16