Buy certainty before you buy a migration
You have been asked for a plan, a date, and a number. The honest answer right now is that you don’t have any of them. Your estate has years of history in it: customised process templates, orphaned links, test suites nobody remembers, and workarounds nobody documented. Anyone who quotes you a migration without looking at that is guessing with your budget.
The direction does not change the discipline. Leaving a server for Services, merging organisations after an acquisition, carving one out after a sale, moving to GitHub, or leaving the cloud altogether: the assessment is the same in every case. Measure first, then promise.
Every failed migration we have been asked to rescue shares one root cause. Nobody measured the estate before the work started.
An assessment replaces guesswork with evidence. After it, you know what you have, what it will take to move, and what it will cost. You can defend the number to a sceptical budget-holder, or to a deal team holding a close date, because it came from your data, not from a sales call.
What happens:
- Estate analysis. Collections, projects, process templates, work item counts, customisations, test artefacts, and pipelines. What exists, what is used, and what can be left behind.
- A pilot migration. We run a representative slice of your real data through the move. The risks that will bite you show up here, in a rehearsal, instead of in production.
- A migration plan. Sequencing, tooling choices, cutover approach, and the risks specific to your estate. Tooling means whatever fits: Microsoft’s import (the first option we test, because fidelity wins), GitHub’s importer, the open-source tools, or custom work.
- A fixed quote. For guided or managed delivery, priced from the pilot. A number that survives contact with your data.
The assessment is fixed-price, agreed before work starts. The plan is yours whether or not we deliver the migration. If the honest conclusion is that your team can do it alone, or that Microsoft’s import service fits, that is what the plan will say.
This is not for you if you have a single project, matching process templates, and no test plans. You probably don’t need an assessment. Start with the open-source tools and their documentation , and come back if it gets complicated.
If the assessment fails to meet the agreed standard, we refund your fee.
Start with the facts.
Tell me what you're running today: versions, collections, rough size. I'll tell you what an assessment of your estate involves and what it costs.
Get in touch