The go-live is behind you. Teams are using the ERP every day, and the project is officially “done.” That is precisely when costs start to drift. Unused licenses, deployed modules that were never adopted, over-provisioned cloud infrastructure, maintenance contracts renewed without review — the ERP budget quietly grows while attention moves to other priorities.
This guide offers a four-step method to regain control: audit actual usage, rationalize licenses and modules, optimize infrastructure, and establish sustainable FinOps governance. The goal is not to cut blindly, but to align costs with the value actually consumed.
The Post Go-Live Paradox: Costs That Rise When the Project Is “Done”
The project phase keeps attention focused on functional scope, timelines, and integration budgets. Once the ERP is in production, that budget vigilance relaxes. Recurring costs — licenses, maintenance, infrastructure — shift into automatic-renewal mode with no critical review.
Purchased Licenses That Were Never Activated (Shelfware)
Shelfware remains a massive problem across organizations. According to the Flexera 2025 State of ITAM Report, 93% of organizations report paying for software that sits unused on the shelf, and 30% of respondents estimate that at least one-fifth of their software budget is tied to shelfware.
In an ERP context, the pattern is familiar: licenses are sized for the peak usage expected at deployment time. Six months later, some users have changed roles, others never completed their training, and entire teams continue to work with their old tools in parallel.
Modules Deployed Then Abandoned by Business Teams
A CRM module activated but never fed with data. A purchase approval workflow bypassed by email. A supplier portal deployed that no supplier has ever registered on. These investments represent not only a direct license cost, but also a maintenance overhead: every active module must be updated, tested through version upgrades, and supported by the IT team.
Over-Provisioned Cloud Infrastructure (Right-Sizing Ignored)
Cloud ERP environments are often sized to absorb peak loads during migration and the first months of production. Once a steady cruising pace is reached, nobody goes back to adjust the resources. According to the FinOps Foundation State of FinOps 2026 report, organizations waste an average of 25–35% of their cloud spend on idle resources, over-provisioned instances, and orphaned storage. Right-sizing alone can generate 15–25% savings on infrastructure costs.
Step 1: Audit Actual ERP Usage
Before cutting anything, measure. A factual usage audit is the foundation of every rationalization decision.
Measure Active Connections vs. Paid Licenses
Extract from the ERP the complete list of user accounts, then cross-reference them against login logs for the past 90 days. The categories to identify are:
- Daily active users: logging in and transacting every business day.
- Occasional users: connecting less than once a week.
- Dormant accounts: no login in more than 60 days.
- Ghost accounts: users who have left the organization but whose accounts remain active.
Most ERP platforms (SAP, Oracle, Microsoft Dynamics 365, Sage Intacct, Access Group) include native usage reports or integrate with third-party Software Asset Management (SAM) tools.
Map Which Modules Are Actually Used
Beyond logins, analyze business transactions by module. A user may connect to the accounting module every day without ever using the procurement module for which they hold a license. Key indicators to track:
- Number of transactions per module per month.
- Number of reports generated by module.
- Active versus configured integration flows.
- Advanced features enabled but never used (capacity planning, project management, integrated CRM).
Identify Orphaned Customizations
Custom developments built during the implementation project each carry a recurring maintenance cost. With every version upgrade, each customization must be tested, adapted, and revalidated. Identify those that no longer have a business sponsor: the owner who requested them has changed roles, the process has evolved, or the feature is now standard in newer versions of the ERP.
Step 2: Rationalize Licenses and Modules
The audit produces data. This step turns that data into concrete cost-reduction actions.
Reclassify Users (Full vs. Limited vs. Read-Only)
Most ERP vendors offer several license tiers, from the most comprehensive (named user with full transactional access) to the lightest (read-only access). Reclassifying a user who only consults dashboards from a “Professional” to a “Team Member” or “Read-Only” profile can cut the unit cost by a factor of three to five depending on the vendor.
The process is as follows:
- Cross-reference the current license profile with actual usage measured in Step 1.
- Identify users whose transaction volume does not justify their license tier.
- Propose reclassifications to business owners, backed by usage data.
- Apply the change after sign-off and measure the saving.
Deactivate or Return Unused Modules
An active but unused module costs in three ways: direct license, technical maintenance, and cognitive load on the support team. The decision to deactivate must be documented and reversible — but it must be made.
For each module identified as underused, ask three questions:
- Is this module used by at least one critical business process?
- Would removing it affect other active modules (technical dependencies)?
- Does the business team have a concrete adoption plan for the next six months?
If all three answers are no, the module should be deactivate and the license returned to the vendor or reserved for the next renewal cycle.
Renegotiate the Vendor Contract Armed With Usage Data
Maintenance renewal is a leverage point that organizations too often overlook. Annual maintenance fees typically represent 18–22% of the initial license cost for on-premise ERP systems — a recurring line item that compounds year after year.
Arriving at the negotiating table with a documented usage audit changes the dynamic. You can request:
- A reduction in the number of covered licenses.
- Maintenance scope adjusted to only the modules in active use.
- Exit terms or a freeze on modules awaiting adoption.
- Contract alignment to actual usage profiles rather than historical profiles.
Step 3: Optimize Infrastructure (Cloud and On-Premise)
Infrastructure costs are an often-untapped savings lever because they fall under a different team than the one managing licenses.
Right-Size Cloud Instances (CPU, RAM, Storage)
Right-sizing means matching allocated resources (CPU, memory, storage) to actual consumption measured over a representative period — ideally 30–90 days that includes month-end peaks.
Concrete steps:
- Enable detailed monitoring on ERP instances (CloudWatch for AWS, Azure Monitor, or your hosting provider’s native tools).
- Identify instances with average CPU utilization below 20% and memory usage below 40%.
- Propose downsizing to the next smaller instance type, or moving to reserved instances for predictable workloads.
- Separate development and test environments — which can be shut down outside business hours — from production.
Archive Old Data to Reduce Volume
ERP databases grow mechanically: historical transactions, logs, attachments, document versions. Beyond three to five years, the operational value of this data drops sharply, but its storage cost and impact on ERP performance remain constant.
Put a structured archiving policy in place:
- Define retention rules by data type (regulatory vs. operational).
- Archive data beyond the active retention period to lower-cost storage (cold storage, object storage).
- Verify that archived data remains queryable for compliance needs (tax audits, statutory reporting, external audits).
Plan Version Upgrades (The Cost of Technical Debt)
Deferring ERP version upgrades appears to save money in the short term. In reality, every skipped version accumulates technical debt: customizations become more complex to migrate, vendor support degrades (or ceases), and security vulnerabilities compound.
The cost of a three-year deferred upgrade is typically two to three times higher than the cost of regular incremental upgrades. Budget a dedicated annual line item for version upgrades and include it in your forward-looking TCO model.
Step 4: Establish Sustainable ERP FinOps Governance
The first three steps generate one-off savings. Without governance, costs drift again within 12–18 months.
Monthly Cost/Usage Dashboard
Build a summary dashboard that cross-references ERP costs (licenses, maintenance, infrastructure, internal support) with usage indicators (active users, transactions by module, cloud consumption). Share it monthly with the CIO and CFO.
Key metrics to track:
- Cost per active user (not per purchased license).
- Utilization rate by module (actual transactions / contractual capacity).
- Infrastructure cost per business transaction.
- Ratio of active customizations to total customizations.
Quarterly License Review With Business Teams
Each quarter, bring together business owners, the CIO, and procurement for a 90-minute review covering:
- Gap between licenses paid and licenses used.
- Modules to deactivate or reactivate.
- New feature requests versus underused existing modules.
- Preparation for the next vendor renewal.
This review transforms ERP license management from an annual burden into a continuous, shared steering exercise.
Rolling 3-Year ERP Budget Model
The ERP budget cannot be a static annual exercise. Build a rolling three-year cost model that incorporates:
- Expected changes in user headcount (growth, acquisitions, restructuring).
- Version upgrade calendar and estimated costs.
- Vendor contract renewals and renegotiation windows.
- Functional extension projects and their license impact.
- Infrastructure cost evolution (cloud indexation, potential migrations).
This model lets the CFO provision accurately and the CIO negotiate from a position of strength.
Summary Matrix: 8 Levers and Their Savings Potential
| Lever | Effort | Potential Saving | Timeline |
|---|---|---|---|
| License profile reclassification | Low | 10–25% on license spend | 30 days |
| Deactivation of unused modules | Medium | 5–15% on license spend | 60 days |
| Removal of dormant/ghost accounts | Low | 5–10% on license spend | 15 days |
| Vendor maintenance contract renegotiation | Medium | 10–20% on maintenance spend | 3–6 months (at renewal) |
| Cloud right-sizing | Medium | 15–25% on infrastructure spend | 30–60 days |
| Historical data archiving | Medium | 5–15% on storage spend | 3–6 months |
| Removal of orphaned customizations | High | Reduced upgrade cost | 6–12 months |
| Quarterly FinOps governance | Low (recurring) | Prevents cost drift (cumulative effect) | Ongoing |
Quick wins — license reclassification, removal of dormant accounts, initial cloud adjustments — can be completed within 30 days and produce visible savings in the following quarter. Structural actions — vendor renegotiation, customization removal, FinOps governance — require 6–12 months but lock in gains over the long term.
To go further on ERP financial management, see our guide on total cost of ownership and hidden ERP costs and our ERP license audit methodology. If you are building post-deployment governance, our article on ERP centers of excellence and performance KPIs complements the FinOps approach described here.
