BRENNEN

Industries / Technology / Software and SaaS / ERP and CRM software

Putting it in

Putting it in is the work of choosing a new ERP or CRM system, setting it up, loading the old system's data into it and switching it on, usually with outside consultants, and then keeping it on a version the vendor still supports.

7

Milestones achieved, from 2007 to 2026.

3

To watch for: announced, not yet confirmed outside.

2

Open deliverables. Nobody has shipped them.

The road

AchievedWatch forOpen

Achieved

  1. 2007

    A suite rented online

    NetSuite sold ERP, CRM and online-shop software as one application that customers reached over the internet and paid for by subscription, so they bought no servers and, in NetSuite's words, paid no "ongoing maintenance and upgrade charges". Its December 2007 stock-market prospectus reported more than 5,400 active customers and revenue of $67.2 million in 2006, and said it served every customer from a single data center run by another company.

    LessonRenting the system moved upgrade work to the vendor, and the prospectus listed the matching risk, that one data-center outage would reach every customer at once.

    sec.gov

    Credit

    NetSuite, co-founded in 1998 by Evan Goldberg, with an investment company controlled by Larry Ellison as its largest shareholder

  2. 2012

    A billion spent, nothing fielded

    In 2004 the US Air Force began the Expeditionary Combat Support System (ECSS) to replace hundreds of old logistics systems with commercial software from Oracle, put in by Computer Sciences Corporation. The Secretary of Defense canceled it in 2012 after more than $1 billion had been spent without "fielding any usable capability"; finishing would have cost about another $1 billion for 25% of what was planned. A 2014 Senate staff report found that Air Force staff would not change their working methods, so the program customized the commercial software instead, and that it had six program managers in eight years.

    LessonStandard software saves money only when the buyer is willing to change how it works to fit the software.

    hsgac.senate.gov

    Credit

    a failure; investigated by the US Senate Permanent Subcommittee on Investigations

  3. 2018

    Seven years, then stopped

    In 2011 the German discount grocer Lidl began replacing its home-built stock system, Wawi, with one based on SAP for Retail, called eLWIS. By 2018 it ran in Austria, Northern Ireland and the United States, and in July 2018 Lidl stopped the project and went back to developing Wawi; an internal note said the original goals could not be reached at acceptable cost. The trade paper Lebensmittelzeitung, citing industry observers, put the money spent at about €500 million; neither company confirmed a figure. According to Handelsblatt, Lidl values its stock at purchase prices while SAP's retail software works from retail prices, and Lidl had the software adapted rather than change.

    LessonKeeping one long-standing accounting habit meant rebuilding standard software around it.

    computerwoche.deconsultancy.uk

    Credit

    a failure; reported by Computerwoche and Handelsblatt

  4. 2018

    One plant's launch hits sales

    Revlon switched on a new SAP ERP system in the United States in February 2018, and its factory in Oxford, North Carolina, then could not make and ship some products to large retailers. Revlon's annual report estimates it could not fill orders worth about $64 million of net sales in 2018 and spent $53.6 million extra recovering. Management found a material weakness in its financial controls, meaning a real chance that a serious error in the accounts would not be caught, and its auditor, KPMG, gave an adverse opinion on those controls.

    LessonA rollout fault on the factory floor became a fault in the accounts, which the auditor had to report.

    sec.gov

    Credit

    a failure; disclosed by Revlon in its 2018 Form 10-K

  5. 2020

    Old system gets a deadline

    SAP said in February 2020 that mainstream maintenance, meaning regular fixes and legal updates at the normal fee, would end in 2027 for the core of SAP Business Suite 7, which includes its ERP Central Component (ECC). Extended maintenance would run to the end of 2030 for a premium of two percentage points, and the successor, S/4HANA, would be maintained until 2040. The Register reported that the 2027 date was itself a two-year extension from 2025, and that in September 2024 Gartner counted only 37% of ECC customers as having licensed S/4HANA. In January 2025 SAP said a paid "transition option" would run from 2031 to 2033 for some customers who sign its RISE cloud contract.

    news.sap.comtheregister.com

    Credit

    SAP

  6. 2022

    Customized, then rebuilt

    Birmingham City Council, the largest local authority in Europe, replaced its old SAP system with Oracle Fusion in April 2022. Its own June 2023 cabinet report said the plan had been to adopt the software and change the council's processes, but officers had instead customized it to fit existing ones; payments in and out had to be matched to accounts by hand, the 2022/23 accounts could not be closed on time, and the full cost was put at about £100 million. A rebuilt system went live in August 2026, and the council's auditor, Grant Thornton, called the switch largely successful, according to The Register, which puts the total cost at about £144.4 million against a first estimate of £20 million.

    LessonBad data outlives the system: the auditor still expects to be unable to vouch for the council's accounts until 2028/29.

    birmingham.gov.uktheregister.com

    Credit

    a failure; reported by Birmingham City Council and its auditor

  7. 2026

    An agent ports ERP code

    Researchers used the Claude Code agent to move 12 features of a company's ERP system from Visual Basic 6, a language Microsoft stopped supporting in 2008, to C# on.NET 10, and then tested whether each new feature behaved like the old one. On average the migrated features matched 70% of the time: 92% for simple features and 47% for complex ones, which used 1.47 million and 9.09 million tokens of AI work ($1.66 and $10.28).

    LessonThe more complex the feature, the less of it survived the move intact.

    arxiv.org

    Credit

    Iago da Silva Rodrigues Alves, Cristiano Politowski and João Eduardo Montandon

