TBM Taxonomy 5.0 vs 4.x: a layer-by-layer change log for migrating your model

In brief

Moving from TBM Taxonomy 4.x to 5.0.1 means remapping every layer. A practitioner change log: what each change breaks, a before/after table and a sequence.

Steve Elliott

Steve Elliott · · 7 min read


On this page
  1. What changed between Taxonomy 4.x and 5.0.1?
  2. Which cost pool changes break your general ledger mapping?
  3. What happens to the Platform and Output towers?
  4. Where did applications go, and what does the Consumer layer change?
  5. How does the migration reach your enterprise architecture repository?
  6. In what order should you migrate?
  7. Sources

Moving a TBM model from Taxonomy 4.x to 5.0.1 means remapping every layer, not renaming a few. Labor and cloud cost pools change shape, the Platform and Output towers are retired, applications leave the solutions layer, and the Business layer becomes a Consumer layer built around value streams and products.

The TBM Council's migration guide and its 5.0.1 tables don't agree on every sub-tower name. This change log works from the 5.0.1 tables, notes where the guide differs, and covers a step that is easy to miss: the copy of the taxonomy that lives in your enterprise architecture repository.

What changed between Taxonomy 4.x and 5.0.1?

The Council released 4.0 in December 2020 and 4.1 on November 4, 2023. Version 5.0 followed on June 6, 2025, and 5.0.1, the current version, on July 18, 2025. The migration guide, published July 16, 2025, covers moves from 4.0 or 4.1 to 5.0. On the taxonomy page, changed towers and sub-towers carry a note on what changed from version 4.1. In our view, those notes are the most precise change log available.

Layer4.x5.0.1Remapping
Cost poolsInternal Labor and External LaborStaffing, with Internal Labor and Staff Augmentation sub-poolsExternal Labor and contractors move one-to-one to Staff Augmentation
Cost poolsOutside Services carried public cloud and managed servicesCloud Services pool; Managed Services as a sub-pool across pools; Outside Services keeps ConsultingOne-to-many split
Cost poolsSoftwareSoftware & SaaS, with a SaaS sub-poolSaaS stays out of Cloud Services
Cost poolsLegacy expense sub-poolsOther Operating sub-poolMany-to-one
TowersPlatformRetired; sub-towers moved to Application and the new Data towerOne-to-many
TowersOutputRetired; Central Print moved to DeliveryOne-to-one
TowersSecurity & ComplianceSecurity, and Risk & ComplianceOne-to-many
TowersNoneData and Smart DevicesNew
TowersIT Management & Strategic PlanningTech ManagementRename
SolutionsApplication solutions; Platform solution typeApplications removed; Platform type retired; Artificial Intelligence type addedApplication becomes a service or product plus Application Hosting
ConsumersBusiness layerConsumer layer: business functions, value streams, partners and internal consumers, external consumersBusiness unit maps to business unit, product or value stream

Which cost pool changes break your general ledger mapping?

The Council's cost pool guidance says mapping is done at the sub-pool level, so the new sub-pools matter as much as the new pools. Expect to revisit your general ledger mapping at the account and vendor level.

  • Staffing. One pool replaces Internal and External Labor. The 5.0.1 table shows Internal Labor and Staff Augmentation sub-pools, each with a capital counterpart. The guide maps External Labor and contractors to Staffing > Staff Augmentation. Rules and reports keyed on External Labor break. In our view, an internal-to-external labor ratio still works, but it now has to be built from sub-pools.
  • Cloud Services. Public cloud gets its own top-level pool. The guide maps 4.1 Outside Services to Cloud Services or Managed Services, in effect a one-to-many split. Outside Services survives in 5.0.1 with Consulting and Managed Services sub-pools, so an account that mixed cloud invoices with consulting fees needs splitting; we would split it by vendor.
  • Software & SaaS. SaaS sits as a sub-pool here, not under Cloud Services. The Council's 2024 draft described this as separating SaaS from cloud. A provider that sells both infrastructure and SaaS on one contract needs a rule for each.
  • Catch-alls. Other Operating now appears under almost every pool, and Managed Services under five. The guide collapses legacy expense sub-pools into Other Operating and also advises reducing reliance on that catch-all in your data pipelines.
  • Renames. Data Center Facilities replaces Facilities & Power, and Misc Costs replaces Other.

What happens to the Platform and Output towers?

Both are retired. The Platform tower's sub-towers move to Application and to a new Data tower. Database moves from Platform to Data. Big Data merges into Data Operations, and Data Management moves across from the old IT management tower. Output disappears and its Central Print sub-tower moves to Delivery.

The other tower changes, from the 5.0.1 notes:

  • Security split. Security & Compliance becomes Security, and Risk & Compliance. The Compliance sub-tower is retired; the Council suggests a sub-tower under Risk & Compliance instead. Identity & Access Governance is a new sub-tower under Risk & Compliance.
  • Smart Devices. A new tower with Industrial & Control Systems and Intelligent Devices sub-towers.
  • Consolidations. Unix volumes go to Servers. Transport goes to WAN, and the old LAN/WAN sub-tower splits in two. Business Software and End User Software consolidate into Licensing under Application.
  • New sub-towers. AI Compute, AI Storage, AI Network and AI Models, plus Quantum and Blockchain & Tokenization.
  • A level above towers. Technology Resource Domains, new in 5.0, organize related towers; the guide says they support executive-level views.

The practice lead guide notes that pool data does not flow into towers on its own. The Council's CFO guide calls towers the layer where benchmarking becomes possible, so these changes break benchmarks and trend lines. The Application tower absorbs container orchestration and other sub-towers that used to sit in Platform, so a year-over-year chart will show a jump that is only a reclassification. In our view, restate at least the prior year in 5.0.1 terms before showing any tower trend to a CFO.

