SAP project tracking tools in 2026: four that actually work

For most new S/4HANA programmes, the right tracking tool is SAP Cloud ALM: it reads transports, tests and phases straight from the SAP system, and customers with Enterprise Support or a cloud subscription pay no licence fee. Jira or Microsoft's Planner and Project make sense only when your organisation already runs on them and someone owns the integration. SAP Solution Manager still fits complex on-premise landscapes, but its mainstream maintenance ends in 2027. This guide is for programme managers and PMO leads choosing or fixing a tool. It compares the four options and ends with a checklist. The test that matters: can the tool show you what is happening inside the system, or only what people reported?

In one of my early S/4HANA projects, we lost five weeks just trying to figure out why transports were stuck in QA. Nobody had a clear view. The tracking tool was tracking tasks, not the work.

Over the years I have learned that the real problem is usually deeper than a late task: a lack of tracking that can see the system. If the tool cannot show what is happening across your system landscape, you are managing on assumptions.

Four properties separate tools that prevent delays from tools that document them afterwards.

Integration with the SAP system. A tool that reads the system knows the real state of transports, test runs and approvals. A tool fed by manual updates knows what people reported, often a week late.

Coverage of the late phases. Most tools cope with the build. They fall apart in testing, cutover and hypercare, which is where delays compound. If the tool cannot track mock runs and cutover tasks, it abandons you at the riskiest point.

Dependency visibility. Data migration feeds UAT. Cutover sequencing depends on transport order. A tool that shows task completion but not dependency chains cannot show what one delay does to three other workstreams.

Adoption. The most capable tool fails if half the team logs status somewhere else. Adoption comes from ease of use, from showing people information they need, and from leadership insisting on it.

1. SAP Cloud ALM

SAP Cloud ALM is SAP's application lifecycle management tool for cloud and hybrid landscapes. There is no licence for it. Customers with a cloud subscription that includes Enterprise Support, cloud editions (RISE and GROW contracts do), or with on-premise Enterprise Support, can provision one tenant per customer number. Standard Support customers are not entitled unless they also hold such a cloud subscription.

What it does well: it structures the project against SAP Activate phases and reads status from the system, including test execution and transports. I implemented S/4HANA for a manufacturing company using Cloud ALM to track the whole 10-month project. During Realize, our data migration ran into issues. The tool flagged the delay and calculated the impact on dependent tasks.

Where it falls short: it needs proper connectivity to your systems. When the Basis team is stretched, that connection does not happen at the start of Prepare. By the time it is configured, the project has lived in a spreadsheet for two months and nobody wants to migrate the history.

For any new S/4HANA cloud or RISE programme, start here. The licence is not the cost. Basis and configuration effort is.

2. Jira with a portfolio add-on

Jira is the default issue tracker in many enterprise IT departments. Portfolio add-ons such as BigPicture add Gantt charts, dependencies and resource views. Atlassian's AI, now branded Rovo, is included on every paid Jira plan with a monthly credit allowance, and summarises tickets and drafts status updates.

It works when the organisation already runs Jira for development and support. If the systems integrator sets up Cloud ALM while the client's IT team runs everything else in Jira, you end up with parallel systems. Jira shows what IT is doing. Cloud ALM shows what SAP is doing. Nobody has a single view.

The risk is integration. Jira has no native understanding of transports or Activate phases. Without a configured integration to the SAP landscape, you can track tasks but not the system.

3. Microsoft Planner and Project

Many PMOs grew up on Microsoft Project, and it remains familiar to finance and operations leaders. The product line changed in 2026. Microsoft retired Project Online on 30 September 2026 and stopped new sales of Planner and Project Plan 5. Customers who need desktop scheduling are pointed to Planner and Project Plan 3, which lists at $30 per user per month. Microsoft 365 Copilot, an add-on licence, drafts status updates and steering packs from the plan and related documents.

There is no deep standard link from Microsoft's tools to SAP. Getting transport or test status into the plan means a third-party connector or your own integration. For a single-entity S/4HANA finance and procurement rollout where the client's PMO already owns the licences, that can be enough. For multi-entity programmes with heavy transport volumes and cross-system dependencies, it is not deep enough.

If your PMO ran on Project Online, check that the migration to its replacement is finished before the programme baseline is set.

4. SAP Solution Manager

SAP Solution Manager 7.2 is the on-premise predecessor to Cloud ALM, included with on-premise maintenance agreements. For complex on-premise landscapes it still goes deepest: transport monitoring, process documentation, native test management and change control. On a recent project, Solution Manager alerted us to conflicting transports before they were imported to quality testing. That prevented a configuration conflict that would have taken days to untangle.

The trade-off is set-up effort. A proper configuration takes weeks of Basis and Solution Manager specialist time. Teams that skip the investment end up using it for transport monitoring only, which wastes most of its capability.

Mainstream maintenance ends at the end of 2027. Extended maintenance runs to 2030 for selected functions, for customers who take Business Suite 7 extended maintenance. SAP's own guidance is to move to Cloud ALM before 2028. For a new programme, only choose Solution Manager if you already run it well and the programme ends before that window closes.

