When a company conducts its carbon footprint assessment, it accounts for scope 1 emissions (direct combustion), scope 2 (purchased energy), and scope 3 (value chain). What few IT departments systematically measure: the footprint of their own information system. Yet the ERP, sitting at the centre of every operational flow, consumes servers, storage, bandwidth, and energy around the clock. It is typically the single largest digital asset in the company in terms of resource consumption.
This article explores concrete levers to reduce the environmental impact of your ERP, within the regulatory framework taking shape across Europe and beyond.
ERP: The Blind Spot of IT Carbon Accounting
Why ERP Weighs Heavily in Corporate Digital Consumption
According to the IEA’s Electricity 2024 report, data centres consumed roughly 415 TWh globally in 2023 — a figure expected to more than double by 2026 as AI workloads scale. The European Environment Agency estimates that digital technologies account for 4–8% of EU electricity consumption, with data centres and cloud infrastructure representing the fastest-growing share.
ERP systems are not called out individually in these studies, but their contribution is real. A SAP S/4HANA or Microsoft Dynamics 365 instance hosted on-premise runs servers continuously, manages large databases, executes nightly batch jobs, and synchronises dozens of real-time interfaces. In SaaS mode, the footprint is not eliminated — it is simply outsourced to the vendor’s or hyperscaler’s data centres.
Digital sobriety is therefore not just about laptops and smartphones. It reaches into business applications — and above all, into the ERP.
What the EU’s Digital Compass and Ecodesign Frameworks Say
The European Commission’s Digital Compass sets targets for energy-efficient and sustainable digital infrastructure by 2030. In parallel, the EU Taxonomy for sustainable activities and the upcoming Green Claims Directive are pushing companies to substantiate environmental assertions about their IT assets.
While frameworks like France’s RGESN (General Reference for the Ecodesign of Digital Services) are nationally scoped, the methodology is directly applicable to any business information system. Criteria covering server resource reduction, algorithm optimisation, and hosting choices are universally relevant for ERP teams.
CSRD and IT Footprint Reporting: What Is Required from 2026
Since fiscal year 2025 (reports published in 2026), companies with more than 250 employees exceeding two of three CSRD thresholds (€50M turnover, €25M balance sheet, 250 staff) must publish a sustainability report compliant with ESRS standards. The E1 standard on climate change requires coverage of scope 3 emissions, including those linked to purchased digital services.
In practice: emissions generated by your SaaS ERP fall into your upstream scope 3 carbon footprint. If your ERP is on-premise, the energy consumed by your servers falls under scope 2. In both cases, ignoring your ERP’s footprint has become a regulatory blind spot.
Sobriety vs. Efficiency: Two Distinct Strategies
Before going further, an important distinction. Digital efficiency means doing the same things with fewer resources (optimising queries, compressing data). Digital sobriety means questioning whether the features and processes are necessary in the first place: do we need this module? This nightly batch run? This real-time interface?
Both approaches are complementary, but sobriety typically delivers larger gains — and immediate cost savings.
Cloud vs. On-Premise: The Real Carbon Comparison
Debunking “The Cloud Is Greener”
The assumption that moving to SaaS automatically reduces your IT carbon footprint is dangerously oversimplified. SaaS externalises the footprint; it does not eliminate it. Pooling resources at a hyperscaler can improve server utilisation rates and thus efficiency — but this depends entirely on the vendor, the data centre, and its energy mix.
A SaaS ERP hosted in a data centre running on 80% coal-fired electricity has a worse carbon profile than an on-premise ERP in a European server room supplied by a low-carbon grid (several European countries benefit from high proportions of nuclear or renewable generation).
Comparing PUE and Energy Mix
The PUE (Power Usage Effectiveness) measures a data centre’s energy efficiency: a PUE of 1.0 is theoretically perfect (all energy goes to servers); a PUE of 2.0 means 50% of energy is lost to cooling and auxiliary equipment.
Published benchmarks from major operators:
- AWS: PUE between 1.07 and 1.15 depending on site (published in sustainability reports)
- OVHcloud: average PUE of 1.28, with 78% low-carbon energy across its European data centres (OVHcloud sustainability report)
- Scaleway: PUE between 1.15 and 1.30, with its DC5 data centre cooled by an adiabatic system without traditional air conditioning
A low PUE is a useful indicator, but insufficient on its own. You also need to examine the energy mix (renewable, nuclear, fossil) and the data centre’s location. A hyperscaler with a PUE of 1.10 running on coal can have a substantially higher carbon footprint than a European provider with a PUE of 1.25 and a 100% renewable mix.
When Sober On-Premise Beats Shared Cloud
For companies whose internal data centre is supplied by low-carbon electricity, whose server utilisation rates are high, and whose IT teams actively manage consumption, on-premise can prove greener than a SaaS deployment with an opaque hosting environment.
The key question to ask your vendor at contract renewal: which data centre hosts my data? What is its PUE and energy mix? Do you publish an audited sustainability report?
6 Levers for ERP Digital Sobriety
Lever 1: Rationalise Active Modules
An ERP deployed ten years ago often carries modules that were activated for internal projects no longer in use: a BI portal, a supplier gateway, a side project management tool. Every active module consumes memory, generates database indexes, and adds weight to backups.
An audit of active modules with business teams identifies what can be cleanly deactivated. The typical outcome: reduced database volume, faster backup times, and lower server load — with zero impact on users.
Lever 2: Archive and Purge Historical Data
ERP databases grow over time. Audit logs, legally archived accounting records, application logs, and test data in production eventually represent a large share of active storage. Active storage (NVMe SSD, high-performance SAN) consumes significantly more energy per gigabyte than cold or object storage.
A rigorous archiving strategy — with retention rules aligned to legal obligations (ten years for accounting records, five years for most commercial data) and a migration to cold storage — can reduce the active database by 30–50% in mature systems. The energy and financial savings are immediate.
Lever 3: Optimise Batch Jobs
Most ERPs launch nightly computation runs: stock updates, provisional closes, cost-of-goods calculations, satellite system synchronisations. These processes often run out of habit rather than genuine necessity.
A batch job audit identifies runs with no active consumer, jobs where frequency can be reduced (weekly instead of daily), and algorithms that can be optimised. Consolidating batch execution windows also lets you concentrate load during periods when grid electricity is less carbon-intensive (night hours in markets with high renewable penetration, for example).
Lever 4: Reduce Real-Time Interfaces and Data Flows
Integrations between the ERP and third-party systems (CRM, WMS, customer portal, e-commerce platforms) generate constant traffic. API calls every minute to synchronise data that rarely changes are a disproportionate source of network and server consumption relative to the value produced.
Shifting from continuous polling to event-driven synchronisation (triggered by an actual change) or batch-mode (hourly rather than per-minute) reduces network and server load — and also improves system resilience by eliminating tight coupling.
Lever 5: Extend Hardware Lifecycle
For on-premise deployments, server manufacturing accounts for a significant share of the lifecycle carbon footprint. According to IEA and industry lifecycle analysis data, manufacturing can represent 40–60% of a server’s total lifetime emissions.
Extending server life from three to five years directly reduces embodied carbon. Refurbishment practices (adding RAM, replacing drives) and regular utilisation-rate reviews allow hardware refresh cycles to be deferred without compromising performance.
Lever 6: Choose Vendors with Measurable ESG Commitments
At contract renewal or ERP selection, a vendor’s environmental policy has become a legitimate evaluation criterion. Key questions to ask:
- Does the vendor publish an annual ESG report with verified emissions data?
- Are commitments aligned with Science Based Targets (SBTi) validated objectives?
- Which data centres host your SaaS instance, and what are their certifications (ISO 14001, ISO 50001)?
- Does the vendor offer hosting options in data centres powered by renewable energy?
A vendor unable to answer these questions is exposing its customers to growing compliance risk as scope 3 reporting obligations tighten.
Measuring Your ERP’s Carbon Footprint: Where to Start
Available IT Measurement Tools
Three open-source initiatives worth knowing:
Boavizta is an international open-source project developing tools to measure the carbon footprint of servers and cloud infrastructure, accounting for both manufacturing (upstream impacts) and operational use. Its API calculates the footprint of cloud instances (AWS EC2, OVHcloud instances) using a documented, public methodology.
GreenIT-Analysis is a browser extension that measures the footprint of a web interface. Useful for assessing the browser-accessible portals and interfaces of your ERP.
Scaphandre is an open-source tool for monitoring server power consumption, compatible with Linux environments. It exports metrics to Prometheus and Grafana, making integration into an existing monitoring dashboard straightforward.
Scope 1/2/3 Perimeter for IT Systems
Mapped to IT following the GHG Protocol method:
- Scope 1: generators powering an internal data centre, refrigerants in cooling systems (off-grid).
- Scope 2: electricity consumed by servers, workstations, screens, and network equipment supplied by the public grid.
- Upstream Scope 3: manufacturing of servers, network hardware, workstations, and packaging. Purchased digital services (SaaS ERP, cloud services).
- Downstream Scope 3: emissions generated by remote users (broadband connection, home workstation) to access the ERP.
For an initial footprint assessment, focus on scope 2 (data centre electricity) and upstream scope 3 (SaaS services and hardware manufacturing). These are the largest and best-documented categories.
Define a Baseline and Annual KPIs
Without an initial measurement, it is impossible to assess progress. Useful indicators for an ERP:
- Annual electricity consumption of ERP-dedicated servers (in kWh, measured via smart PDUs)
- Volume of active database data (GB/TB), with monthly tracking
- Number of active batch jobs and their execution frequency
- Number of active interfaces and monthly API request volume
These four metrics allow you to build a baseline and measure the impact of sobriety actions year after year.
What ERP Vendors Are (and Are Not) Doing on Sustainability
SAP and Its “Clean Industries” Programme
SAP has committed to reaching carbon neutrality for its own emissions (scope 1 and 2) by 2030. Its “Clean Industries” programme aims to help customers measure and reduce their footprint via SAP Sustainability Control Tower and SAP Product Carbon Footprint Analytics — solutions that centralise emissions data and automate GHG Protocol reporting directly from the ERP.
What is concrete: SAP publishes an annual sustainability report with third-party verified emissions data. What to watch: scope 3 customer commitments remain less precise than scope 1 and 2 pledges.
Microsoft Dynamics, Oracle, and Odoo: Carbon Commitments and Transparency
Microsoft has made some of the most ambitious commitments in the sector: net zero by 2030, and carbon negative by 2050 for all historical emissions. Dynamics 365 runs on Azure, whose energy mix is trending toward 100% renewable across European regions.
Oracle publishes an annual ESG report and has committed to reducing emissions by 50% by 2030 (2020 baseline). Oracle Cloud Infrastructure (OCI) communicates its PUE figures and renewable energy procurement.
Odoo is less forthcoming on this topic. The Belgian vendor does not yet publish a structured ESG report with verified emissions data. For an Odoo SaaS deployment, ask your integrator where the instance is hosted and what the environmental credentials of that hosting provider are.
How to Challenge Your Vendor at Renewal
Concrete questions to include in a vendor questionnaire or RFP:
- What are your emission reduction commitments (scope 1, 2, 3), and are they validated by SBTi?
- In which data centres will my instance be hosted? What environmental certifications do those sites hold?
- Do you offer reporting on the carbon footprint associated with my usage (CPU, storage, network)?
- Is your ESG policy audited by an independent third party?
These questions are no longer seen as peripheral. They are part of the CSRD scope 3 due diligence that sustainability teams must conduct on strategic suppliers.
A 12-Month Digital Sobriety Action Plan for ERP
A realistic, sequenced plan applicable to a mid-sized enterprise:
Months 1–2: audit existing state. Inventory active modules, batch jobs, interfaces, and data volumes. Measure or estimate electricity consumption via hosting operator data or smart PDUs. Send the sustainability questionnaire to your ERP vendor.
Months 3–4: quick wins on modules and batch. Deactivate modules with no active users. Reduce or remove unnecessary batch jobs. These actions require no budget — only IT time and business-team sign-off.
Months 5–6: archiving plan. Define retention rules by data category (legal compliance, business utility, purge eligibility). Launch a first archiving campaign on the oldest data. Measure the volume reduction.
Months 7–8: interface review. With integration teams, audit the relevance and frequency of each data flow. Shift high-frequency synchronisations to event-driven or batch mode.
Months 9–10: hosting review. If on-premise, assess actual server utilisation rates and whether consolidation makes sense. If SaaS, question your vendor about the data centre and consider requesting a low-carbon hosting region.
Months 11–12: baseline and CSRD reporting. Publish a first ERP IT footprint assessment in your sustainability report. Set reduction targets for the following year. Include KPIs in your IT director dashboard.
To go further, read our CSRD and ERP guide: how to prepare sustainability reporting, our analysis of ERP cloud vs. on-premise: advantages and trade-offs, and our article on ERP data archiving and retention strategy.
