Mon – Sat: 9:00 AM – 7:00 PM IST
iDempiere

Compiere, ADempiere and iDempiere

Three names, one lineage — and what it means if your business is still running the earlier branches.

In short

Compiere was an early open-source ERP. A community disagreement over its commercial direction led to ADempiere, a community fork. ADempiere was later re-architected onto OSGi and a modern stack, and that became iDempiere. The data model is recognisably common across all three, which is why migration between them is a real option rather than a reimplementation.

Why It Matters

Why this matters in practice

A surprising number of businesses are still running Compiere or ADempiere instances implemented a decade or more ago, often unsupported and on obsolete infrastructure. Because the lineage is shared, moving to iDempiere is usually a migration rather than a fresh start — your data model, your configuration logic and often your reports have recognisable equivalents.

Shared ancestry means the data model is broadly familiar
Migration is usually possible without reimplementing from zero
iDempiere is the actively developed branch of the three
Customisations are the variable — core data usually maps cleanly
How It Works

How it works in practice

Compiere

The original. A commercial open-source model whose licensing direction prompted the first fork.

ADempiere

The community fork, continuing development under a community governance model.

iDempiere

A re-architecture of ADempiere onto OSGi, ZK and a modern Java stack, with the plugin model that defines it today.

What carried across

The application dictionary concept, the multi-organisation accounting model and much of the document structure.

What changed

The runtime, the UI framework and above all the extension mechanism — plugins rather than core modification.

Worked example

A worked example: why the lineage matters to a buyer

A business evaluating open-source ERP encounters all three names, often from different vendors, and reasonably asks whether this is one product with three labels.

It is not, and the differences are practical. Compiere's open-source line effectively ended after commercial acquisition. ADempiere continues but with much reduced activity. iDempiere is the actively developed line, rebuilt on OSGi, with the plugin architecture that makes upgrade-safe extension possible. A vendor proposing ADempiere in the present day is proposing a less active codebase, and the right question is simply why — sometimes the honest answer is that it is what their team knows.

What all three share is the Application Dictionary, the metadata layer that makes so much configurable without code. That shared inheritance is why concepts transfer between them and why experience on one is genuinely relevant to another. It is also why the lineage is worth understanding rather than dismissing as history: it explains both what these systems are good at and why the active one is the one with the plugin framework.

Key terms

The vocabulary, briefly

Term What it means
Compiere The original open-source ERP, from which the others descend.
ADempiere The 2006 community fork, formed over disagreements about project governance.
iDempiere The 2011 fork of ADempiere, rebuilt on OSGi with a modern technical architecture.
Fork A branch of a codebase taken in its own direction, usually over governance rather than technology.
Application Dictionary The metadata-driven architecture inherited through all three generations.
What Goes Wrong

Common mistakes worth avoiding

Assuming customisations migrate as-is

Core data migrates well; custom code usually has to be rebuilt as plugins. Inventory it before costing the move.

Leaving an unsupported instance running

An unpatched ERP on obsolete infrastructure is a security and continuity exposure, whatever its functional state.

Migrating history indiscriminately

Decide which transactional history genuinely needs to move. Carrying everything is expensive and rarely used.

No reconciliation after migration

Opening balances and stock valuation must reconcile to the source before the old system is switched off.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Project commit activity The most direct evidence of whether a codebase is maintained. Public, and rarely checked.
Release cadence Whether releases ship predictably. Long gaps are worth asking about.
Distinct active contributors Concentration risk. A project with one contributor carries the same risk as one supplier.
Issue response time How quickly reported problems get attention, which is the closest thing to a support signal.
FAQ

Questions we are asked about this

Development activity has largely concentrated on iDempiere, which is the branch receiving sustained work. Check the current state of each project before committing either way.
The data is the straightforward part because of the shared model. The effort sits in rebuilding customisations as OSGi plugins and in testing, so a customisation inventory is the first task.
Yes, and it is a well-trodden path because the data model is largely shared. The data migration is usually the straightforward part; the work is in customisations, which must be re-implemented as OSGi plugins rather than carried across as core modifications. That re-implementation is often worth doing on its own merits, since it is the step that makes future upgrades routine.
Governance rather than technology, in both cases. ADempiere formed when the community and the commercial entity behind Compiere disagreed about the project's direction and openness. iDempiere later forked from ADempiere over architectural direction and development process. This pattern is common in open source, and it is informative rather than alarming — it is how communities resolve disagreements that proprietary vendors resolve by decision.
iDempiere, in almost all cases, on the strength of development activity and the OSGi architecture. The qualification is your implementation partner: an excellent team on ADempiere will serve you better than a weak team on iDempiere, because with open source the partner is the larger variable. Where a partner proposes an older line, ask whether that reflects your requirements or their bench.
Substantially, yes. The Application Dictionary, document model, accounting engine and overall structure are recognisably common, so functional knowledge moves easily between them. What does not transfer is the extension mechanism: core modification habits learned on the older lines are actively harmful on iDempiere, and that is the specific thing to probe when assessing experience claimed on an earlier generation.
Related

Where to read next

What is iDempiere?

Read more

Our iDempiere consulting

Read more

What is an OSGi plugin?

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.