# Infor M3 Business Engine upgrade checklist: customizations and integrations > Source: https://netray.co/erp-help/m3-be-upgrade-checklist-customizations-integrations-how-to > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer An M3 upgrade rarely fails on the core transactions. It fails on what surrounds them: customizations, integrations through MI programs and ION, H5 personalizations and scripts, reports and interfaces nobody documented. Inventory those first, test them against a copy of production data, and plan the cutover around your busiest processes. ## Kind how-to ## System infor-m3 ## Erp Infor M3 ## Module M3 Business Engine / Upgrade ## Query Infor M3 Business Engine upgrade checklist ## Alternate Queries - M3 upgrade customizations integrations test plan - how to plan an Infor M3 upgrade - M3 BE upgrade what breaks ## Applies To Infor M3 Business Engine upgrades between 13.x releases and to later versions, on-prem or in a private cloud. Cloud tenants follow Infor's update schedule, so the same inventory applies to update testing. ## Steps ### Upgrade preparation checklist **Items:** - Inventory customizations: Java modifications, custom programs, custom fields and tables, and extension points. Mark which are in use. - Inventory integrations: every MI program, API call, MEC flow, ION connection and file interface with owner and business impact. - Inventory H5 personalizations and scripts per user group, since these depend on the UI and can break across versions. - Inventory reports and document outputs, including forms, labels and any reporting that reads M3 tables directly. - Build a test environment from a recent copy of production and upgrade it first, with real data volumes. - Write regression tests per business process, such as order to cash, procure to pay, MO to stock, period end, with named business owners. - Run the upgrade twice on test, time it and record the issues, so the production cutover has a rehearsed runbook. - Plan rollback and freeze windows around month end and peak shipping. ## Sections ### Customizations: decide keep, replace or retire **Body:** Every customization adds upgrade cost. Before the project, list each one with its owner, why it exists and whether the standard product now covers it. Retiring a customization the standard product replaced is the cheapest upgrade work you will do. For the ones you keep, check against the release notes for changes to the objects they touch. A customization that reads or writes M3 tables directly is the highest risk, because table structures and business rules can change across releases. ### Integrations: the silent failures **Body:** Integrations built on MI programs break when a program changes its inputs or outputs, a field is added as required, or authority rules change. Integrations that read M3 tables with SQL break when columns change. Each should be tested end to end with a business owner confirming the result, not only that the call returned success. ION flows, MEC mappings and file-based interfaces need the same treatment. A flow that runs without error but drops a field is the typical failure, and it often surfaces weeks later in a downstream system. ### H5 personalizations, reports and users **Body:** Personalizations and scripts attached to panels can be affected by UI changes. Test the ones that matter to daily work, such as order entry and shop floor reporting. Also test security: roles, authority and user setup should behave the same, and any change to menu structures needs to be communicated. Reports that depend on column positions or table structures should be run side by side, old versus new, on the same data and compared. Month-end financial output is the one finance will check first. ## Pitfalls - Upgrading production before a full rehearsal on production-sized data. - Testing only the main transactions and not the integrations and reports around them. - Leaving customizations undocumented until the upgrade, when nobody remembers why they exist. - Scheduling cutover across month end or peak shipping. - Checking that an interface returned success instead of that the data landed correctly downstream. ## Ai Angle An assistant that can read your M3 configuration and logs, such as a SyteRay-style accelerator adapted to M3 work or a custom build, can help produce the inventory of customizations and integrations and compare outputs before and after. It does not replace your partner or regression testing, and any code or configuration change stays under your normal change control. ## Faq ### How long does an M3 upgrade take? **Answer:** It depends on customization volume, integrations and testing capacity more than on the core upgrade. Plan months, not weeks, for a customized environment, and base the estimate on a rehearsal rather than a rule of thumb. ### What breaks most often after an upgrade? **Answer:** Integrations and customizations that touch M3 tables or MI programs directly, then reports, then personalizations. Core transactions tend to be stable. This is why the inventory comes before the technical upgrade. ### Can we skip regression testing for a minor update? **Answer:** You can reduce scope, but not skip it. Even small updates change behavior. A short, repeatable regression set per process, owned by the business, makes each update cheaper. ### Should we upgrade or move to the cloud? **Answer:** That is a separate decision with different trade-offs in control, cost and data location. The inventory work is the same either way and is worth doing first, because it tells you how much you would carry to the new platform. ## Search terms m3 upgrade checklist, infor m3 business engine upgrade, m3 customizations upgrade, m3 integration regression test, m3 h5 personalization upgrade, m3 upgrade plan, infor m3 update testing, m3 cutover --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json