Infor M3 BE Upgrade Modification Retrofit Effort Calculator
This calculator estimates the retrofit and test effort for upgrading an on-prem Infor M3 Business Engine 13.x installation to a later 13.x level when you carry Java modifications made with MAK. It separates modification retrofit from scripts, MEC maps, custom APIs and testing, so you can see what drives the plan.
Your numbers
Your results
Hours per object are assumptions; replace them with figures from your last fix or upgrade. Data migration, infrastructure and training are not included.
Total effort (hours) vs complex MAK modifications
Sweeps MAK modifications, complex from 0 to 40, holding your other inputs fixed.
Get your modification inventory reviewed
Send your MAK, H5, MEC and API inventory and we will review the retrofit estimate and which mods could be replaced.
Optional. The tool and every export work without this. No spam.
Why MAK modifications dominate
Modifications built with MAK (the M3 Adaptation Kit) change the M3 Java programs themselves. When the upgrade delivers new versions of those programs, each modified program has to be compared and merged with the new standard code, rebuilt and tested; Lifecycle Manager tracks the fixes and modifications on the installation. H5 scripts, MEC maps and custom list APIs sit outside the standard programs, so they usually only need checking against changed fields, panels and API transactions. That is why a few complex MAK mods often cost more than dozens of scripts.
- Retrofit = simple x h + medium x h + complex x h
- Scripts, maps and APIs = H5 x h + MEC x h + APIs x h
- Total = retrofit + scripts/maps/APIs + test cycles x hours per cycle
How to build the inventory
List the modified programs from MAK and the modification and fix records in Lifecycle Manager for the installation, and classify each by size of change: a few lines in one program is simple, changes across several programs or panels medium, new logic or database changes complex. Export the H5 scripts deployed in H5 administration, the MEC agreements and maps in use, and custom MDBREADMI list transactions or other custom APIs. Count only objects still used in production; retiring dead mods is the cheapest retrofit.
Worked example
20 simple, 10 medium and 4 complex mods at 8, 24 and 60 hours give 640 hours of retrofit. 30 H5 scripts at 2 hours, 25 MEC maps at 3 hours and 15 custom APIs at half an hour add 142.5 hours. Three test cycles of 120 hours add 360. Total about 1,143 hours, about 8.2 weeks for 4 people at 35 hours. MAK mods are 56 percent of the effort; the chart shows each extra complex mod adding 60 hours.
Replacing mods instead of retrofitting
Before retrofitting, ask whether each modification can become an H5 script, an MEC flow, a custom list API or a configuration change. Those survive upgrades with much less work and match the extensibility approach Infor recommends for M3. Replacing a complex mod costs more once but removes it from every future upgrade.
Frequently Asked Questions
What is Infor M3?
Infor M3 is an ERP for manufacturing and distribution, built on the M3 Business Engine (Java) with programs such as MMS001 for items and OIS100 for customer orders. It runs on-prem as M3 13.x or as the Infor-hosted CloudSuite. On-prem installations can carry Java modifications made with MAK.
What does an Infor M3 technical consultant do in an upgrade?
They inventory and retrofit MAK modifications, check H5 scripts, MEC maps and custom APIs against the new level, apply fixes with Lifecycle Manager, and support test cycles. The share of their time spent on MAK retrofit is what this calculator helps you estimate.
How many test cycles should an M3 upgrade plan include?
Plan at least two full cycles plus a final regression before go-live; three is common when modifications are numerous. Each cycle covers order to cash, procure to pay, manufacturing and finance with the integrations running. Use your previous upgrade's hours per cycle if you have them.
Do H5 scripts need rework in an M3 upgrade?
Usually less than MAK mods, but they read panel fields and call APIs, so changed panels, field names or API transactions can break them. Test each script on the target level and fix the ones that fail, which is why a small number of hours per script is included.
If you want users to ask M3 about orders, stock and items in plain English on your own servers, without adding new modifications, we can set that up.
Related Tools
Infor 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 H5 Script Review Checklist
A review checklist for H5 Client scripts covering design, coding, security, testing and upgrade risk.
Infor M3 & CloudSuiteInfor M3 MEC Mapping Design Template
A fill-in design document for an M3 Enterprise Collaborator mapping, from partner and flow to field rules and error handling.
Developer ToolsInfor M3 EXPORTMI Extraction Call Volume Calculator
Plan paged extracts from M3 through EXPORTMI or Lst transactions: calls per run, elapsed minutes and daily call volume under a record cap.
Infor M3 & CloudSuiteInfor M3 ION BOD Message Volume Calculator
Size the BOD volume M3 13.x publishes through ION from your order lines and master data changes, with peak hour load and retention storage.
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 Facility and Warehouse Structure Worksheet
- Infor M3 Fit-Gap Analysis Worksheet
- Infor M3 Interface and Integration Inventory Worksheet
- Infor M3 Functional Specification Template
- Infor M3 User Acceptance Test Script Template
Keep exploring
Free tools
- Infor M3 13.x On-Premises Upgrade Readiness AssessmentScore 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.
- Infor M3 H5 Script Review ChecklistA review checklist for H5 Client scripts covering design, coding, security, testing and upgrade risk.
- 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.
- How to Build a Grid Mapping in M3 Enterprise Collaborator (MEC)Set up a MEC grid mapping step by step: collection, grid transform, and delivery through M3 API, plus where most EDI/B2B integration mappings break.
Guides
- 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.
- Infor M3 Customization vs Modification: A Decision FrameworkInfor M3 customization vs modification strategy: when to personalize, extend by API, or build a MAK mod, and how to control lifetime retrofit cost per change.
- Infor M3 Upgrade: Risk Assessment FrameworkAssess risks before upgrading Infor M3. Customization impact analysis, integration compatibility testing, and go/no-go decision framework.