The discrepancies matter for your crosswalk. The migration guide lists ML Engineering and Model Hosting as new sub-towers under Data, and IoT Devices and Operational Technology under Smart Devices. The 5.0.1 tables list AI Models under Application and use different Smart Devices names. The guide's table also sends Platform to Smart Devices, and one example maps External Labor to "Staffing > Contractor". It was published two days before 5.0.1 and is still scoped to 5.0. We would build the crosswalk from the 5.0.1 data tables and treat the guide's examples as illustrative.

Where did applications go, and what does the Consumer layer change?

The taxonomy page says plainly that "Applications have been purposefully removed from the Solutions taxonomy." They are now treated within the towers. The guide maps a 4.1 application solution to a service or product plus Application Hosting. The Platform solution type is also retired, with its elements redistributed under Delivery and Infrastructure, and Artificial Intelligence is added as a solution type. The guide flags any filter that uses Platform or Application as a solution type, so expect dashboards to break here.

In our view, this is the biggest conceptual shift for an architect. An application stops being something the business consumes and becomes a resource that supports what the business consumes.

At the top, the Business layer is renamed the Consumer layer. The 5.0.1 page lists business functions, business value streams, partners and internal consumers, and external consumers. The guide adds products, portfolios and digital services, and maps a 4.1 business unit to a business unit, product or value stream. What changes is that showback can now land on a value stream or product, which means someone has to own that list.

How does the migration reach your enterprise architecture repository?

Your TBM model may not be the only copy of the taxonomy. Some EA repositories carry TBM categories as reference data linked to applications.

SAP LeanIX is the clearest documented case we found. On November 17, 2025, it updated its tech category reference catalog from TBM Taxonomy version 4 to 5.0.1. Its release notes describe the changes as minor, for example moving Decision Intelligence & Automation under a new Artificial Intelligence category. Existing fact sheets were not updated automatically. Admins have to rename some categories and create and link new ones, and workspaces where nobody acts stay on version 4.

On the ServiceNow side, a 2023 Council event page says its Standards Committee had built TBM integration models including ServiceNow's Common Service Data Model for the CMDB. That predates 5.0, and we found no published 5.0.1 mapping to it.

The Council's November 17, 2026 repositioning raises the stakes. It positions the TBM Framework and Taxonomy as "contextual and semantic layers for Agentic TBM" across SAP, LeanIX and ServiceNow. In our view, that makes version control across repositories a governance question. If the EA repository is on version 4 and the cost model is on 5.0.1, people and agents reading each get different answers about the same application.

In what order should you migrate?

This sequence draws on the guide's eight steps, adds the EA repository, and works from the ledger up.

  1. Inventory. List allocation rules, ETL logic, dashboards and the people who depend on them. Add every system holding a copy of the taxonomy: the EA repository, the CMDB and any planning model.
  2. Build the crosswalk. Map 4.1 objects to 5.0.1 from the data tables, tag each with version metadata, and mark each mapping one-to-one, one-to-many or many-to-one. The one-to-many rows need a rule or a percentage.
  3. Remap cost pools. Staffing, the Cloud Services split out of Outside Services, and SaaS.
  4. Remap towers. Redistribute Platform, stand up Data and Smart Devices, split Security, then restate the prior year.
  5. Remap solutions and consumers. Move applications into the Application tower, rebuild services or products on top, and decide which value streams and products receive cost.
  6. Update the EA repository in the same release. Rename and relink tech categories so architecture and cost reference one version.
  7. Run both models in parallel. The guide recommends at least one to two full reporting cycles. Then freeze and archive the 4.1 assets and cut over.

The point of the Consumer layer is to tie technology cost to the products and value streams the business runs on, so the migration works best when the cost model, the architecture repository and the portfolio describe one operating model.

Sources

Frequently asked questions

Is TBM Taxonomy 5.0.1 different from 5.0?

Version 5.0.1 is the current release. The TBM Council released it on July 18, 2025, six weeks after 5.0 shipped on June 6. The Council publishes the 5.0.1 whitepaper and data tables as the reference. Its migration guide was written against 5.0, and some sub-tower names in its examples differ from the 5.0.1 tables, so build mappings from the 5.0.1 tables.

How long should we run 4.1 and 5.0 in parallel?

The TBM Council's migration guide recommends running the 4.1 and 5.0 models side by side for at least one to two full reporting cycles, monthly or quarterly. The aim is to compare outputs and explain differences before cutover. After that, the guide advises freezing and archiving the 4.1 assets and moving reporting to the new version.

Where do SaaS costs go in TBM Taxonomy 5.0?

SaaS sits in the Software & SaaS cost pool, as its own sub-pool, not in the new Cloud Services pool. Cloud Services covers public cloud provider spend. A vendor that sells both infrastructure services and SaaS needs a separate mapping rule for each. In our view, the split is best made at the vendor or contract level.

Does SAP LeanIX support TBM Taxonomy 5.0.1?

Yes. SAP LeanIX updated its tech category reference catalog from TBM Taxonomy version 4 to 5.0.1 on November 17, 2025. Existing fact sheets in customer workspaces were not changed automatically. Admins need to rename some categories and create and link new ones. Workspaces where nobody takes those steps stay on version 4.

Free playbooks

In-depth guides for product and operations leaders.

Browse the playbooks
Steve Elliott

Steve Elliott

Published November 22, 2026

More on TBM & IT Financial Management

Cost pools, towers, showback, unit cost.