The first month of managed IT should establish who owns access, what systems are covered, how staff get help and which risks need a separate decision.
Agree what must work on day one
List the accounts and systems that stop the business if access fails: the domain, cloud tenant, identity service, network, support inbox and backups. Name a business owner for each. Ask the outgoing and incoming teams to agree on the approved way to transfer access and how staff will reach support during the overlap.
| When | Check | Evidence to retain |
|---|---|---|
| Before handover | The business owns its key accounts and has an authorized recovery contact. | Ownership and access checklist, with unresolved exceptions named |
| First week | Covered users and devices can reach support and critical systems are inventoried. | Test ticket, system inventory and escalation contacts |
| First month | Monitoring and backups report on the systems in scope and a restore can be tested. | Coverage report, restore evidence and remaining remediation plan |
Check one realistic handover scenario
Ask an authorized staff member to open a test ticket for a representative device. Confirm the team can identify the device, the named contact receives updates and the escalation path works. Pick a backup workload and agree who will test the restore and who checks that the recovered work is usable. Record what remains outside the agreement before closing onboarding.
Use the provider transition guide if an outgoing provider is involved. Compare recurring coverage and one-time work in the managed IT pricing guide.
Bring your current provider, site list and the systems that must stay available. Explore NetSys managed IT services.
Related reading
Discuss managed it services for your business.
Tell us about your current systems, the result you need and your timeline. We will discuss the work, responsibilities and pricing before you decide on an engagement.