ERP in Hungary: the market map

What an ERP is, and what it is made of

An ERP is a software suite on a shared database that runs finance, logistics, production and sales in one system. The definition comes down to three things: one master data set, one transaction log, several functional modules. If invoicing and the warehouse app each keep their own item master, that is two systems sitting next to each other, not an ERP.

We did not take the module list from one vendor marketing page. SAP and Oracle both block automated fetches of their “what is ERP” pages with a 403, so the breakdown is assembled from module names actually sold on the Hungarian market: Vision-Software’s Octopus 8, the Logzi module list, the Novitax product split and the LIBRA product family.

One market quirk is already visible. In Hungary payroll is usually a separate product rather than part of the core ERP. That is one reason international packaged systems here almost always end up with a Hungarian add-on or custom work beside them, and the budget has to account for it. For the basics we wrote a separate piece on what an ERP is.

How many companies actually need an ERP

We found no public figure for the Hungarian ERP market in monetary terms. Statista keeps its outlook behind a paywall, and Gartner and IDC do not publish Hungarian market share reports openly. What is freely available is the statistical office’s company register, and that draws the addressable base reasonably well.

Three numbers follow from that table. The 10-249 band holds 39,906 companies, and that is the core of the Hungarian ERP market. Above 50 staff there are 6,325; above 250 there are 1,052. One caveat matters: these are registered rather than actively trading businesses. Most of the 836,000 entities in the zero-headcount bucket will never buy an ERP, and the statistical office counts operating SMEs separately, so the two figures are not interchangeable.

Company counts: KSH stadat 9.1.1.5, 2025. The software level column is our own read, not a published statistic.

Who is on the market

The uzletiszoftver.com software catalogue lists 50 products per page across three pages in its ERP category, which puts roughly 100 to 150 distinct ERP products on the Hungarian market. The catalogue publishes no total, so that number is an estimate from the per-page count. The fragmentation answers a question on its own: most of these products have no public price, no comparative review, and often no recent reference either.

International systems with a Hungarian presence

“Not verified” means we found no public vendor statement on the point. It does not mean the capability is missing; ask the partner.

Hungarian-built systems

The catalogue carries further names we did not verify on vendor sites: Vectory, MGS-IVISZ, azERP, reflex plus, 10xONE, myCentury, Stockhouse, TREND, ROOLNET, Symbol Enterprise, Szinva Ügyvitel, ÜgyVisz, AvERP, ECoNET, DREAM, Helix. One frequently searched name deserves a separate line: for Forrás ERP we found no reliable public source on the vendor or its current status, and the forrasnet.hu domain did not resolve on the day we checked. Until that clears up we do not list it among active products. The ten best known Hungarian systems are covered in more depth in our best ERP systems in Hungary 2026 round-up.

What Hungarian regulation expects from an ERP

This is the section that separates a Hungarian ERP project from the international template. A globally solid system can still fail here if statutory reporting is delegated to a partner add-on, and that add-on lags behind schema changes.

Packaged or custom

This decision is rarely binary, and it is not binary for us either. The table below is our position rather than a cited statistic, with one exception: Panorama’s 2026 data puts over-customisation among the contributing factors in 23 percent of failures.

In practice most Hungarian companies of 30 to 150 staff land somewhere in between: a packaged financial core with a custom sector layer and integrations on top. This two-tier arrangement also appears on CloudERP.hu’s 2026 trend list. The reasoning is simple. Statutory compliance stays on the packaged side where someone maintains it, and the process that gives you an edge stays on your own side where you can change it.

Rollout time and cost

Start with the best supported number, because it comes from an official vendor list price. A 50-person company buys 30 Dynamics 365 Business Central Essentials seats and 20 Team Members seats: 30 × EUR 69.30 plus 20 × EUR 6.90 a month, which is EUR 2,217, or about EUR 26,600 a year. At 400 HUF/EUR that is roughly HUF 10.6 million a year on licences alone, before implementation. The figure contains no implementation, no customisation and no Hungarian add-on.

Hungarian implementers rarely publish rollout prices, but they do publish ratios. Acterra International, a Hungarian SAP Business One partner, puts implementation at 1.5 to 2 times the licence cost, annual software maintenance at 10 to 20 percent of the licence, and complementary software at 10 to 15 percent of the total ERP budget.

This table is not a published market statistic. It is our own estimate derived from the public list prices and ratios above, and it should be cited that way. If anyone has a more precise public Hungarian ERP price table, we would like to see it.

To run the arithmetic with your own numbers, we built a tool: 5-year ERP TCO calculator.

How often ERP projects overrun

The most cited source is Panorama Consulting Group’s annual ERP report. A caveat comes first: Panorama’s own page carries only a download form, the figures are not in the HTML, so we took them from a secondary source that names the 2026 report. Anyone basing a business decision on these should pull the PDF and check.

The cost row is ambiguously worded in the original. We read it as actual cost being 1.89 times the plan, rather than exceeding it by 189 percent.

Here are the failure causes in the discrete manufacturing breakdown. Worth noticing what is absent from the list: the software itself.

• Inadequate change management42%
• Bad data migration38%
• Inexperienced implementation team35%
• Missing executive sponsorship31%
• Insufficient user training29%
• Scope creep26%
• Over-customisation23%
• Poor vendor selection19%

On elapsed time the most quoted figure is Godlan’s: 17 months actual against 12 planned, on average. We found it on an aggregator with no link to the original report, so we treat it as an order of magnitude. On the day we checked, no public ERP rollout statistics based on a Hungarian sample existed at the statistical office, at IVSZ, or at the large consultancies.

How to choose

There is no universal sequence, but the projects we have seen tend to slip at similar points. These six steps come from those.

1. Write the process down before you invite anyone in

   Five to ten pages will do: what happens between an order arriving and an invoice going out, who touches it, where the manual steps are. Without that, every demo looks good, because the vendor is showing you their own story.

2. Model the licence curve over five years, with headcount growth

   Per-seat pricing keeps climbing even when the system does not gain a single feature. Add the Hungarian complements and the payroll product, because those are separate line items.

3. Ask how statutory reporting is actually delivered

   Who builds the NAV Online Invoice module, how fast it follows a schema change, whether it is in the price, and what happens on the eVAT machine-to-machine side from January 2027.

4. Look at who will implement it, not only what is implemented

   On Panorama's list an inexperienced implementation team is the third most common cause of failure. Ask for a reference from a Hungarian company of similar size and sector, and actually call them.

5. Plan the data migration at the start of the project

   Bad data migration is the second most common cause. Master data cleanup takes months, and it is usually the client's team doing it rather than the vendor's.

6. Put the exit terms in the contract

   Data export format, source code access or escrow, and what happens to customisations at a version upgrade. Have that conversation at the beginning, not when you already want to leave.

On the operational side we go deeper in the ERP system guide, and the neighbouring category is covered in our Hungarian CRM round-up.