Changing managed IT providers in Reston: a handover checklist

Plan the handover before cancelling support

When changing managed IT providers in Reston, first establish who controls your accounts, what the current agreement requires, and which systems need continuous care during the change. Confirm notice periods and export arrangements before choosing a cutover date. Do not remove the old provider's access until the agreed replacement responsibilities are ready.

This checklist is for an owner or office manager coordinating a transition. It is not a technical migration procedure. Your current and incoming providers should turn it into a plan with named owners, approved access, test results, and a way to reverse a change that does not work.

Collect the business records

• Accounts: domain registration, internet, phone service, cloud tenant, backup service, and essential software subscriptions.
• People: authorized business contact, current provider, incoming provider, and application vendor contacts.
• Equipment: device inventory, network equipment, warranty details, and the location of any server or network cabinet.
• Open work: unresolved tickets, upcoming renewals, known faults, and already approved projects.
• Access records: who can administer each system and the approved secure process for transferring credentials.

Keep sensitive access details in a controlled password vault or another agreed secure channel. An email thread listing the project team is not a suitable place for passwords. Where records are missing, label the gap and assign discovery work instead of assuming the incoming provider can recover everything.

Confirm backup and access before cutover

Ask which data is protected, who owns the backup account, when the last successful recovery test happened, and whether changing the support agreement affects retention or licenses. Agree on a suitable recovery check before making a material infrastructure change. A successful backup-job notification is different from a demonstrated restore.

Review the remote tools and administrator accounts used by both providers. CISA and its partners advise organizations to control authorized remote software and protect access. Use their remote access guidance to support the handover discussion. The technical team should decide when to remove old tools and revoke permissions without leaving systems unmanaged.

Schedule changes around your office

For a Reston office visit, confirm who can admit the technician, whether building management must approve access, and when staff can tolerate an interruption. Mark business deadlines and any days when a key employee or vendor is unavailable. A calendar date should not replace a readiness check.

Prepare a short staff message with the new support number, how to submit a request, how to identify an authorized support session, and what to do if their usual email is unavailable. Use a previously trusted internal channel to distribute it.

Accept the handover in writing

1. Verify that an employee can request support and receive a useful response.
2. Confirm agreed devices are enrolled and the responsible team can see relevant alerts.
3. Record the recovery check and unresolved backup questions.
4. Review old administrator accounts, remote tools, and subscriptions with the outgoing provider.
5. Keep a signed-off list of completed items, remaining risks, owners, and next review dates.

Some work may continue after the initial handover. Make that visible. Avoid accepting a broad claim that the transition is finished when ownership of a critical application is still unclear.

Plan your Reston transition

UX Genius provides IT support in Reston from its Reston office. Explore our managed IT service scope. If you are still comparing providers, start with the Reston provider selection guide.

Book a free 30-minute IT assessment. It is a conversation about your priorities, with no obligation. We will contact you to arrange a time. A site survey, technical audit, or implementation is scoped separately. You can also call (703) 755-0014.