Onboarding.Day one that sticks.
Switching IT providers is the part everyone dreads. Ours is a written 4–6 week plan with 60+ tasks, a named project manager, and support you can reach from week one — not week six.
4–6 weeks end to end · 60+ tasks · zero gaps in coverageWhat actually happens, week by week.
Every onboarding follows the same project plan, tailored to your environment. You always know which phase you are in and who owns it.
We agree the plan before we touch anything
Scope, schedule, named contacts on both sides, escalation paths, and the working hours we must not disrupt. You leave the call knowing what happens on every one of the next 30 days.
We collect what your last provider never wrote down
Network diagrams, administrative credentials, authorised user lists, vendor and escalation forms. Most of the friction in a bad transition is missing documentation — so this is where we are strict.
Our engineers do the heavy lifting
Monitoring agents, endpoint protection, patching, backup verification and SOC coverage go in. Issues we uncover along the way get fixed as part of onboarding — not filed as future projects.
Your whole team learns how to get help
On-site training for all staff: how to raise a ticket, what counts as urgent, and how to reach the service desk at 6am on a Sunday. Adoption is the difference between a working help desk and an ignored one.
Services and billing start together
Coverage moves to full 24/7/365. Billing generally commences on the date of staff training — earlier only for services you asked us to start sooner. No invoices for work that has not begun.
Then the boring part begins — deliberately
Monitoring, patching, service desk and quarterly reviews with your vCIO. The measure of a good onboarding is how little you think about IT in month six.
What we need from you
Five things. Gather them before kick-off and onboarding runs at the fast end of the range.
- 01Network diagrams and asset inventory, if they exist
- 02Administrative passwords and admin access
- 03Your customer escalation procedure
- 04Authorised user lists and named contacts
- 05Vendor escalation forms and support contracts
What EMPIST handles
Everything else. Our engineering team owns the technical work and the coordination around it.
- Project management and the 60+ task plan
- Deployment of monitoring, security and backup tooling
- Resolving issues discovered during onboarding
- Coordination with your outgoing provider and vendors
- On-site staff training and documentation
You are never between providers.
All staff can open tickets directly from the training date onward. But designated contacts agreed at the kick-off call can raise tickets straight to your project manager from week one — so if something breaks mid-transition, someone at EMPIST already owns it.
Onboarding questions, answered
Timing, coverage, what we need from you, and who does the heavy lifting.
Get a Free IT Strategy Session ›How long does EMPIST onboarding take?
Will we be without IT support during the transition?
What do you need from us to get started?
When does billing start?
Who does the technical work?
Can onboarding move faster than four weeks?
From day one. IT, cybersecurity, AI, and cloud. On us.
Ready to stop worrying about IT?
Book a strategy session — we’ll map kickoff, coverage, and what your first 4–6 weeks look like.