Azure DevOps Server to Azure DevOps Services Migration

It is a fixed-scope project in which IT Partner moves your on-premises Azure DevOps Server or TFS collection into Microsoft's cloud-hosted Azure DevOps Services using Microsoft's official Data Migration Tool — readiness validation, Entra ID identity mapping, a dry-run import, the production cutover, and reconnection of agents, service connections, and extensions. Estimated at $3,950 per project and about 3 weeks, with a fixed written quote confirmed after readiness.

No — this is the reason to use Microsoft's Data Migration Tool rather than copy-paste tooling. It imports the entire collection database with full fidelity: work items with their history and attachments, Git and TFVC repositories with complete commit and changeset history, test plans, and pipeline definitions. What does not carry over automatically is a short, known list — agent registrations, service connection secrets, extensions — and reconnecting those is part of this service.

Yes, but with a step first: the Data Migration Tool only accepts the two most recent Azure DevOps Server releases, so older servers must be upgraded to a supported version before import. One upgrade hop is included in this service where required; a server several versions behind needs a multi-hop upgrade, which the readiness assessment identifies and the written quote prices explicitly — before work begins, not as a surprise afterward.

Your team works normally through readiness, preparation, and the dry run — the source server stays live. Downtime happens only at the final cutover, when the collection is detached for the production import. Its length depends on collection size and the import method, and because we run a full dry run first, the estimate we give you for the cutover window is measured, not guessed.

Every identity in the collection is mapped to a Microsoft Entra ID account so that sign-in, permissions, and history attribution survive the move. We prepare the mapping file, review it with you (including how to handle departed employees and service accounts), and validate it before import. If your users are not in Entra ID yet — still purely on-premises Active Directory — that is a prerequisite we will name honestly, and our On-premises Active Directory to Microsoft Entra ID Transition service covers it.

Pipeline definitions import with the collection. What needs rebuilding is the connective tissue: self-hosted agents must be re-registered against the new organization, service connections re-created with fresh credentials (secrets deliberately do not migrate), and marketplace extensions re-installed. We do that reconnection and verify a representative build and release run green before closeout. Converting classic pipelines to YAML or redesigning your delivery process is separate, deliberately — see the CI/CD Pipeline Implementation service.

That is a different project with different tooling, and we scope it too. Some teams are better served by GitHub (especially those standardizing on GitHub Actions and GitHub Advanced Security); others get the fastest, highest-fidelity move via the Data Migration Tool into Azure DevOps Services and evolve from there. Tell us where you want to end up and we will quote the right migration rather than the one on this page.

The Data Migration Tool imports one collection into one new Azure DevOps Services organization. Multiple collections become multiple organizations, each its own import — quoted accordingly. Consolidating several collections into a single organization is possible but is surgical, third-party-tooling territory and is scoped as a separate engagement with its trade-offs stated plainly.

Azure DevOps Services is billed by Microsoft per user: the first five Basic users in an organization are free on Microsoft's published pricing, users with Visual Studio subscriptions are typically covered, and additional Basic users are paid monthly. We verify what your team will need during readiness — but confirm current rates against Microsoft's published pricing, since they are Microsoft's numbers, not ours, and can change.

That is what it is for, and it usually finds something — size issues, identity gaps, unsupported customizations, version problems. Remediation of validation findings is part of the service, and anything that materially changes scope (like a multi-hop upgrade) goes into the written quote before work begins. The rule throughout: no production import until validation is clean and the dry run is verified by your team.

Keep it offline but intact through an agreed verification period as a safety net, then decommission it — we hand over written guidance for that. If the retirement of that server is part of a bigger question (the Windows and SQL Server underneath it are usually aging too), our Azure migration services cover moving or retiring the rest of the stack.

$3,950 is the typical price for a single-collection migration with a supported or one-hop-upgradable server. The readiness assessment in week one converts it into a fixed quote in writing — covering any upgrade work and your specific collection — which you approve before migration work begins. Per IT Partner's standard terms, you pay after you approve delivery.

Yes, until the cutover window. Readiness, the upgrade hop if needed, identity mapping, and the dry run all happen alongside normal work on the live server. The only freeze is the final import window, which is scheduled with you — typically outside working hours — and its length is estimated from the dry run.