# Infor XA (MAPICS) Migration Readiness Assessment > Source: https://netray.co/tools/infor-xa-mapics-migration-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Ten questions that score how ready you are to move off Infor XA (MAPICS), covering customizations, IBM i dependencies, data quality and ownership. ## Category erp-migration ## Erp Infor XA ## Industry Discrete Manufacturing ## Audience - CIO - IT manager - ERP project lead ## Tool **Kind:** assessment **Questions:** #### How heavily is XA customized? **Help:** Include modified programs, added fields, custom screens and RPG or CL code. **Options:** ##### Close to standard, few modifications **Score:** 10 ##### Moderate, a known list of mods **Score:** 6 ##### Heavy, many mods and no complete list **Score:** 2 ##### We do not know **Score:** 0 #### How well documented are custom programs and reports? **Options:** ##### Documented and in source control **Score:** 10 ##### Partly documented **Score:** 6 ##### Only one or two people understand them **Score:** 2 ##### No documentation **Score:** 0 #### How many systems integrate with XA (EDI, shop floor, WMS, CRM, spreadsheets)? **Options:** ##### We have a complete inventory and it is short **Score:** 10 ##### We have an inventory and it is long **Score:** 6 ##### Partial list **Score:** 3 ##### No list **Score:** 0 #### How clean is item, bill of material and routing data? **Options:** ##### Reviewed and cleansed in the last two years **Score:** 10 ##### Mostly clean with known gaps **Score:** 6 ##### Many obsolete items and duplicates **Score:** 2 ##### Not reviewed **Score:** 0 #### Do you have people who know XA and the IBM i platform well? **Options:** ##### Yes, more than one, and they are staying **Score:** 10 ##### One key person **Score:** 5 ##### Mostly outside support **Score:** 3 ##### No **Score:** 0 #### Have you defined why you are migrating and what success looks like? **Options:** ##### Written business case and success measures **Score:** 10 ##### Agreed informally **Score:** 6 ##### Driven mainly by platform or support risk **Score:** 3 ##### Not defined **Score:** 0 #### How much of your process is outside XA (spreadsheets, paper, side databases)? **Options:** ##### Little, the ERP is the system of record **Score:** 10 ##### Some, known and tolerated **Score:** 6 ##### A lot of critical process lives outside **Score:** 2 ##### We cannot say **Score:** 0 #### How ready are users and leadership for process change? **Options:** ##### Sponsor named, super users identified **Score:** 10 ##### Leadership agrees, users not yet engaged **Score:** 6 ##### Mixed support **Score:** 3 ##### Resistance or no sponsor **Score:** 0 #### Do you have a plan for historical data (orders, costs, quality records)? **Options:** ##### Retention rules defined and tested **Score:** 10 ##### Rough plan to migrate or archive **Score:** 6 ##### Not decided **Score:** 2 ##### Assumed it will come across **Score:** 0 #### Do you know your regulatory and customer audit obligations during the change? **Help:** For example traceability, quality records and any export control requirements. **Options:** ##### Mapped and owned **Score:** 10 ##### Known but not mapped to the plan **Score:** 6 ##### Partially known **Score:** 3 ##### No **Score:** 0 **Bands:** #### Early stage: assess before you commit **Min:** 0 **Max:** 34 **Verdict:** There are large unknowns in customizations, integrations or data. Starting a migration now would likely produce a poor scope and a late project. **Recommendations:** - Inventory customizations, integrations and reports before choosing a target. - Name an owner for data quality and begin cleansing active items and bills. - Capture knowledge from the people who know XA and IBM i today. #### Partly ready: close the gaps first **Min:** 35 **Max:** 59 **Verdict:** You have some foundations, but gaps in documentation, data or ownership will hit the project hard if left alone. **Recommendations:** - Document the top custom programs and reports by business impact. - Write the business case and success measures so target selection is objective. - Plan the historical data and audit trail approach early. #### Ready to select and plan **Min:** 60 **Max:** 79 **Verdict:** The main risks are known. You can compare target platforms and build a realistic plan and budget. **Recommendations:** - Run a fit gap exercise against two or three candidate targets. - Decide which customizations to retire, replace or rebuild. - Build a cutover and parallel run plan around your busiest periods. #### Strong position **Min:** 80 **Max:** 100 **Verdict:** You are well prepared. Focus on execution quality, testing and change management. **Recommendations:** - Lock scope and governance and protect your key XA people during the project. - Plan data migration test cycles with business sign off. - Keep a rollback and support plan for the first closes after cutover. ## Content **Intro:** Moving off Infor XA (MAPICS) is rarely a pure software question. It depends on how much you have customized, how clean your data is and how much knowledge sits with a few people. This assessment scores those factors in about five minutes. **Sections:** #### How to use this assessment **Body:** Answer each question for the plant or group you intend to migrate, ideally together with someone from IT and someone from operations, since each will see different gaps. Be honest about unknowns: a score of zero on an answer such as we do not know is useful, because it points to discovery work that must come before any commitment. Export the result and use it as the opening page of your migration business case. #### What the questions measure **Body:** The ten questions cover five themes: customization depth and documentation, integrations, data quality, people and platform skills, and project readiness including sponsorship and audit obligations. Customizations and integrations drive most migration cost, since each one must be retired, replaced or rebuilt on the target. Data quality drives cutover risk. People and sponsorship decide whether the project survives its first difficult quarter. **Bullets:** - Customizations: count, documentation, ownership. - Integrations: inventory and complexity. - Data: items, bills, routings, history. - People: XA and IBM i knowledge. - Readiness: sponsor, goals, audit obligations. #### Reading your result **Body:** A low score does not mean you should not migrate. It means you should spend a few weeks on discovery first, because discovery is cheap compared with learning the same facts mid project. A middle score usually indicates a few specific gaps, commonly documentation and data, that you can close before selecting a target. A high score means you can move on to fit gap and planning. Remember the score is a guide, not an audit of your system. #### Common mistakes **Body:** Teams often choose the target platform first and discover the customization list later, which breaks the budget. Others assume history will migrate automatically, then find that costing, quality and traceability records need explicit rules. A third mistake is losing the one or two people who know the legacy system before knowledge is captured. Treat knowledge capture as a project task with an owner and a date. **Cta:** If you want help inventorying XA customizations and reports, we can use AI tools to read and summarize legacy code and reports so that discovery takes weeks rather than months. **Faq:** #### Is Infor XA the same as MAPICS? **Answer:** XA grew out of MAPICS, and many users still call it MAPICS. The product runs on IBM i. Naming differs between versions and companies, so this assessment applies to the family of MAPICS and XA installations running on that platform. #### Does a low score mean we should stay on XA? **Answer:** No. It means you should do discovery before committing. The score highlights unknowns in customizations, integrations and data. Closing those gaps first gives you a more accurate scope, budget and target selection. #### How long does an XA migration usually take? **Answer:** It depends heavily on customization, integrations and data quality. Projects commonly run from several months to well over a year. A discovery phase and a clear scope are the best predictors of staying on schedule. #### Can I use this for planning a move to CloudSuite? **Answer:** Yes. The factors apply to any target, including Infor cloud products or other ERPs. The assessment checks your readiness, not which target is best. Target choice should follow a fit gap against your requirements. ## Search terms infor xa migration, mapics migration assessment, mapics to cloudsuite, infor xa end of life, mapics erp replacement, infor xa ibm i migration, mapics xa upgrade options, migrate from mapics --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json