Unit4 alternative for Hungarian entities price, NAV compliance, 5-year TCO

What Unit4 is, and why people still call it Agresso

Unit4 is a Dutch business software company founded in 1980 and listed in Amsterdam since 1998. It merged with the Norwegian Agresso Group in 2000, which is where the name that survives in the Hungarian market comes from. The ownership history is short: Advent International bought the company in 2014, TA Associates in 2021 in a transaction above two billion dollars. Simon Paris has been CEO since January 2025. Headcount sits somewhere between 2,400 and 2,600 depending on the source, with more than 6,000 customers in over 100 countries.

The naming matters because both names still appear in search. Agresso Business World is now Unit4 ERP, CODA became Unit4 Financials by Coda, the acquired Prevero became Unit4 FP&A, and Scanmarket became Unit4 S2C. The platform picture is split: support for the older on-premise line ended in December 2024 according to the InvGate version database, and the vendor steers customers either to the cloud-native ERPx or to ERP CR hosted on Azure. I could not confirm that date against Unit4's own lifecycle documentation, because unit4.com blocks automated requests, so treat it as a single-source claim.

Public pricing, as far as it can be established

ERP Research puts it plainly: Unit4 pricing is never published and always requires a formal engagement. Everything below is a third-party estimate, and the sources partly contradict each other. That uncertainty cannot be hidden, so the sources are named in each row.

The contradictions show up inside single publishers. ITQlick puts year one for 10 users at 90-290k USD on one page and at 44,952 USD on another. No public source quotes a Hungarian implementation project price at all.

Five-year TCO comparison at 100 users

The Unit4 column starts from the ERP Pilot three-year breakdown for 100 users and extends it to five years. Where the figure is a linear extrapolation rather than a sourced number, the row says so. The AppForge column comes from the published price list.

Comparing the two columns needs an exchange rate. At an indicative 350 HUF/USD the Unit4 band is roughly 248-553 million HUF. That is not a central bank figure, and the ratio moves about ten percent with the rate. If the scope includes production planning, MES integration or a BI layer, the AppForge side moves into the enterprise band: 30-100M HUF to build, 52.5-225M HUF over five years.

In fairness, these two columns are not feature-equivalent. A five to seven module custom system does not do what the full Unit4 suite does, because it ships without ready-made fund accounting, deep HCM and talent management, or an FP&A planning engine. In exchange, maintenance and roadmap stay with you, which is responsibility and freedom in equal measure. For a 100-person organisation that genuinely uses all three Unit4 pillars, the gap narrows a long way.

Migration plan from Unit4 or Agresso

This is our method rather than a promise. The timings assume roughly 100 users across finance, projects and HR, and they get sharper after week two. Multi-entity groups should plan for a longer schedule.

1. Weeks 1-2: data picture and obligation inventory

   Which Unit4 generation is running (Agresso on-premise, ERP CR on Azure or ERPx), which modules are live, how many legal entities, what the chart of accounts looks like. In parallel we list the Hungarian reporting obligations, from NAV Online Számla to statistical filings, because those drive the schedule more than the software does.

2. Weeks 3-5: master data extraction and cleanup

   Partners, items, chart of accounts, cost centres, dimensions, currencies, tax codes. The export comes either through the ERPx REST API or straight out of the legacy installation's relational database; the exact path depends on the deployment, which is why nobody should promise a schedule before week two. Cleanup usually costs more calendar time than extraction.

3. Weeks 6-10: three to five years of transaction history

   Sales and supplier invoices, journal entries, project time and cost, HR base records. ERP Research recommends at least two full trial migrations before go-live and we stick to that, because the first trial always finds a document type nobody remembered.

4. Weeks 11-20: build, NAV integration, UAT

   Modules are written in code, and outgoing NAV Online Számla 3.0 reporting sits inside the fixed price. Your accountant and controller sit in UAT rather than in the week after go-live. This is also where it becomes clear which Unit4 functions are worth keeping instead of rebuilding.

5. Weeks 21-28: parallel run and cutover

   Eight to fourteen weeks of parallel operation with daily reconciliation between the two systems. Unit4 stays read-only until the licence lapses so closed years remain searchable. The Surrey report suggests most of the damage happens in the weeks after go-live, so hypercare is a fixed part of the project rather than an upsell.