Boeing, Philips, Lockheed Martin, and the UK Government's DWP trusted us inside the systems their delivery depends on.
Azure DevOps migration services
Leaving TFS. Consolidating after a merger. Moving to the cloud. The move itself is not the biggest risk: losing history, compliance evidence, and months of team momentum is. We plan, execute, and validate migrations where delivery continues throughout, and downtime becomes a design choice, not an inevitability.
Where you might be
If one of these sounds familiar, you're in the right place. The one thing they share: waiting does not make any of them cheaper.
TFS or Azure DevOps Server out of support, upgrades deferred for years, the people who set it up long gone. Or the cloud move is approved but the standard import doesn't fit your estate. Every month it runs is unmanaged risk.
A merger needs collections, organisations, and process templates to become one. A sale needs part of the estate to leave, cleanly and provably. Both run on the deal's clock, and the history your compliance team depends on has to survive.
The board is asking about GitHub, or compliance is asking about leaving the cloud altogether. Both questions have honest answers, and one of them is often "move less than you think".
An in-house or third-party attempt stalled, corrupted data, or silently dropped history. You need someone who has seen this before, and fixed it.
Choose your path
Some estates can move with free, open-source tooling and your own engineers. We will tell you if yours is one of them. Others carry too much history, complexity, or deadline risk to learn on the job. Bring us in at the level your situation demands, not the level a salesperson suggests.
Buy certainty before you buy a migration. We analyse your estate, run a pilot against your real data, and give you a plan and a fixed quote you can defend to your board.
Scope your migrationYour team runs the migration. We plan it with you, stay on call for every difficult decision, and make sure your first mistake is not a production one. The capability stays in-house.
Get expert backupWe take the whole migration: planning, execution, validation. Your teams keep shipping while the estate moves. One accountable partner, a fixed scope, and evidence of what moved.
Hand it overA migration that has stalled, corrupted data, or dropped history. We find out what state it is really in, save what can be saved, and get it to done. The sooner we see it, the more survives.
Get unstuckThe tooling
We use whatever fits your estate: Microsoft's own import service, our open-source tools, or custom tooling built for your edge cases. The open-source tooling is documented at devopsmigration.io and free to use without ever talking to us.
Microsoft's free, full-fidelity path from Azure DevOps Server into the cloud. It is the first option we test on every migration. What it requires, what surprises people, and when it cannot fit.
See when it fitsOpen-source tools for migrating work items, test plans, and history between TFS, Azure DevOps Server, and Azure DevOps Services. Free to use. We built them, we maintain them, and we will tell you honestly whether they are all you need.
See the toolsThe successor to the Azure DevOps Migration Tools. Open source, free, and available now. Currently experimental: expect rough edges and fast change, and know exactly where it is headed.
See what's nextBoeing, Philips, Lockheed Martin, and the UK Government's DWP trusted us inside the systems their delivery depends on.
Why NKD Agility
That was one Fortune 500 engagement. The tooling we built to do it became the open-source Azure DevOps Migration Tools, and the pattern has held across hundreds of migrations since: the estate moves, the record survives, and your teams barely notice. The migration ends. The capability stays.
Work item history, links, attachments, and test data move with full traceability.
Every migration is piloted, measured, and verified before anyone flips a switch.
Teams keep working. Cutover happens in a small window we plan around your delivery.
If a simpler path fits, including Microsoft's own import, we tell you. Turning work away is how you know the advice is real.
Led by Martin Hinshelwood. Microsoft MVP, ex-Microsoft ALM Ranger, and creator of the Azure DevOps Migration Tools. Working with TFS and Azure DevOps since the first release in 2005: pattern recognition across hundreds of migrations, so your estate is not the one we learn on.
Case studies
Frequently Asked Questions
If your question isn't here, ask us directly.
Most migrations fail in the planning, not the execution. Tell me where you are today, where you need to be, and what you've already tried. I'll tell you honestly what it will take. If a simpler path fits, I'll point you at it. And if we do work together and the engagement fails to meet the agreed standard, we refund your fee.