Your apps don't need rebuilding. They need modernising.

AI agents draft the plan and write the code. Our engineers own the architecture, the risk and the sign-off. Modernise your .NET and Java apps on Azure, proven on a fixed-scope pilot, before you commit to a number.

GitHub Copilot writes the upgrade

Assess, plan, apply. In the IDE, on your code.

The migration agent is preview

Planning only. It does not move your app.

A human owns every pull request

The AI never ships to production alone.

Microsoft Managed Partners in South Africa
0 of 9
Microsoft Managed Partners in South Africa
0 GA today
South African businesses grown
1 +
Microsoft-certified professionals
1 +

There is no one-click modernisation.

Microsoft’s own engineers say it in writing. No silver bullet. No one-click, modernisation done. Agentic AI is a force multiplier for experienced teams, not an autonomous solution, and you should treat the vendor claims as marketing until you have seen them work in your own codebase. So that is exactly what Braintree does. We prove it in your code, on a scoped pilot, before we promise a number. One of nine Microsoft Managed Partners in South Africa, accountable locally.

The Microsoft stack you will run. Generally available, named honestly.

GitHub Copilot modernization

The AI that does the work. It reads the codebase, drafts the upgrade plan, applies the code fixes, validates the build, then a human reviews the diff and opens the pull request.

.NET and Java, in the IDE you already use

Framework upgrades and CVE fixes in one pass

Every change reviewed before it merges

GitHub Copilot modernization for .NET

.NET Framework to .NET. Newtonsoft.Json to System.Text.Json. Azure Functions in-process to isolated. Generally available.

GitHub Copilot modernization for Java

Java 8 to 17 or 21. Spring Boot 2 to 3. javax to jakarta. CVEs closed in the same pass. Generally available.

GitHub Copilot for Azure

Query Azure resources, generate infrastructure and CLI code, and troubleshoot, in natural language. Generally available in VS Code.

Azure Migrate

Free. Discover the estate, build the TCO business case, and assess each workload against the right Azure target. The evidence before the decision.

Assess. Plan. Transform. Validate. Review. Deploy.

The AI accelerates every stage. A human owns the one that matters. The review gate is a named step here, not a disclaimer at the bottom of the page.

01 · Assess
Know the estate before you touch it
Azure Migrate and code assessment
Discover the apps, the framework versions, the dependencies and the technical debt. The TCO business case, on-premises against Azure, before a decision.
The AI Jumpstart on-ramp
Nervous about agentic. Start with the safe assessment. Nothing in the codebase is touched yet.
02 · Plan
The path, drafted then owned
GitHub Copilot drafts the plan
The agent reads the codebase and writes a step-by-step upgrade plan. You read it before a single line changes.
Agentic migration, scoped honestly
Where the Azure migration agent helps, it plans only. Preview, VMware-first, it does not move your app. We say so on the page.
03 · Transform
The AI writes the upgrade
GitHub Copilot modernization
Applies the code fixes. .NET Framework to .NET, Spring Boot 2 to 3, javax to jakarta. CVEs closed in the same pass.
Re-platform onto Azure PaaS
Azure App Service, Container Apps or AKS. Monolith to microservices where the architecture itself is the debt.
04 · Validate
Proven, not assumed
Builds and tests
The agent validates the build and runs the tests. A red build does not progress.
Security re-scanned
The modernised app re-scanned for CVEs. The number that mattered, closed and evidenced.
05 · Review
The human gate. Named, not hidden
A human reviews every diff
Our engineer reads the change, not a summary. The AI never ships to production on its own.
The pull request, team-reviewed
The change opens as a PR. Your team reviews and merges. Standard engineering, accelerated, not bypassed.
06 · Deploy
Live on Azure, owned
App Service, Container Apps or AKS
Deployed to the right Azure target for the workload, not a one-size landing.
Run and optimise
Cost-to-run tracked, the estate optimised, the next modernisation candidate flagged.

We prove it in your codebase first. Built by Braintree.

Microsoft's own advice, productised. Share a scoped repository. We return a time-boxed assessment, the actual diff GitHub Copilot proposes, and the TCO business case, before you commit to a single number. No headline percentage borrowed from a brochure. The proof is in your code.

Built by Braintree

Discover, Evaluate, Deploy, Build.

Four stages. The business case first. The full TCO modelled. Committed only where the case proves out in your code.
01

Discover

