# Is Your ERP Data Ready for AI? A Readiness Checklist > Source: https://netray.co/erp-help/cio-is-our-erp-data-ready-for-ai > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer Most ERP data is ready enough to start a scoped AI pilot immediately; full data-quality remediation is not a prerequisite. A handful of specific gaps - duplicate item or customer masters, inconsistent units of measure, missing descriptions, and orphaned records - will visibly degrade AI answers and are worth checking before the pilot, not after. ## Kind cio ## System cio ## Erp ERP Data Quality (any platform) ## Module Data Governance / AI Readiness ## Query Is our ERP data ready for AI ## Alternate Queries - ERP data readiness for AI - how to prepare ERP data for AI - ERP data quality checklist before AI project - AI readiness assessment for ERP ## Applies To Any ERP instance being considered for a grounded AI or reporting assistant project ## Steps ### 5-point readiness check **Items:** - Sample 20 real questions users would actually ask, then manually check whether the ERP data currently answers them correctly. - Check item, customer and vendor master data for duplicates - the single most common cause of confusing AI answers. - Confirm consistent units of measure and currency across sites and subsidiaries that feed the same report. - Verify that access control mapping - who is allowed to see what - is enforced at the data layer, not only in the ERP's own UI. - Check for orphaned or soft-deleted records still appearing in the tables an AI layer would query. - Confirm there is a stable read path (API, ODBC, or a replica) that will not add load to production transaction processing. - Do not wait for a full master data management project - fix the top three issues the pilot surfaces, then expand scope. ## Sections ### What 'AI ready' actually means **Body:** It does not mean perfect data. It means the data is consistent enough that the same question, asked twice, gets the same correct answer both times. Most ERP instances that have been running for a few years already clear that bar for their core transactional data - open orders, inventory quantities, AR balances - even if peripheral fields are messy. The gap that matters is specifically in the fields used for matching and identification: item numbers, customer names, and descriptions. Those are what an AI layer relies on to connect a user's question to the right record. ### The master data issues that matter most **Body:** Duplicate item or customer records are the most common AI-answer killer, because the assistant may correctly find one duplicate while the user was thinking of another, producing an answer that looks confident and wrong. Blank or inconsistent descriptions cause similar mismatches when a user searches by name rather than by exact code. Inconsistent units of measure or currency across subsidiaries feeding a combined report will produce numerically wrong totals even when every individual record is technically correct, which is a harder failure to catch than a clearly nonsensical answer. ### Governance and access control before day one **Body:** An AI layer must respect the same row- and field-level security the ERP already enforces through its own roles - a shop-floor user asking a natural-language question should never be able to retrieve payroll or standard-cost data they could not see in the ERP UI. This needs to be verified explicitly, not assumed, since many ERP security models were built for form-based access, not free-text queries. ### The fastest way to find out **Body:** Running the pilot itself is usually the fastest and cheapest data-readiness audit available. The specific questions that come back wrong point directly at the exact fields and tables that need attention, which is far more actionable than a generic data-quality audit project run in isolation before any AI work begins. ## Pitfalls - Delaying the AI pilot for a 12-month data cleanup project that never quite finishes. - Assuming AI will silently fix bad data rather than surfacing it in visibly wrong answers. - Not checking access control mapping before the pilot, discovering the gap only after a wrong disclosure. - Ignoring unit-of-measure or currency inconsistency across subsidiaries until totals come back visibly wrong. - Treating a one-time data audit as sufficient, with no ongoing governance once new bad records start entering the system. ## Ai Angle ERPray pilots typically begin with a short data-readiness pass grounded against the customer's actual tables and saved searches, which gives the CIO a concrete, prioritized list of the five to ten fields worth fixing rather than a generic data-quality audit disconnected from how the AI will actually be used. ## Faq ### Do we need a full data cleanup before starting an AI pilot? **Answer:** No. Start the pilot with current data, then fix the specific issues it surfaces. A full cleanup project run in isolation, before any real use case is tested, usually fixes the wrong things first. ### What is the most common data issue that breaks AI answers? **Answer:** Duplicate item, customer or vendor master records. The AI can correctly retrieve one record while the user meant a different duplicate, producing a confident but wrong answer. ### How do we know if our access control setup is safe for an AI layer? **Answer:** Test it directly: have a user with a limited ERP role ask the AI assistant questions that would require elevated access, and confirm the answers are correctly restricted before wider rollout. ### Should data governance change once AI is in production? **Answer:** Yes. New records entering the system need the same quality checks that fed the initial pilot, since AI answer quality degrades again if duplicate or inconsistent data is allowed to accumulate after go-live. ### Can we skip the readiness check and just launch the pilot? **Answer:** You can, and in practice the pilot itself often functions as the readiness check, since the wrong answers it produces point directly at the fields needing attention faster than a standalone audit would. ## Search terms erp data readiness for ai, is our erp data ready for ai, erp data quality checklist ai, ai readiness assessment erp, erp master data ai, erp data cleanup before ai, erp access control ai, duplicate item master ai, erp data governance ai, erp data quality ai project --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json