Lyrion ERP: what mid-sized businesses in Bavaria should know before introduction

ERP introductions are considered the most expensive and riskiest IT projects in the SME segment — and the reputation is earned. Two-thirds of all ERP projects exceed budget or schedule, many both. What is discussed less often: why that is, and whether it can be different.

Lyrion ERP is the platform we at HELITS use when mid-sized companies in Bavaria and the DACH region want to replace their business software or introduce it for the first time in a structured way. This article explains what distinguishes Lyrion from classic ERP systems — and what we have taken from the first productive introduction projects.

What an ERP system is actually supposed to do

An ERP system (Enterprise Resource Planning) is a company's central data foundation: orders, purchasing, warehouse, production, financial accounting, HR — everything in one system that talks to itself. The theoretical added value is clear: no redundant data maintenance, no media breaks, a single source of truth.

Reality looks different at many mid-sized businesses. We regularly see companies with 40 to 200 employees that operate an ERP from the early 2000s as an accounting backend, do order management in Excel, communicate stock movements via email, and run leave planning in a separate cloud app. That costs — in working time, in error rate, in lack of transparency.

Why Lyrion is a fit for the SME segment

Lyrion is modular by design. That sounds like a standard sales argument — but it is not a given for ERP systems. SAP Business One, for instance, is modular in licensing, but in practice a tightly interlocked system in which one module rarely runs without another. That makes the entry expensive and the project timeline long.

With Lyrion, in the first step we activate only what the customer needs. A production company in the Rosenheim area, 65 employees, plastics processing: we started with item master, bills of material and production orders — three modules, six weeks of introduction, productive without standstill. Finance was added three months later, when the team had become familiar with the system.

This staggered approach is not a compromise, it is the model. ERP projects that try to introduce everything at once fail more frequently — not because the software is bad, but because the organisation cannot absorb the change.

Data migration: the actual risk

What is regularly underestimated in ERP projects is data migration. Not the technical side — that is solvable — but the substantive side: what is the state of the data in the old system?

For a trading company in Traunstein that switched from an AS/400-based solution to Lyrion, we did a data audit before the project start. Result: 34 % of item masters had inconsistent units (some kg instead of pieces), 18 % of supplier records contained duplicate entries with diverging payment terms. That is not an exception — that is the normal state in systems that have grown over years.

Migrating these problems into the new platform does not solve them. It only makes them more visible — and louder, because the new system depends on consistent data. In every introduction project we spend about 20 to 30 percent of the total time on data cleansing before we even configure an interface.

Integration with Microsoft 365

Lyrion can be connected to Microsoft 365 — Teams notifications for critical stock levels, document storage in SharePoint, Outlook integration for offer and order correspondence. For companies that have already standardised on M365, this is a real advantage: no second login ecosystem, no app proliferation.

In combination with HELITS HRIS, comprehensive coverage emerges: personnel master data is maintained once and is available both for the HR module and for ERP cost allocation. Duplicate maintenance disappears.

What Lyrion is not

Lyrion is not an SAP replacement for corporations. It is a platform that can be introduced for upper-mid-market businesses — 20 to 500 employees, manufacturing or trading operations — within a project timeframe of three to nine months, without external consulting teams of ten people.

For companies with highly specific industry requirements (pharmaceutical management, aerospace supply with AS9100 certification, financial services with regulatory requirements) an individual review is necessary. Lyrion solidly covers most standard processes, but not every industry specificity is mapped out of the box.

What we take from the first projects

Three productive Lyrion introductions in Bavaria are behind us. The common pattern: the critical success factor is not the software — it is the internal project responsibility on the customer side. Projects in which an employee with a real mandate and capacity acts as an internal project manager run significantly better than projects where this is done "on the side."

That is an uncomfortable statement because it demands effort on the customer side. But it is realistic — and for us the reason why we explicitly clarify before every project start who is internally at the wheel.

For companies considering an ERP introduction or replacement, we are available for an initial, no-obligation conversation. Details on Lyrion and our introduction approach can be found under IT Consulting & Digitalisation.

---