Sample IT
onboarding plan.
This is how an onboarding plan from Chrysalis is laid out, phase by phase. Use it to see what the work covers and what we would ask of your team.
Illustrative sample only. This is not a real client’s plan and not a timeline commitment. Your actual plan is written with you after discovery, and its order and timing depend on your systems.
How to read this sample.
Onboarding moves a business from its current IT setup to managed IT with Chrysalis. The sample below runs through six phases: discovery, inventory and documentation, an ownership and escalation matrix, a security baseline, a transition checklist and a first review. Each phase lists what happens, what you get and what we need from you. Real plans keep this shape and change the detail.
The six phases.
Phases can overlap, and anything urgent found along the way is raised with you rather than held for a later phase.
- 1
Discovery
Understand the business before touching the technology.
What happens
- Conversations with the owner and key staff about how work gets done
- A list of business-critical systems and when they are needed
- Known problems, recent incidents and planned changes
- Contacts for your current IT provider and main vendors
What you get
Agreed priorities and the scope for onboarding.
What we need from you
A main contact, and time with the people who know your systems best.
- 2
Inventory and documentation
Write down what you have, so nothing depends on one person’s memory.
What happens
- Record computers, servers, network equipment, printers and phones
- List software, licenses and accounts, including Microsoft 365
- Map the network and internet connections at each location
- Gather administrator access and record it securely
What you get
A documented inventory of your environment that your team can refer to.
What we need from you
Access to your systems, plus any documentation or vendor details you already hold.
- 3
Ownership and escalation matrix
Agree who owns what, and who to call when something goes wrong.
What happens
- Name an owner on your side for each system
- Set out what Chrysalis looks after and what stays with vendors
- Agree who can approve changes and spending
- Write down the escalation path for urgent issues
What you get
A matrix your team can find when they need it, like the example below.
What we need from you
Names, roles and who signs off on changes.
Example rows only. A real matrix is filled in from your discovery and your agreed scope. System Owner at your business Chrysalis Outside vendor If it is urgent Email and Microsoft 365 Office manager Accounts, security settings and user support Microsoft Call client support on 713.575.2626 Internet connection Office manager Watches the connection and works faults with the provider Internet provider Chrysalis contacts the provider; the owner approves any change to the service Business application Department lead Computers, access and sign-in around the application Software vendor Chrysalis raises the issue with the vendor and keeps the owner updated Phones Operations lead The phone system and handsets in scope Phone system provider Call client support on 713.575.2626 Backups Owner or partner Runs and checks the backups in scope Backup platform Chrysalis leads recovery; the owner approves any restore - 4
Security baseline
Check the basics and agree what to fix first.
What happens
- Check multi-factor authentication on email and remote access
- Review updates and patching on computers and servers
- Confirm what is backed up, and test a restore
- Check endpoint protection, firewall settings and administrator accounts
What you get
A baseline report with fixes in priority order.
What we need from you
Decisions on fixes that change how people work, such as an extra sign-in step.
- 5
Transition checklist
Move support over cleanly from your previous provider or in-house setup.
Checklist
- Access and passwords handed over by the previous provider
- Domain, licensing and vendor accounts confirmed in your name
- Monitoring and support tools installed
- Old tools and old access removed
- Staff told how to get help: 713.575.2626 and the client portal
- Cutover date agreed and shared
What you get
A completed checklist and an agreed date when Chrysalis takes over support.
What we need from you
Cooperation from your previous provider. Chrysalis can coordinate that handover with you.
- 6
First review
Look back at onboarding and agree what comes next.
What happens
- What onboarding found and fixed
- Open issues, and anything outside the agreed scope
- What support requests are showing so far
- Progress against the security baseline
- Priorities for the next stretch, and how often to meet
What you get
An updated plan and an agreed rhythm for reviews.
What we need from you
Time with the people who make technology decisions.
Reminder: this page is an illustrative sample, not a client’s plan and not a commitment to any timeline. Your plan is agreed with you and reflects your systems, your scope and your priorities.
Onboarding questions.
Ask us something elseIs this a real client’s onboarding plan?
No. It is an illustrative sample that shows the shape of a Chrysalis onboarding plan. It does not describe any client’s systems.
How long does onboarding take?
That depends on the size and condition of your environment, which is why this sample carries no day or week counts. Your own plan sets out the timing once discovery is done.
What should we prepare before onboarding?
A main contact, a list of the systems your team relies on, and contact details for your current provider and key vendors. Anything else comes up in discovery.
Do we need our previous provider’s cooperation?
It helps. The transition checklist covers access, accounts and handover, and Chrysalis can coordinate that work with you.
What happens after the first review?
Day-to-day support carries on, with 24/7 IT support by phone and through the client portal, and reviews at a rhythm agreed in your plan.
Want a plan written for your business?
Start with a conversation about your systems and priorities. Your onboarding plan is written with you after discovery.