- Your MSP contract is expiring, or the relationship has reached the decision point
- You are insourcing, outsourcing, or moving one platform (M365 tenant, file services, identity)
- Two IT setups need to become one after an acquisition
- Or nothing is being outsourced and the service has simply broken: repeat outages, unowned systems, one irreplaceable person
- Up to 150 employees, up to 3 locations, one outgoing and one incoming provider
All services
01 · Delivery remediation & optimization
IT Transition & Turnaround
Change your provider, your platform or your whole IT setup without losing a day of business.
- 8–12 weeks
- ~25–30 consulting days
- From 750,000 HUF + VAT
- Onsite for cut-over
The problem
The messy part of changing providers is nobody’s job.
Your outgoing provider knows more about your IT than you do, and has no incentive to make leaving easy. Your incoming provider has an onboarding plan written for their own convenience, and cannot see what they are inheriting. And you are the only party who carries the consequences if something is missed.
Nobody has the list of what actually has to be handed over. Nobody is sure which accounts the old provider still holds. The cut-over date was picked because a contract expires, not because anything is ready. That is how transitions produce outages, lost licences, orphaned access and months of finger-pointing — and how you end up paying twice, once for the overlap and once for the clean-up.
The same is true when nothing is being outsourced at all and the service has simply broken down: recurring outages, systems nobody owns, one person who knows how it all works and is about to leave.
Who it's for
- CEOs, founders and operations managers — and CFOs, when the trigger is a contract renewal
- Your internal IT and both providers become direct counterparts; a named client-side sponsor is required
- Multi-provider chains, several sites, or a transition coupled with a company merger are quoted individually
What happens
Six steps, eight to twelve weeks.
- Mobilisation One week. Sponsor kick-off onsite, contact lines opened with both providers, access to the contracts and whatever documentation exists.
- Discovery and inventory Two weeks. Systems, data, accounts and privileged access, licences, contracts, runbooks and the knowledge that only lives in people’s heads — with interviews on both sides.
- Scope Statement and transition plan One week. The plan, the RACI across you and both providers, the cut-over criteria and — just as important — the rollback criteria. From this point the scope changes only by written change order.
- Execution Three to six weeks. A weekly transition board with both providers, knowledge-transfer sessions, the runbook pack built, and a rehearsal where one is possible.
- Cut-over and verification One week. Onsite on the day. Afterwards, the outgoing provider’s access is verified removed — not declared removed — and the service baseline measurement starts.
- Hand-over One week. The acceptance report, the KPI baseline, and every open item with a name and a date against it.
Premium adds twelve weeks of hypercare after hand-over: fortnightly service reviews with the new provider, KPI tracking, and closure of whatever the transition left behind.
What you get
Five documents, and a service that still runs.
Everything that has to move or be stabilised: systems, data stores, accounts and privileged access, licences, contracts, runbooks — each with an owner, a criticality and a decision (move, retire, keep, document).
Every risk to continuity, data, access and compliance, including the contractual gaps — a missing exit clause, unclear data return — with priority, treatment and owner.
What is in scope, who does what across you and both providers, the cut-over date, and the rollback criteria. This is the scope baseline.
A runbook for every business-critical system as it will operate after cut-over — access, backup and restore, escalation, known issues — plus the record of what the outgoing provider handed over and to whom.
Evidence, not assurances: the cut-over record, verified removal of the old provider’s access, licence and data return status, the post-cut-over KPI baseline, and the open items.
Packages
- Entry — transition readiness check Before you commit to a date: what has to move, what your contracts actually oblige the outgoing provider to do, the transition risks, and a go/no-go recommendation. 750,000 HUF + VAT.
- Standard — the transition itself Everything on this page, from inventory through cut-over to hand-over. 4,200,000 HUF + VAT, fixed price.
- Premium — with hypercare Standard plus twelve weeks of stabilisation and fortnightly service reviews with the new provider. Quoted individually.
- Custom Several providers, several sites, or a transition alongside a merger. Quoted individually.
Payment is 40% at signature, 30% at scope confirmation, 30% on the hand-over report. The Entry fee is credited in full against Standard or Premium if you continue within 60 days.
- One executive sponsor and one internal counterpart — this is the part that cannot be outsourced to us
- Access to the provider contracts and SLAs, including the exit terms
- Both providers contractually required to cooperate with the plan; if your contract has no exit clause, that becomes the first entry in the risk register
- Decisions on cut-over and rollback within two business days of our recommendation
- Requested information within five business days; delays move milestones, they do not shrink the work
- Not the technical migration itself — your providers or internal IT execute; we plan, coordinate and hold them to it
- Not contract negotiation — we advise, you sign
- Not licence procurement
- Not the ongoing service after hypercare ends
- Not a second transition: one event per engagement, named in the Scope Statement
Next step
Before you pick a cut-over date.
The cheapest moment to have this conversation is before the date is fixed and before the contract is signed. If your transition turns out to be simple enough to run yourself, we will say so.