Assess the application estate, the framework versions, the technical debt and the dependencies. Map where modernisation carries the strongest TCO case.

02

Evaluate

Full TCO and payback model, modernise against stand still, with the scoped-pilot diff as evidence. Presented to management. Sign-off before any code changes.

$ Management sign-off gate

03

Deploy

GitHub Copilot modernization applies the upgrade, a human reviews every diff, and the app is re-platformed onto the right Azure target.

04

Build

Where the architecture is the debt, re-architect to Azure-native patterns and add agent capability on Microsoft Foundry. Then run and optimise.

Braintree doesn't hand your codebase to an autonomous agent. We put experienced engineers in front of every change.

Upgrade in place or re-architect. The fork is where you start, not where you land.

Different applications need different moves. Read the column that applies.

Upgrade in place

Best when the application is sound, the runtime is old, and you need support and security brought current with the fastest payback.

Re-architect

Best when the architecture itself is the technical debt, the app blocks scale or AI, or the cost-to-run is too high.
Sometimes the answer is don’t. We will tell you when an application is fine as it is.
azm engineer | Braintree
The review gate, made visible. A Braintree engineer reads the diff before any change opens as a pull request.

1 of 9

Microsoft Managed Partners in South Africa. The accreditation that puts the architecture, and the accountability behind it, on a different tier.
Microsoft’s own engineering team has put the honest position in writing. There is no silver bullet, no one-click modernisation, and you should treat the claims as marketing until you have seen them work in your own codebase. We agree, and we built our offer around it. Behind the work: 100+ Microsoft-certified professionals, 220+ SA businesses grown, 10+ years on the Microsoft estate, SA data residency and POPIA-aligned access to your source code. We prove it in your code, on a scoped pilot, before we promise a number.

GA today, named honestly

GitHub Copilot modernization for .NET and Java, generally available. We label preview as preview.

Human-owned pull requests

Every AI change reviewed by an engineer and merged by your team. No autonomous deploys.

Generally available today, against public preview today.

We feature what is GA as real, and label what is preview as preview. That is the whole difference.
What you can use Public preview
GitHub Copilot modernisation for .NET
Assess, plan, apply. Upgrades .NET and moves it to Azure
GitHub Copilot modernisation for Java
Runtime and framework upgrades, javax to jakarta, CVEs closed
GitHub Copilot for Azure
Query, generate and troubleshoot, GA in VS Code
Azure Migrate, discover, assess, TCO business case
Free and generally available
Azure Copilot migration agent Preview. Planning and analysis only, VMware-first. Does not execute the migration
Azure SRE Agent Preview, region-limited. A forward look at agentic operations
Microsoft Agent Framework Public preview. The emerging successor to Semantic Kernel and AutoGen

Three specialists. One direct line. Plus the 8-minute readiness check.

We match you to the right specialist when you book the scoping call. Names land in your calendar invite, not on a page you scrolled past.

CB

Azure Architect

Architecture, GA against preview
& the risk sign-off

Microsoft Certified · Azure Solutions Architect Expert

ML

Modernisation Lead

Proof-pilot scoping
& the TCO business case

Microsoft Certified · Azure App Modernisation

DE

Developer Enablement Lead

GitHub Copilot modernization
& the human-review gate

GitHub Copilot · Developer Enablement

How modernisation-ready is your application estate?

8 questions, mapped against benchmarks from 220+ SA clients. You get a tier. Modernise-ready, Assessment-ready, Nearly ready, or Early. Plus the actions to close the gap.

Three steps. Five-day SLA. No sales pitch.

01

Tell us what you run today

Your application stack, the framework and runtime versions, the languages, and the apps that worry you most. Five to ten minutes on your side.

02

Get the assessment

Braintree returns a scoped modernisation assessment, the GitHub Copilot diff on a sample, the upgrade-or-re-architect recommendation and the TCO case. Inside five business days.

03

Pick the path

Upgrade in place or re-architect. Discuss the Azure target, the human-review workflow and the South African data residency answer. No sales pitch.

What CIOs and engineering leads ask before they book.

