# Infor M3 13.x On-Premises Upgrade Readiness Assessment > Source: https://netray.co/tools/infor-m3-13-on-prem-upgrade-readiness-assessment > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer Score how ready your on-prem Infor M3 environment is for an upgrade to a newer 13.x release, across modifications, client scripts, integrations, infrastructure and testing. ## Category infor-cloudsuite ## Erp Infor M3 ## Audience - M3 technical consultant - M3 system administrator - IT manager ## Tool **Kind:** assessment **Questions:** #### Is every MAK (M3 Adaptation Kit) Java modification inventoried with owner, purpose and changed programs? **Help:** Modifications not on the list are the ones that break silently after an upgrade. **Options:** ##### Yes, complete and current **Score:** 3 ##### Mostly, a few unknowns **Score:** 2 ##### Partial list only **Score:** 1 ##### No inventory **Score:** 0 #### What share of MAK modifications could be replaced by configuration, H5 scripts, MEC or standard functions? **Options:** ##### Assessed, and most can be replaced **Score:** 3 ##### Assessed, some can be replaced **Score:** 2 ##### Not assessed yet **Score:** 1 ##### Not assessed and many mods **Score:** 0 #### How are users working in the client today? **Help:** Smart Office scripts and mashups need rework if you move users to H5. **Options:** ##### All users on H5, no Smart Office scripts **Score:** 3 ##### Mostly H5, a few Smart Office scripts left **Score:** 2 ##### Mixed, many Smart Office scripts in use **Score:** 1 ##### Mainly Smart Office with unknown scripts **Score:** 0 #### Are MEC maps listed with partners, message types and a repeatable test? **Options:** ##### Yes, with test files for each map **Score:** 3 ##### Listed, tests for the main maps **Score:** 2 ##### Listed, no tests **Score:** 1 ##### Not listed **Score:** 0 #### How healthy is the Lifecycle Manager (LCM) setup? **Help:** LCM manages the installation, fixes and grid applications of an on-prem M3 13.x environment. **Options:** ##### Healthy, fix levels known per environment **Score:** 3 ##### Working, fix levels partly documented **Score:** 2 ##### Working but fragile or out of date **Score:** 1 ##### Problems or nobody knows it well **Score:** 0 #### Are your database, Java and operating system versions on the target release's supported list? **Help:** Check the target release's system requirements document, not memory. **Options:** ##### Checked, all supported **Score:** 3 ##### Checked, minor upgrades needed **Score:** 2 ##### Checked, major platform upgrade needed **Score:** 1 ##### Not checked **Score:** 0 #### Are integrations through MI programs and ION documented, including which MI transactions each uses? **Options:** ##### Yes, per interface **Score:** 3 ##### Main interfaces only **Score:** 2 ##### Partly, in people's heads **Score:** 1 ##### No **Score:** 0 #### Do you have test scripts for key flows such as order entry (OIS100), purchasing (PPS200) and manufacturing orders (PMS100)? **Options:** ##### Yes, written and run in the last year **Score:** 3 ##### Written but out of date **Score:** 2 ##### Only informal key-user testing **Score:** 1 ##### None **Score:** 0 #### Are data volumes and archiving under control? **Help:** Large history tables lengthen database conversion and testing. **Options:** ##### Archiving in place, volumes known **Score:** 3 ##### Volumes known, no archiving **Score:** 2 ##### Some very large tables, not assessed **Score:** 1 ##### Unknown **Score:** 0 #### Will key users be available for testing during the upgrade window? **Options:** ##### Yes, time agreed with their managers **Score:** 3 ##### Likely, not agreed **Score:** 2 ##### Only partly, peak season clash **Score:** 1 ##### No **Score:** 0 #### Is there a tested rollback plan for the production cutover? **Options:** ##### Yes, restore rehearsed with timings **Score:** 3 ##### Written, not rehearsed **Score:** 2 ##### Backups only **Score:** 1 ##### No plan **Score:** 0 **Bands:** #### Ready **Min:** 80 **Max:** 100 **Verdict:** Your environment is well understood and the upgrade can be planned with normal contingency. **Recommendations:** - Book the test environment build and the first test cycle - Run one full rehearsal of the production cutover with timings - Retire the modifications you already marked as replaceable before the upgrade, not after - Freeze new MAK development from the start of the final test cycle #### Ready with gaps **Min:** 60 **Max:** 79 **Verdict:** The upgrade is feasible, but specific gaps will cost time unless you close them first. **Recommendations:** - Close the lowest-scoring questions first and assign each an owner and date - Complete the MAK and Smart Office script inventory before estimating - Write or refresh test scripts for the order, purchase and manufacturing flows - Confirm platform support for the target release in writing #### Significant gaps **Min:** 35 **Max:** 59 **Verdict:** Starting now would mean discovering scope during testing. Spend a short readiness phase first. **Recommendations:** - Run a 4 to 8 week readiness phase: inventory mods, scripts, MEC maps and interfaces - Have someone who knows LCM and the grid review the environment - Decide the future of each Smart Office script and MAK mod before the project plan - Plan platform upgrades (database, OS, Java) as a separate step if needed - Agree key-user time with business managers #### Not ready **Min:** 0 **Max:** 34 **Verdict:** Too much is unknown to plan an upgrade safely. **Recommendations:** - Build the inventory of modifications, scripts, maps and integrations first - Stabilise the current environment and document fix levels - Set up a test environment that can be refreshed from production - Reassess with this tool after the inventory is complete ## Content **Intro:** This assessment scores how ready an on-prem Infor M3 13.x environment is for an upgrade to a newer 13.x release. It focuses on the things that actually drive upgrade effort: MAK modifications, Smart Office and H5 scripts, MEC maps, LCM health, platform support, testing and rollback. **Sections:** #### How to use it **Body:** Answer the 11 questions with your M3 technical lead and the person who runs LCM. Be honest: the score is for planning, not for a steering committee slide. The result is a percentage of the maximum score and falls in one of four bands. Each band lists what to do next. Export the result to PDF and keep the answers, then rerun the assessment after closing gaps. This tool is for on-prem upgrades within 13.x. For test steps use the upgrade test checklist, and for a move to CloudSuite use the cloud migration readiness assessment. #### What drives upgrade effort in M3 13.x **Body:** On-prem M3 13.x runs the M3 Business Engine on the Infor Grid, installed and maintained through Lifecycle Manager. Java modifications are built with MAK, and every modified object that Infor changes in the new release has to be merged and retested. Client-side changes live in H5 scripts and, on older setups, Smart Office scripts and mashups. Integrations use MI programs, MEC maps and ION. Effort scales with the number of modifications touched by the release, the number of scripts and maps, and the quality of your tests, much more than with user count. **Bullets:** - MAK: Java modifications to M3 BE programs - LCM: installation, fixes and grid application management - H5 and Smart Office: client scripts and personalizations - MEC and MI: integrations and file maps #### How to read the result **Body:** 80 and above means the environment is known and the upgrade can be planned normally. 60 to 79 means feasible, but close the low-scoring questions first or they will surface as test delays. 35 to 59 means run a readiness phase before committing to dates. Below 35 means the inventory does not exist yet and any estimate is a guess. The questions with a zero matter more than the total: a missing rollback plan or no MAK inventory is a blocker even when the overall score is high. #### Common mistakes **Body:** Teams often underestimate Smart Office: scripts written years ago by a departed consultant still run critical panels. Others assume MEC maps will work unchanged and skip them in testing. Platform support is another trap: check the target release's system requirements for database, Java and operating system versions before you plan, and do not rely on what worked for the current release. Finally, do not take end-of-support dates from forums; confirm them with Infor for your contract. **Cta:** If you want your M3 team to ask in plain English which modifications and scripts touch a given program, we can set that up on your own servers. **Faq:** #### What is Infor M3? **Answer:** Infor M3 is Infor's ERP for process, distribution and fashion industries and asset-heavy manufacturers. The M3 Business Engine runs programs such as OIS100 (customer order), PPS200 (purchase order) and PMS100 (manufacturing order). It is offered as CloudSuite in Infor's cloud and as 13.x for on-prem installations. #### Is there an Infor M3 velocity implementation guide for upgrades? **Answer:** Velocity is Infor's methodology for CloudSuite implementations, documented in Infor's own materials. For an on-prem 13.x upgrade you still need your own readiness view: modifications, scripts, maps, platform and testing. This assessment covers that and can sit alongside whatever method your partner uses. #### Do Smart Office scripts work after an M3 upgrade? **Answer:** Scripts usually survive within the same client, but any panel or field change in the new release can break them, and they do not run in H5 at all. If users are moving to H5 as part of the upgrade, each Smart Office script must be rewritten, replaced or retired. Inventory them early. #### How long does an M3 13.x on-prem upgrade take? **Answer:** It depends mainly on modifications, scripts, maps and test readiness, not on user numbers. A well-documented environment with few mods can be a matter of weeks of technical work plus test cycles; a heavily modified one with no tests takes months. Use this assessment to find out which you have before estimating. ## Search terms infor m3 velocity implementation guide, what is infor m3, infor m3 on premise, infor m3 on prem, infor m3 update, infor m3 technical consultant, infor m3 customization, infor smart office m3 --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json