Watch for

  1. A third less migration work

    SAP says new "agent-led transformation tooling" can cut the effort of moving to its newer ERP by more than 35%, by automating the analysis of the old system, the repair of custom code, setup and testing. At the same event SAP said work that once took weeks, from mapping a company's systems to assessing its custom code, can be done in a single weekend.

    Achieved whencustomers or their auditors publish effort and defect counts for finished migrations, compared with similar migrations done without the tools.

    news.sap.comnews.sap.com

    Claimed by

    SAP, May 2026

  2. Agents that set up systems

    Oracle added AI agents to its implementation service that analyze a customer's current systems, turn business processes into designs, build the Oracle Fusion configuration, plan tests and write integration code, working from Oracle's machine-readable store of setup rules. Lexington Health's IT director said the approach cut "certain design and configuration efforts by 80 percent" before go-live.

    Achieved whena customer that used the agents goes live and an outside review reports the hours saved and the defects found after go-live.

    oracle.com

    Claimed by

    Oracle and Lexington Health, October 2026

  3. Five shared cloud ERPs

    The UK government plans five shared service centers, each running a cloud ERP for a group of departments, operational by 2028, so that departments use common processes and data. The National Audit Office counts £1.15 billion of Treasury funding committed since 2021, £459 million spent since 2020 and £1.0 billion of net lifetime benefits expected, but it found inconsistent ERP configurations, no single owner and "a real risk that the strategy will not be delivered to time or budget".

    Achieved whenall five centers are live with their departments on board and the National Audit Office confirms the benefits.

    nao.org.uk

    Claimed by

    Cabinet Office, as reported by the National Audit Office, March 2026

Open

  1. 01

    A migration test with answers

    A public data set for a made-up company, exported as the flat files old systems produce (customers, suppliers, items, open invoices, stock and ledger balances), with known errors planted in it and an answer key, plus a scorer that loads a tool's cleaned output into an open-source ERP and checks every planted error and every balance. Planted errors would include duplicate customers, wrong units of measure, invalid tax codes and open invoices that do not add up to the ledger.

    The brief
    Credit · unclaimed
  2. 02

    Community modules, ported by agents

    A public test of coding agents on a job that comes round with every yearly Odoo release: porting the free add-on modules kept by the Odoo Community Association (OCA) to the new version. Take 100 modules that people have already ported from Odoo 18 to Odoo 19, give each agent the 18.0 code, the OCA's migration notes and its rule-based migration tool, and score each port by whether the module installs, passes its own tests and passes the OCA's style checks, then compare it line by line with the human port.

    The brief
    Credit · unclaimed

Open 01 · the brief

A migration test with answers

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A public data set for a made-up company, exported as the flat files old systems produce (customers, suppliers, items, open invoices, stock and ledger balances), with known errors planted in it and an answer key, plus a scorer that loads a tool's cleaned output into an open-source ERP and checks every planted error and every balance. Planted errors would include duplicate customers, wrong units of measure, invalid tax codes and open invoices that do not add up to the ledger.

Why it is still open

Vendors now sell AI migration tools with effort claims, such as SAP's 35%, but publish no test of whether the tools catch bad data. In January 2026 Birmingham's auditor found that the council's process "for ensuring that data is ready for migration was not well-established for finance in particular", while it was rebuilding the system that failed in 2022. Web and arXiv searches on 20 November 2026 found no public migration test set with planted errors.

computerweekly.comnews.sap.com

Built with what exists

ERPNext or Odoo Community Edition as the target system; Python with Faker and pandas to generate the data; SQL checks on the target database; current language models such as Claude, or open-weight models, as the tools under test.

  1. First step

    Write down the ten error types, generate a 1,000-record pilot set and load it into a local ERPNext by hand to check the answer key.

  2. Done looks like

    50,000 records with 500 planted errors of ten kinds, published with scores for at least three tools or agents: the share of planted errors found, the number of false alarms, and whether the trial balance and open invoices match the source to the cent after loading.

Open 02 · the brief

Community modules, ported by agents

Credit · unclaimed

The first to publish is credited on this line, and the deliverable moves from Open to Achieved.

What to build

A public test of coding agents on a job that comes round with every yearly Odoo release: porting the free add-on modules kept by the Odoo Community Association (OCA) to the new version. Take 100 modules that people have already ported from Odoo 18 to Odoo 19, give each agent the 18.0 code, the OCA's migration notes and its rule-based migration tool, and score each port by whether the module installs, passes its own tests and passes the OCA's style checks, then compare it line by line with the human port.

Why it is still open

On 20 November 2026, more than a year after Odoo 19 came out, the OCA's migration checklists for four of its repositories (sales, purchasing, finance tools and web) marked 149 modules as ported and 146 as not yet done. In September 2025 OCA contributors debated a plan to send many machine-made migration pull requests; one wrote that recent migrations are "very easy for most modules" and that AI could get "1000+ modules" migrated. The OCA's own tool, odoo-module-migrator, applies fixed renaming rules. A search found guides, workflow scripts and a vendor's time estimates, but no published rate of how often an agent's port passes.

github.comgithub.comtest.odoo-community.orggithub.com

Built with what exists

the OCA's open-source repositories on GitHub; odoo-module-migrator as the baseline; Odoo 19 Community Edition in Docker with the OCA's test and pre-commit setup; coding agents such as Claude Code, GitHub Copilot's agent (see the Note "Effort, not model") and agents built with Cursor's Agent SDK (see the Note "Findings that cite notes").

  1. First step

    Pick 20 modules from the sales repository that were ported to 19.0 this year, set up Odoo 19 with the OCA's test runner, and run odoo-module-migrator alone on their 18.0 code as the baseline.

  2. Done looks like

    100 modules, each run through at least three agents and the rule-based tool alone, with the share that install, pass their tests and pass the style checks, the cost of each port, and the differences from the human port marked by a reviewer who knows Odoo; all runs public. No pull requests are sent to OCA projects as part of the test.