Moving to an AI-native ERP: a migration path that limits risk

Contents

1. What vendors now promise
2. Two paths
3. The data that has to move
4. A 90-day sequence
5. Questions buyers ask
6. Sources

ERP migrations have a poor record. Gartner's ERP strategy lead said in November 2025 that 70% of ERP initiatives fail to fully meet their original business case goals⁠1ERP carnage continues as orgs jump in unpreparedThe Register · 13 Nov 2025, and a June 2025 analysis of more than 250 implementations found 45% over budget and 51% over schedule⁠2First National Capital Corporation releases research on ERP implementationsManufacturing Dive (press release) · 13 Jun 2025. AI-native vendors promise something different: go-lives in weeks. Both can be true, depending on how much is moved at once.

What vendors now promise

These are claims from the vendors' own pages, and they describe the vendor's part of the work. They do not include the time a finance team spends cleaning data, testing reports and retraining staff.

Two paths

Operations first. The ledger stays where it is. An operations layer connects to it, reads customers, items and stock, and writes back orders and purchase orders. OpenLazarus describes this path for distributors: move the daily work first and retire the old screens when nobody opens them any more⁠6Wholesale and distributionOpenLazarus. DOSS follows the same logic for consumer brands⁠8DOSS: the AI-native operations platform for consumer goodsDOSS. The risk is contained, because the books do not move.

Ledger first. The general ledger moves to an AI-native product, and operations follow later or stay in existing tools. This suits companies whose bottleneck is the close or consolidation, such as the multi-entity groups DualEntry and Campfire describe⁠39DualEntry: the agentic AI ERPDualEntryCampfire: the AI-native ERPCampfire. The risk is higher, because the audit trail changes systems, but the vendors in this group take on more of the migration work themselves.

Moving the ledger and operations in the same quarter doubles the reconciliation work and leaves no stable system to compare against.

The data that has to move

• For an operations layer: customers and their pricing, items and units, stock by location, open sales and purchase orders, and supplier contacts. OpenLazarus's inventory article describes importing a product catalogue from a spreadsheet and defining warehouses, zones and reorder rules⁠10AI Inventory ManagerOpenLazarus · 26 Dec 2025.
• For a new ledger: chart of accounts, opening balances, open receivables and payables, fixed assets, and as much transaction history as reporting and audits require. OpenLazarus's bookkeeping article describes importing past transactions from QuickBooks or Xero as CSV files⁠11AI Bookkeeper: replace QuickBooks, Xero and FreshBooksOpenLazarus · 21 Dec 2025; the AI-native ledgers handle migration themselves⁠54PricingRilletPricingDualEntry.

A 90-day sequence

1. Weeks 1 to 2: draw the line. Decide which system owns each record, using the test in what to keep in your ERP.
2. Weeks 3 to 4: connect read-only. Let the new system read customers, items, stock and open orders without writing anything back.
3. Weeks 5 to 8: one flow, with approvals. Switch on a single flow, such as emailed orders or purchase-order drafting, with every action waiting for a person.
4. Weeks 9 to 12: loosen limits on evidence. Raise the approval thresholds only for the cases that ran cleanly, and hold a month-end close on the combined system.
5. Day 90: decide the next record. Expand to the next flow, or begin a ledger move, based on what the first one showed.

The end state after 90 days is modest and measurable. One flow runs with agents doing the routine cases and people approving the exceptions. The ledger has closed at least once with the new data flowing in. The finance team can name, for every field, which system is the master. That foundation is what makes the next move safe.

For the ranking of products by situation, see the main guide.

Questions buyers ask

Sources

1. ERP carnage continues as orgs jump in unprepared. The Register, 13 Nov 2025. Accessed 8 Nov 2026.
2. First National Capital Corporation releases research on ERP implementations. Manufacturing Dive (press release), 13 Jun 2025. Accessed 8 Nov 2026.
3. DualEntry: the agentic AI ERP. DualEntry. Accessed 8 Nov 2026.
4. Pricing. DualEntry. Accessed 8 Nov 2026.
5. Pricing. Rillet. Accessed 8 Nov 2026.
6. Wholesale and distribution. OpenLazarus. Accessed 8 Nov 2026.
7. Pricing. OpenLazarus. Accessed 8 Nov 2026.
8. DOSS: the AI-native operations platform for consumer goods. DOSS. Accessed 8 Nov 2026.
9. Campfire: the AI-native ERP. Campfire. Accessed 8 Nov 2026.
10. AI Inventory Manager. OpenLazarus, 26 Dec 2025. Accessed 8 Nov 2026.
11. AI Bookkeeper: replace QuickBooks, Xero and FreshBooks. OpenLazarus, 21 Dec 2025. Accessed 8 Nov 2026.

Updated 8 Nov 2026: First published.

Further reading

• Buyer's guide · Updated quarterlyThe best AI-native ERP for mid-sized companies in 2026An analysis of eight products sold as AI-native or AI-ready ERP, separated into the ones that keep the books and the ones that run operations, with the evidence behind each and a path to a first deployment.
• Guide · ArchitectureWhat to keep in your ERP when you add AI-native toolsThe ledger, inventory valuation and job costing need a system of record. Order entry, purchasing and follow-up often do not. A practical way to draw the line.
• Guide · DefinitionsAI-native vs AI-added ERP: what the difference means for buyersEvery ERP vendor now describes itself in terms of AI. The useful distinction is not the label but where the agent works, what it may change on its own and what it costs to run.