What is Done & Pending — Migration Status Map

A migration honesty panel — four states, not a pass/fail. It shows which business flows the browser kernel already reproduces indistinguishably from iDempiere (maxDiff=0c), and exactly what stands between that and a full tenant cut-over.

🟢 Done · in the new experience

Folds to the cent today

Every figure reconciles to the cent against real iDempiere, in two currencies. 44 checked surfaces.

Live nowReal iDempiere, resident — it is the benchmark — GardenWorld, the default company (no install), is iDempiere's own demo: 1,003 tables · 370 windows · 20,911 fields; every posting reconciles to the cent against the real iDempiere ledger, and a second iDempiere company migrates live from its Postgres database. Nothing in the dictionary is left uninterpreted.
Order-to-Cash & Procure-to-Pay — sales / purchase order → delivery → invoice → 3-way match → payment → allocation, customer and vendor sides, in two currencies, with reversals and voids that net to zero
Inventory & costing — stock movements, on-hand balances, automatic replenishment, inter-company transfers, and cost of goods sold posted to the ledger
General Ledger & financials — journals, multi-currency (FX), bank reconciliation, and the statements that read off them: Balance Sheet · Income Statement · Cash Flow, invoice print, AR / AP aging
Live nowDocuments & processes — every document's legal actions and state changes (Draft → Complete → Close / Void) enforced exactly, now on iDempiere's own screens: New creates a signed order and Complete processes it for real (each survives reload); processes and reports run on demand from the menu. Create / edit / delete is now general — any window is editable from its own Application Dictionary entry (field types, mandatory, read-only and sequences all read from the AD — not a hand-picked few tables): a Business Partner is New / Edit / Delete just like an Order, each a signed change that survives reload
Live nowFront door — one URL, no install — five migrated demo companies appear at login and install on pick, no dialog, no server
Live nowBIM → Project Order — a priced building becomes a real iDempiere project (phases · tasks · cost lines): on the Duplex, 6 phases · 9 tasks · 16 cost lines whose planned amount ties to the 5D estimate to the cent, pushed to the ERP from the model in one click — and it is now financially controllable, not just visible: priced in its own currency (MYR + conversion rate) and units (m / m² / m³), BoQ lines mapped to GL accounts; Original + approved Variations = Revised Contract Sum with live EVM (PV / EV / AC, CPI / SPI); a Variation Order approves through the document FSM (DR → CO) to move the commitment; a progress claim raises a C_Invoice and shows the GL posting preview (balanced Dr / Cr — honest where the demo's books carry no Fact_Acct); and a what-if Project Order can be pushed as a blue speculation and rolled back on the timeline — every figure to the cent (BigDecimal)
Other ERPs, same engine — one renderer, N dictionaries — the unchanged screens fold & drive any vendor's model from its own dictionary, no per-ERP code: Odoo end-to-end (full migrated catalog 38·35·27, order-to-cash to the cent, its own menus over the unchanged UI), with SAP · Oracle · MS Dynamics as wired proof-of-concept companies

All figures reconciled to the cent against real iDempiere — every check independently falsified (a deliberately broken rule must fail it)

🟠 Pending · extraction gap

Fold proven — data not yet wired

The engine already folds these flows (passing witness each). Mechanical extractor work, not engine development.

Purchasing data — remaining PO chains not yet extracted into shard (fold proven live for P00011; gen_ad_odoo.js covers SOs only today)
Money — 3 real payments + reconciles, 13 manual journals, 7 credit notes
Inventory state — 43 on-hand quants as opening balances

iDempiere-side: no extraction gap — GardenWorld is resident & full. These rows are Odoo-side. Backlog → MIGRATE_INSTALL_TENANT.md §RESUME

🔴 Out of fold-scope — by data or architecture

No unbuilt fold capability remains

Every posting and report this demo's data supports already folds — gap-closure complete (2026-06-14). What's left here can't be folded: the source has no such postings, or it's program code, not declarative ERP rules.

Odoo automation rules — resolved: architectural, by design. Investigated — all 64 are Python program code, not declarative rules, so there is nothing to fold; running them needs a Python runtime. Effectively N/A, not a missing feature.
Analytic / cost-centre accounting — resolved: data condition, not an engine gap. The source defines analytic accounts but posts nothing to them (0 postings) — it folds the moment such postings exist.
Posting edge-cases — charge lines · GL distribution · realised FX gain/loss. Same: data-bound, not unbuilt — defined in the dictionary but absent from this demo company's books.

Bottom line: none of these is an unbuilt engine gap — fold-gap closure is complete (all priorities, 2026-06-14). Per the Grand Lane, the genuine remaining work is wiring proven engines into the live screens — of the Complete → Create → Post journey, Complete (J5), Create (J4) and Post (J6) are now live on iDempiere's own surfaces — Complete/Create sign, and a completed document's GL now renders to the cent on the invoice window (Posting-Preview), with a receipt and a financial statement that fold from the books; fanning the journey across all five tenants is the active leg — UI, not folding. iDempiere-side: no interpreter gaps remain.

🔵 N/A · deleted by architecture

No port — leaves the denominator

Whole tiers the serverless model deletes — not missing features, no counterpart by design.

What the server did

Who does it now

ZK web UI · 190k LOC

the browser renders

Generated X_* ORM · 345k LOC

AD rides as data

Server-side HTML · 44k LOC

gone, no server

JDBC · OSGi · app server

nothing owns the record

Web services tier

the op-log is the wire ^*

* Live nowShare a sale, no server: a deliver-later sale travels device-to-device by your own channel — copy → WhatsApp / email → paste → it replays on the other phone. Working today, not a roadmap item (PR #300).

Granted in exchange — the -marked rows run nothing in their place; deleting 40% is what makes the engine offline-first, serverless, and per-device shardable — live today. Finer warm/cold tiers + checkpoint boot are proven-ahead, switched on when scale needs them.

The Holy Grail

One engine, every ERP — no server, nothing destroyed

How any ERP's before state becomes a single, foldable after state — and why "the log is the truth" stays editable and maintainable.

① Any ERP — the source (before)

Each runs its own server + database

iDempiereOdooSAPDynamics

Each carries a model, its data, and its rules / automation — and overwrites rows in place (destructive updates: the past is lost).

▼ MIGRATE — extract, don't rebuild ▼

② Translate — the one elegant law

Model → the AD canonical dictionary · Rules → re-filed by op-log effect

DERIVEout ← f(in) · no op

VALIDATEassert(p) · gates, no op

ACTemits signed ops

Code-only remainder → a user plugin (exposed to find & resolve), never an auto-import.

▼ every change becomes one signed op ▼

③ The truth — the spine

A signed, hash-chained op-log — append-only

op → op → op → op → op → …

Every change, kept forever. Nobody owns it; any client can verify and rebuild from it.

▼ FOLD — replay the log ▼

④ The live state (after)

Current numbers + screens = fold(op-log)

In the browser, no server. One renderer, N dictionaries · offline · per-device.

Before — any big ERP

After — the Grail engine

Truth lives in a server row (overwritten)

A signed op-log (append-only)

Change a value = UPDATE — past lost

Change = append an op — past kept

Automation = code per ERP

3 typed lanes + user plugin

"How did this get here?" = guess

Replay the log — exact

EDITappend a new signed op → state changes now, past kept

BRANCHBlue Future — a safe fork; accept or discard

AUDITfold to any past point — exact provenance

FIXappend a reversing op — nothing destroyed

"Can we edit it? Is it maintainable?" — the op-log is git, for your ERP data. You never hand-edit history; you commit a change. To edit anything you append a signed op and the live state — a fold of the log — updates at once: the present is always editable, the past stays as the audit trail. Maintainable more, not less — every value carries its own history, reversible and replayable, with no destructive-update mysteries.