Every estate is different, and not every move needs a consultancy. Sometimes Microsoft’s own import service, or the open-source tools with your own team, is the honest answer. If that is true for you, I will say so, and this conversation will have cost you nothing.
Tell me where you are, where you need to be, and what is driving the move. I will tell you what it will actually take, the risks specific to your estate, and which level of support fits.
What to include:
- What you’re running today (TFS / Azure DevOps Server version, collections, rough size)
- Where you’re headed: Azure DevOps Services, GitHub (or a hybrid, with Boards staying), a consolidated or separated organisation, or back to a local server
- What’s driving it: end of support, a merger or a sale, a cloud mandate, the GitHub question, data sovereignty, compliance
- Any deadline or constraint the plan has to respect
How engagements work, so there are no surprises: assessments are fixed-price and agreed before work starts. Migration quotes are priced from a pilot against your real data. Expenses are actuals only, with no markup. And if an engagement fails to meet the agreed standard, we refund your fee.