Infor M3 13.x On-Premises Upgrade Readiness Assessment
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.
1. Is every MAK (M3 Adaptation Kit) Java modification inventoried with owner, purpose and changed programs?
Modifications not on the list are the ones that break silently after an upgrade.
2. What share of MAK modifications could be replaced by configuration, H5 scripts, MEC or standard functions?
3. How are users working in the client today?
Smart Office scripts and mashups need rework if you move users to H5.
4. Are MEC maps listed with partners, message types and a repeatable test?
5. How healthy is the Lifecycle Manager (LCM) setup?
LCM manages the installation, fixes and grid applications of an on-prem M3 13.x environment.
6. Are your database, Java and operating system versions on the target release's supported list?
Check the target release's system requirements document, not memory.
7. Are integrations through MI programs and ION documented, including which MI transactions each uses?
8. Do you have test scripts for key flows such as order entry (OIS100), purchasing (PPS200) and manufacturing orders (PMS100)?
9. Are data volumes and archiving under control?
Large history tables lengthen database conversion and testing.
10. Will key users be available for testing during the upgrade window?
11. Is there a tested rollback plan for the production cutover?
How to use it
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
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.
- 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
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
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.
Frequently Asked Questions
What is Infor M3?
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?
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?
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?
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.
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.
Related Tools
Infor M3 LCM Fix and Cumulative Update Checklist
Checklist for applying M3 Business Engine fixes and cumulative updates on an on-prem M3 13.x system through Lifecycle Manager, including MAK retrofit and regression checks.
Infor M3 & CloudSuiteInfor M3 Smart Office to H5 Script Migration Checklist
Checklist for moving Infor Smart Office scripts, mashups, shortcuts and personalizations to the M3 H5 client: inventory, classify, rewrite, test and decommission.
Infor M3 & CloudSuiteInfor M3 Upgrade Test Checklist
A structured test checklist for an M3 upgrade or update, covering technical checks, core processes, integrations and cut-over.
Infor M3 & CloudSuiteInfor M3 Cloud Migration Readiness Assessment
Ten questions to gauge how ready an on-prem M3 estate is for a move to Infor CloudSuite, with prioritized next steps.
Infor M3 & CloudSuiteInfor M3 MI API and ION API Gateway Security Checklist
Security checklist for on-prem M3 13.x integrations using MI programs over REST and the ION API gateway: accounts, authorization, transport, monitoring and lifecycle.
More Infor M3 & CloudSuite tools
See all- Infor M3 Program Reference (MMS001, OIS100, PMS100)
- Infor M3 MI API Transaction Call Generator
- Infor M3 Customer Order Status Tracking Worksheet
- Infor M3 Item Master Upload Worksheet
- Infor M3 MEC Mapping Design Template
- Infor M3 H5 Script Review Checklist
- Infor M3 Facility and Warehouse Structure Worksheet
- Infor M3 Fit-Gap Analysis Worksheet
- Infor M3 Interface and Integration Inventory Worksheet
Keep exploring
Free tools
- Infor M3 BE Upgrade Modification Retrofit Effort CalculatorSize the retrofit of MAK modifications, H5 scripts, MEC maps and custom list APIs plus test cycles for an on-prem M3 BE 13.x upgrade.
- Infor M3 Cloud Migration Readiness AssessmentTen questions to gauge how ready an on-prem M3 estate is for a move to Infor CloudSuite, with prioritized next steps.
- Infor M3 Upgrade Test ChecklistA structured test checklist for an M3 upgrade or update, covering technical checks, core processes, integrations and cut-over.
ERP fixes and how-tos
- Infor M3 Business Engine upgrade checklist: customizations and integrationsPractical checklist for an Infor M3 Business Engine upgrade: inventory customizations, integrations, H5 personalizations, reports and a regression test plan.
- How to Add a Personalization Script to an M3 H5 PanelAdd a JavaScript personalization script to an M3 H5 panel using the MForms API: setup, panel/field events, save and deploy, and common scripting mistakes.
- Private AI Layer for Infor M3 On-Prem: Reference ArchitectureReference architecture to add a private AI assistant to Infor M3 on-prem: data access paths, retrieval, permissions, sizing and rollout, no cloud needed.
Guides
- Infor M3 Upgrade: Risk Assessment FrameworkAssess risks before upgrading Infor M3. Customization impact analysis, integration compatibility testing, and go/no-go decision framework.
- Infor M3 Upgrade Path Planning: From Assessment to Go-Live with Minimal DisruptionPlan your Infor M3 version upgrade strategy. Assess customizations, test regression, manage data migration, and minimize downtime for M3 13.x to 2024.x upgrades.
- Infor M3 Upgrade and CloudSuite Migration PlanningInfor M3 upgrade and CloudSuite migration guide: modification inventory, extensibility rework, data strategy, testing waves, and 9 to 18 month timelines.
Integrations
- How to use ChatGPT with Infor M3How to use ChatGPT with Infor M3: exports, custom GPT actions over the M3 API or ION, enterprise data controls, and when a private model is the safer choice.
- How to add an AI chatbot to Infor M3How to add an AI chatbot to Infor M3 for staff and customers: grounded in M3 data via the API, embedded in a portal or Teams, and able to run fully on-prem.