SAS ABM is retiring. Your costing knowledge does not have to.
In short. SAS announced end of life for its Activity-Based Management product, with support ending in 2025 as widely reported. Teams that ran ABM for years hold something valuable: a mature activity model of their business. Migration done well preserves that knowledge and upgrades the machinery to time-driven costing. Done badly, it re-implements 2005. Here is the calm path.
A note on tone: SAS ABM served its users for a long time, and many of the best-built ABC models we have ever seen live in it. Nothing here disparages the product; the facts of its lifecycle are stated as announced by the vendor, and users should verify current details with SAS.
What actually ends when a product like ABM ends?
Less than the anxiety suggests, and more than the calendar shows.
What ends is the software: the engine, the interfaces, the vendor support that made an audit comfortable. SAS announced end of life for ABM, with the end of support in September 2025 widely reported. CONFIRM: exact lifecycle wording and date from SAS's published notice at time of publication
What does not end is the asset your team built inside it: the activity dictionary, the driver relationships, the account mappings, the years of institutional agreement about how the business consumes cost. That asset took years to negotiate. It fits in a spreadsheet. It is portable.
The software is mortal. The model is not, unless you leave it behind.
Should you rebuild the same model in a new tool?
This is the fork in the road, and it deserves a real decision rather than a default.
Classic ABM models are driver-and-percentage machines: activities receive cost from the ledger, drivers push it onwards. They answer well until the maintenance bill arrives: re-surveys, driver updates, module-by-module care. Many ABM installations quietly froze years ago for exactly this reason.
Time-driven ABC was developed to fix that maintenance problem. Two mechanisms replace the driver web. Capacity cost rates: cost of capacity supplied divided by practical capacity, per resource pool. Time equations: each transaction costed by a formula of its own characteristics. The result is a model that updates from operational data instead of interviews.
If your ABM model was mainly a reporting allocator, a like-for-like rebuild may serve. If leadership is asking customer, product and channel profitability questions, migration is your once-a-decade chance to answer them properly.
What does the modern stack look like?
Data in
The extracts you already produce. Transaction logs are welcome at volume: one of our production models runs on a 525,000-row shipment dataset.
Capacity model
Cost pools with practical capacity and a rate each. This is where most of your ABM activity dictionary translates directly; activities become pools or equation terms.
Time equations
The replacement for the driver web. A few dozen equations typically replace hundreds of driver assignments, which is what makes the model maintainable by a finance team rather than a support contract.
Decision surfaces
Cost-to-serve, whale curves, capacity utilisation and scenarios, refreshed on your reporting rhythm. In our stack this is CostCtrl, run by your team after handover.
How does the migration run?
Harvest the model, not the software
Export the activity dictionary, driver definitions, account mappings and the last agreed results. This is the knowledge audit, and it is urgent while the people who built the model are still in the room.
Translate to capacity and time
Activities regroup into cost pools with practical capacities; driver logic becomes time equations where causality is time-shaped, direct assignment where it is not. Expect the new model to be structurally smaller. CONFIRM: typical reduction in model objects C&P is willing to state from engagements
Parallel run one closed period
Old results beside new results, differences explained line by line. ABM veterans make this step fast because they already know where the bodies are buried; the parallel run gives them the forum to say so.
Cut over, hand over, retire with honours
The new model goes live with your team operating it. Archive the ABM outputs for audit continuity, and document the mapping from old activities to new pools so history remains readable.
WHAT MIGRATES, WHAT RETIRES
DRIVER WEB TO TIME EQUATIONS
How do the approaches compare?
| Classic ABM (as commonly implemented) | Modern TDABC stack (CostCtrl) | |
|---|---|---|
| Modelling approach | Activity dictionary with driver-based assignment | Capacity cost rates and time equations |
| Time equations | Not native; time captured via surveys and driver proxies | Native; core costing mechanism |
| Data volume | Periodic, aggregated driver tables | Transaction-level feeds, hundreds of thousands of rows |
| Implementation time | Historically multi-quarter implementations | First working model in weeks CONFIRM: committed range |
| Pricing model | Legacy licence and support (now per vendor lifecycle terms) | Subscription plus expert build; client team operates CONFIRM: current commercial wording |
Fair questions.
- When exactly does SAS ABM support end?
- SAS announced end of life for ABM, with end of support in September 2025 widely reported. Verify the current, exact terms for your licence directly with SAS; contractual arrangements differ. Our guidance holds regardless of the precise date: harvest the model while the team that understands it is available.
- Can our ABM activity model be imported automatically?
- The dictionary and mappings export cleanly and accelerate step 2 substantially. Full automation is neither possible nor desirable: translation to capacity and time is a modelling decision, and it is where the upgrade happens.
- Is TDABC accepted by auditors and regulators?
- The method is published, peer-reviewed and transparent by construction: every figure traces to a rate and an equation. We co-authored a peer-reviewed TDABC study in healthcare, and the parallel-run period gives your auditors a documented bridge from the old model.
- How long does a migration take?
- The knowledge harvest takes days; the first working model, weeks; the parallel run, one closed period. CONFIRM: typical end-to-end duration from comparable engagements The deadline pressure is real but the project is smaller than the one that built ABM originally.
- We also run other legacy costing tools. Same story?
- Broadly, yes. SAP PCM is in maintenance mode and Oracle HPCM users face their own cloud transition; we maintain a separate page for each. The pattern repeats: the generation of allocation engines is retiring together, and the modelling question is open for all of them.
Your ABM model deserves a second life.
Bring your activity dictionary to a 30-minute call and we will tell you what translates, what simplifies and what it would take.