Blog / Web management /

What to prepare before a website host changes support teams

A hosting ticket is handed to a new support team, and the first reply asks questions the previous team already answered. Which service hosts the email? Who controls DNS? Is that odd rule deliberate?

The problem is lost context. A host changing support teams may not need any infrastructure move, but the people handling the next issue need a usable map of the arrangement. Preparing it saves the business from rediscovering important decisions in the middle of an urgent request.

Hosting, DNS, SSL and client training sit within my Nivonix experience, and what I focus on is practical: ownership, dependencies, active issues and enough history to explain why the setup looks the way it does.

Confirm what is actually changing

Ask whether the change affects only the people providing support or also accounts, systems, service terms and escalation routes. A staff handover isn’t a migration, and a provider announcement won’t explain every operational detail.

Record the effective date and the new contact process. Confirm how authorised people identify themselves and which account owns the service. Use established provider channels to verify instructions, particularly where a message asks for account or payment changes.

Explain the change internally in plain language. Colleagues need to know where requests go and whether anything they use will change. Don’t announce downtime unless some is actually planned.

Prepare a concise service map

List the website, hosting account, domain registration, DNS, email-related services, certificate arrangements and backups relevant to support. Identify the owner of each service and where the authorised account details are managed.

Separate services that share a provider from services that merely share a domain name. A website host may not control email, and a registrar may not serve the active DNS records. Get that wrong and the request goes to the wrong team.

I would include a simple description of important connections. For example, the website may send form notifications through a separate provider. The support team needs to know that dependency exists without receiving a document full of passwords.

Preserve the reasons behind unusual settings

Some configurations look unnecessary until someone knows their purpose. Record approved exceptions, redirects, scheduled jobs and integrations that support important tasks. Explain why they exist and who can authorise a change.

Not every old setting is intentional. Mark uncertain items for investigation instead of inventing a reason to keep them. A handover is a chance to separate known requirements from historical clutter.

Keep source references where available, such as a previous resolved ticket or an internal decision record. Summarise the useful conclusion so the next team does not have to read an entire conversation before understanding the dependency.

Review open issues and ongoing work

Prepare a list of active tickets with their impact, current status, evidence and next action. State what has already been tried. This helps prevent the new team from repeating a change that was ruled out for a documented reason.

For an intermittent issue, include the observed times and affected customer task. Separate confirmed behaviour from suspected cause. “Form notifications were delayed during this period” is an observation; attributing it to a particular server requires further evidence.

Identify planned maintenance that may overlap the transition. Agree who is responsible for it and whether the timing remains appropriate. Do not let a scheduled task assume an owner simply because it appeared on the old team’s calendar.

Confirm recovery and escalation routes

Establish who can authorise a restore, who handles domain-related problems and how the business escalates an urgent service failure. Ask what information the new team expects in a request and what its response commitments actually cover.

Check backup ownership and access without assuming a listed backup can restore the service you need. Keep any recovery-test evidence and known limits to hand. If a check is still needed, assign it instead of calling recovery guaranteed.

Review out-of-hours arrangements where the business needs them. A contact address is not the same as an attended support route. Internal stakeholders should understand the agreed coverage before an urgent issue exposes the gap.

Use a small handover check

Ask the new support contact to confirm the service map, active issues and escalation process. A short review can reveal misunderstandings while there is time to resolve them. Keep a record of agreed corrections.

Choose a safe, ordinary support question to check that the route works. Avoid creating a live fault for the sake of testing responsiveness. The goal is to confirm access and understanding, not manufacture an incident.

Update internal instructions once the transition is complete. Remove obsolete contacts and identify who maintains the handover information. The document should remain useful after the announcement has disappeared from everyone’s inbox.

Keep the handover pack current during the transition. If a configuration changes after the document is written, update that section and tell the new team where the revision is. Put a visible revision date on it, and give one person the job of coordinating corrections while each service owner confirms their own details.

Before the support team changes, find the one configuration detail a new person is most likely to misunderstand. Can you explain its purpose and owner in a paragraph?