Even if your website works, your business may not control the domain account, hosting subscription, or recovery email. Delegating technical work to an agency and giving up access to digital assets are separate decisions. Reviewing ownership, permissions, and transfer conditions together before a problem occurs makes business continuity easier to plan.

Domains, DNS, and hosting are different services

Domain registration allows an internet name to be managed through a registrar. DNS records direct visitors and email to the relevant services, while hosting is the environment where the application and data run. All three may be provided by the same company, but they need not share an account or contract. In the business inventory, record each service’s provider, contract holder, and renewal date separately. ICANN’s information for registrants explains how registration, renewal, management, and transfers relate to the registrar; country-code extensions also require reviewing the relevant registry’s rules. When planning an agency change, separate the scope into parts so that moving website files does not accidentally shut down email or DNS services.

  • Domain registrar and renewal date
  • Authoritative DNS provider
  • Hosting account and application owner

Do not share one password to establish company control

A primary account tied to one person’s personal email can become a management problem when that person leaves. Use company-controlled business contact and recovery methods, and give the agency a separate role suited to its work where possible. The person with management access, the bill payer, and the approver of technical changes need not be the same. Use a small permissions table to define who may perform each action. Keep multi-factor authentication enabled and know who holds the recovery procedure. Do not add passwords or verification codes to brief documents, messaging groups, or shared screenshots. Check working integrations and the necessary technical handover before revoking access; rushed removal can interrupt service.

  • Business-controlled recovery contacts
  • Permissions specific to the person and task
  • Technical handover checks before access removal

Ask for more than files in the handover plan

A ZIP file alone may not be enough for website delivery. Assess the database, media, application settings, license usage terms, scheduled jobs, and deployment instructions together. Clarify in the contract which files the business will own and the scope of usage rights; do not assume every third-party plugin is transferable. Ask the agency to explain which components depend on which providers and what happens when a subscription ends. Before a migration, check in a separate environment that a current backup can be restored. Finally, assign owners for DNS, email, forms, and measurement flows. These recommendations concern operational control; when legal interpretation of a contract is needed, have a qualified professional assess it.

  • File, database, and media delivery
  • License and subscription limits
  • Email and form checks after migration

Sources

LET’S ADAPT IT TO YOUR BUSINESS

Let’s define the next step together.

Share your goal and current situation; let’s discuss a scope suited to your needs.

Request a quote →