Complex migrations,
delivered without the drama.
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.
Infrastructure work, end to end
The areas I'm brought in for — most engagements touch two or three of them at once, because that's how real environments are built.
Data Migrations
Planning and execution for file, storage, database, and application data migrations — with validation, reconciliation, and a rollback path.
Read moreVirtual Desktops & Citrix
Design, migration and rescue work for Citrix Virtual App and Desktop environments — including image management and profile strategy.
Read moreDocument Imaging
Getting documents out of an old or unsupported imaging system and into a format the new one will actually ingest — images, index data and all.
Read moreCore Conversions
Independent, bank-side support through a core system conversion — data validation, balancing, and someone whose only interest is your outcome.
Read moreDatabase Programming
Import and export routines, conversions between systems that were never designed to talk, and the recurring data jobs your team runs by hand.
Read moreData Aggregation
Pulling data out of systems that don't talk to each other and combining it into one reporting database — kept current automatically, not rebuilt by hand.
Read moreAutomation
PowerShell, Python and Ansible automation for provisioning, onboarding, reporting and the repetitive work quietly consuming your team's week.
Read moreWhy bring in an independent
Big integrators staff projects with whoever is on the bench. You get me — the person who scoped the work, on the call during cutover.
Cutovers that hold
Every engagement gets a runbook, a validation checklist, and a rollback plan before anything moves. The window is the window.
Estimates from measurement
Throughput gets tested on a pilot batch against production-like data, so the schedule reflects your storage and network, not a vendor datasheet.
One accountable person
You get continuity from scoping through hypercare. Nothing is handed to a delivery pod you've never met.
Documentation you keep
Runbooks, diagrams, and scripts are yours at the end — written so your team can repeat the work without me.
Fits your team
I work alongside internal staff and existing vendors, in your ticketing and change process, without turf.
A predictable shape to every engagement
Nothing here is novel. It's just consistently done, which is the part that separates a boring cutover from a memorable one.
Discovery
A working session and a look at the real environment — not a questionnaire. I map sources, targets, dependencies, and the constraints nobody wrote down.
Plan & pilot
A written migration plan with a rollback path, then a pilot batch against real data so the estimates come from measurements instead of optimism.
Cutover
Runbook-driven execution in the agreed window, with validation gates and a clear go/no-go call at each one.
Handover
Documentation your team can actually operate from, plus a hypercare period so the first week after go-live isn't a surprise.
Have a migration on the calendar?
Tell me the shape of it — source, target, data volume, downtime tolerance — and I'll tell you honestly whether I'm the right fit and what it should take.