Australia · English
Client Portal|Service Request|02 6189 1322
EMPREUSIT SUPPORT · CANBERRA
EMPREUSIT SUPPORT · CANBERRA
02 6189 1322
support@empreus.com.au
Unit 19/63 Wollongong St, Fyshwick ACT 2609
Empreus · Onboarding

How we onboard.

A considered 30 to 45 day transition. Documented, deliberate, and built so nothing falls through the gaps when you switch providers.

30–45 Days
Typical Transition
7 Phases
Documented
1 Named
Transition Lead
0 Surprises
at Go-Live
The Process

Seven phases.

01
Week 0 · 1 hour
The Conversation

An honest first chat. No pitch. We meet — in person at Fyshwick or by video — to understand what you have, what's working, and what isn't. We'll ask about your team, your environment, your past providers, and what made you start looking. We'll tell you honestly whether we think we're the right partner. If we are, we'll send a draft engagement proposal within five business days. If we're not, we'll tell you who we think might be.

  • Discovery call (60 minutes, no obligation)
  • Indicative scope and pricing within 5 business days
  • An honest recommendation, either way
02
Week 1 · 2–3 days
The Audit

Once we've agreed to proceed, we visit. We walk your sites, open your cabinets, review your stack, and meet your team. We complete our Transition Information Request — a structured questionnaire covering your environment, vendors, licences, contracts, escalation paths, and the small details that matter. You receive a written audit report with findings, risks, and recommended quick wins.

  • Site walk-through and cabinet audit
  • Transition Information Request completed jointly
  • Written audit report and risk register
  • Quick wins identified and prioritised
03
Week 2 · 5 days
The Build

We deploy our managed stack to your environment. SuperOps agents go on every endpoint. Huntress provides managed EDR. Proofpoint protects email. Cove backs up Microsoft 365 daily. Hudu becomes your living documentation — every device, password, contract, and runbook in one place. Where you have existing tools, we evaluate them. Where they're better than ours, we keep them.

  • SuperOps agents deployed and verified
  • Huntress, Proofpoint, and Cove activated
  • Hudu documentation built and populated
  • Existing tools reviewed — we keep what works
04
Week 3 · 3–5 days
The Handover

We coordinate directly with your previous provider for credentials, ownership transfers, runbook handovers, and outstanding contracts. We use a written handover checklist — nothing relies on memory or goodwill. Your team meets the engineers who'll be answering the phone.

  • Credential and ownership transfers, documented
  • Domain, M365, Azure, and hosting access verified
  • Escalation matrix shared with your team
  • Introduction to your assigned engineers
05
Day 30 · Half a day
Go-Live

Quiet, planned, and undramatic. We flip the switch — support now routes through Empreus. Your team lodges their first tickets. We're available all day. The monitoring is live. The documentation is current.

  • Support routing live through Empreus
  • First tickets lodged and resolved
  • Full-day availability from the team
  • Monitoring confirmed across all endpoints
06
Days 30–90 · Ongoing
The First 90 Days

The relationship deepens. We work through the inevitable surprises every new environment reveals. We refine documentation. We resolve the items from the quick-wins list. We hold a 30-day review call and a 60-day review call.

  • 30-day and 60-day review calls
  • Quick wins completed and documented
  • Environment documentation refined
  • Any issues from go-live closed out
07
Day 90 onward
The Steady State

By day 90, the unusual should be unusual. You know our engineers. We know your environment. The runbooks are current. The monitoring is tuned. The work that was visible in the first ninety days now happens in the background, where it belongs.

  • 90-day review and service health report
  • SLA performance reviewed
  • Annual planning conversation scheduled
  • You stop thinking about IT — which is the goal

Onboarding done badly is where MSP relationships go to die.

We've inherited enough broken environments to know what bad onboarding costs. Ours is designed to surface the problems before go-live, not after.

Start a Conversation

Stay Informed

Occasional notes from the Empreus journal — security advisories, Microsoft 365 updates, and the occasional studio bulletin.