1. Sep 2026Microsoft Project Online retiredPlanner and Project Plan 3 is the route for desktop scheduling
2. End 2027Solution Manager mainstream maintenance endsSAP's guidance is to complete the move to Cloud ALM before 2028
3. End 2030Solution Manager extended maintenance endsSelected functions only, with Business Suite 7 extended maintenance

Source: Microsoft Tech Community and SAP Support Portal, checked October 2026

The table summarises the four options as of October 2026.

Tool	Best for	SAP integration	Set-up effort	Licensing
SAP Cloud ALM	New S/4HANA programmes, RISE and GROW	Native	Medium	No licence fee with Enterprise Support or a cloud subscription
Jira with portfolio add-on	Organisations already on Jira	Via third-party or custom integration	Medium to high	Per-user subscription plus add-on and integration effort
Microsoft Planner and Project	Mid-market PMOs already on Microsoft	Via third-party or custom integration	Low to medium	Planner and Project Plan 3 lists at $30 per user per month
SAP Solution Manager 7.2	Complex on-premise landscapes already using it	Native, deep	High	Included with on-premise maintenance; mainstream maintenance ends 2027

All four tools now have an AI layer. SAP has added Joule to Cloud ALM, including agents for operations that summarise alerts and build monitoring dashboards from plain-language prompts. Microsoft 365 Copilot drafts narrative updates from a plan. Atlassian's Rovo summarises Jira threads and drafts Confluence pages.

What AI does not change is integration depth. It speeds up writing status from whatever data the tool holds. If the tool is fed from spreadsheets, AI writes faster summaries of spreadsheets. Build the integration first. The AI layer is the easy part to add later.

Run these questions before you commit to a tool.

1. Does the tool read transport, test and approval status from the SAP system, or rely on people typing it in?
2. Does it track mock migrations, cutover tasks and hypercare tickets as well as the build?
3. Can it show dependency chains across workstreams?
4. Who owns the integration between the tool and the SAP landscape, by name?
5. What is the real set-up cost? The licence is often the smallest number; Basis and integration time is the real investment.
6. Will the whole team use it, including the business leads?
7. If two tools must coexist, which one is the source of truth for system state, and which for the business schedule?

For how tracking feeds governance, see my guide to getting SAP projects back on track.

I notice that project teams sometimes ignore their tracking tool because it is too complicated, and keep separate spreadsheets instead. By the time leadership notices, the system configuration is three weeks behind schedule.

Tools create visibility. They do not create the habit of acting on it. That needs a steering committee that treats a red flag as a reason to act, not a reason to add a mitigation comment and move on.

What is SAP Cloud ALM and is it free?

SAP Cloud ALM is SAP's application lifecycle management tool for implementing and running SAP systems. There is no separate licence. Customers with SAP Enterprise Support or Product Support for Large Enterprises can provision one tenant per customer number. So can customers whose cloud subscription includes Enterprise Support, cloud editions, which covers RISE and GROW. The real cost is the effort to connect and configure it.

Does Jira work for SAP project tracking?

For tasks and issues, yes. It does not natively understand transports, SAP Activate phases or SAP dependencies. With a portfolio add-on and a configured integration it can manage programme schedules and pull some SAP data. Use it when the organisation already runs Jira for everything else. For a dedicated SAP programme with no existing Jira investment, Cloud ALM is the more efficient start.

What replaced Microsoft Project Online?

Microsoft retired Project Online on 30 September 2026. For customers who need desktop scheduling, Microsoft points to Planner and Project Plan 3, which includes the Project desktop application. Planner and Project Plan 5 is no longer sold to new customers. If your PMO tracked an SAP programme in Project Online, confirm the migration is complete and the history has moved before you rely on the new plan.

When should you use SAP Solution Manager instead of Cloud ALM?

When three things are true. You run a complex on-premise ECC or S/4HANA landscape. You already have Solution Manager configured and a team that knows it. And the programme will finish before mainstream maintenance ends in 2027. During an ECC to S/4HANA move, the two can run in parallel: Solution Manager for the old landscape, Cloud ALM for the new one. SAP recommends completing the move to Cloud ALM before 2028.

How do tracking tools reduce delays on SAP programmes?

By showing problems before the weekly status meeting does. A transport stuck in an approval queue does not appear in a manual report until someone notices. A tool reading the system shows it the same day. On the early project above, a tool reading real transport status would have shown the blockage before it cost five weeks. The gain is biggest in Realize and Deploy, when transport volumes are high and testing runs in parallel.

Can you use more than one tracking tool on the same SAP programme?

You can, and it usually causes trouble: two tools show different status for the same workstream and every escalation starts with an argument about which is right. If you must run two, give each a defined job. System state (transports, tests) lives in Cloud ALM or Solution Manager. The business schedule can live in Jira or Planner if that is the client's standard. Synchronise them at set intervals.