Cutovers that hold
Every engagement gets a runbook, a validation checklist, and a rollback plan before anything moves. The window is the window.
I'm Alex Tafoya. For over nineteen years I've moved organizations' data, desktops, applications and infrastructure from where they are to where they need to be.
Defined projects with defined outcomes.
Big integrators staff projects with whoever is on the bench. You get me — the person who scoped the work, on the call during cutover.
Every engagement gets a runbook, a validation checklist, and a rollback plan before anything moves. The window is the window.
Throughput gets tested on a pilot batch against production-like data, so the schedule reflects your storage and network, not a vendor datasheet.
You get continuity from scoping through hypercare. Nothing is handed to a delivery pod you've never met.
Runbooks, diagrams, and scripts are yours at the end — written so your team can repeat the work without me.
I work alongside internal staff and existing vendors, in your ticketing and change process, without turf.
Every engagement follows the same four steps.
A working session and a look at the real environment — not a questionnaire. I map sources, targets, dependencies, and the constraints nobody wrote down.
A written migration plan with a rollback path, then a pilot batch against real data so the estimates come from measurements instead of optimism.
Runbook-driven execution in the agreed window, with validation gates and a clear go/no-go call at each one.
Documentation your team can actually operate from, plus a hypercare period so the first week after go-live isn't a surprise.
| Model | What you get | Typical length |
|---|---|---|
| Fixed-scope assessment | A defined piece of analysis with a written deliverable — a plan, an assessment, a DR gap review. Fixed price. | 1–3 weeks |
| Project delivery | End-to-end ownership: planning, execution, cutover and handover, with acceptance criteria agreed up front. | 1–6 months |
| Retained hours | A monthly block for escalations, upgrades, design reviews and second opinions. | Ongoing |
Based in Olathe, working across the KC metro. For clients across Johnson County and the Kansas City metro, being on site for a cutover weekend is a drive, not a flight. Remote everywhere else.
Send the source, the target and the downtime you can tolerate. You'll get an honest read on scope.
Not currently accepting new project work. Please still reach out. I'm scheduling future work, I'm glad to answer a quick question, and if I can't help I'll point you to someone who can.