Does the AI migrate my application automatically?
The honest rule of thumb. Operator Connect suits most organisations. You pick a Microsoft-certified operator in the Teams Admin Center, there is no session border controller to deploy and no on-prem voice infrastructure to maintain. Direct Routing is the path when you need PBX coexistence, custom routing logic or specific in-country number ranges an operator cannot carry. It uses a SIP trunk and an SBC, so it carries more control and more to run. We assess your network, your number ranges and your coexistence needs, then recommend one. Most SA mid-market lands on Operator Connect.
It is the GitHub Copilot capability that modernises application code. It is generally available for .NET and for Java. For .NET it upgrades framework and runtime versions, moves Newtonsoft.Json to System.Text.Json, moves Azure Functions from in-process to isolated, and more. For Java it upgrades the runtime and frameworks, Spring Boot 2 to 3, javax to jakarta, and fixes CVEs in the same pass. It runs across Visual Studio, VS Code, the Copilot CLI and GitHub. Microsoft recently dropped the word app from the name, so older pages still call it GitHub Copilot app modernization.
No. The Azure Copilot migration agent inside Azure Migrate is in public preview, and it is planning and analysis only. It reasons over your inventory and helps you make migration decisions, but it does not execute the migration, and its end-to-end support is VMware-first today. We feature it honestly as preview, in the GA-versus-preview comparison on this page, rather than implying an autonomous capability that does not exist yet.
No. Every change the AI proposes is reviewed by a Braintree engineer and opens as a pull request that your team reviews and merges. The human review gate is a named step in our process, not a disclaimer in the footer. You keep ownership of the architecture, the risk and the sign-off.
No. AI-assisted conversion accelerates the work, but converted legacy code needs expert refinement before it is production-ready. That refinement is our service line, not an afterthought. This is exactly why we run a fixed-scope pilot on your codebase before we promise a number, rather than quoting you a headline percentage borrowed from a vendor brochure.
Azure Migrate is a free Azure service. It discovers your estate, builds a TCO business case comparing the cost of running on-premises against Azure, including year-on-year cash flow, the move from capital to operating expenditure, and Azure Hybrid Benefit savings, then assesses each workload against the right Azure target. It is the generally available, evidence-led on-ramp to a modernisation decision, and it is where we start.
It depends on why you are modernising. Upgrade in place suits a sound application on an old runtime that needs CVEs closed and support brought current, and it has the fastest payback. Re-architecture suits an application whose architecture is itself the technical debt, where you need to scale, cut cost-to-run, or add AI and agent capability. We assess both against your codebase and your TCO case before recommending one. Sometimes the honest answer is to leave an application as it is, and we will tell you that too.
Your code, your repositories and your workloads sit in your own Microsoft tenant and on Microsoft Azure, with the South African Azure regions available for data residency. Braintree engineers work under POPIA-compliant access controls from SA-resident workstations. A modernisation project touches your most sensitive asset, your source code, so we treat residency and access as a design decision, not a tick box. Braintree is one of nine Microsoft Managed Partners in South Africa, accountable locally.

Insights for CIOs and engineering leads modernising on Azure.

Technical debt

The cost of standing still. What an ageing .NET or Java estate really costs an SA business.

Licence drift, CVE exposure, the developers who cannot leave the legacy app, and the cloud bill you are not yet saving. The honest line items behind doing nothing.

GitHub Copilot modernization. What it actually does to your .NET and Java code, and what it does not.

GitHub Copilot

Assess, plan, transform, validate. The reviewable PR at the end. A clear-eyed look at the GA capability, the human gate, and where the hype runs ahead of the product.

Decision

Upgrade in place or re-architect. The five questions that decide it.

Runtime age, CVE exposure, cost-to-run, AI ambition and whether the architecture is the debt. A practical framework for the modernisation decision, not a feature table.

Azure Cloud gets you onto Azure. This makes what runs there worth running.

Azure Cloud

The infrastructure underneath. Azure Cloud gets you onto Azure. Migrate and host the estate. This page makes the result worth keeping. One team across both.

AI Jumpstart

Want the safe first step instead. The de-risked, low-code on-ramp. Copilot Studio and custom agents live there. Start AI without touching the codebase, then modernise when you are ready.

Modern Workplace

Microsoft 365 Copilot for your people. GitHub Copilot here is for developers. Microsoft 365 Copilot, the assistant in Word, Teams and Outlook, lives on Modern Workplace. Two different Copilots, two homes.

Let's grow.

30-minute scoping call. We assess your codebase, model the TCO of modernising against standing still, and tell you what to modernise first and how. We prove it in your code before we promise a number. No pitch deck.
Specialists in Business Applications, Modern Workplace and Azure.