Infor M3 Upgrade Test Checklist (Free, Excel/PDF)

0%

0 of 32 items complete

9 critical items still open - these are the highest-risk gaps.

Download checklist:

Preparation

Release notes and known issues for the target version are read and impacts listedCRITICALCustomisations register is up to date: scripts, extensions, reports, interfacesCRITICALTest environment is a recent copy of production data, with sensitive data masked as policy requiresTest scope, owners and exit criteria are agreed in writingBusiness-critical processes are ranked by riskBackup and rollback plan for production is documented and rehearsed

Technical tests

Users can sign in through the expected identity provider, with roles intactCRITICALMenu, bookmarks and personalisations work after upgradeH5 scripts and extensions run without errorsBatch jobs and schedules start and finish in expected timePrinters, document output and email notifications workPerformance of the main programs is acceptable at normal user load

Order to cash

Customer order entry, allocation, pick, delivery and invoice complete end to endCRITICALPricing, discounts and tax calculate correctly on a sample of real ordersCredit check and customer blocks behave as beforeReturns and credit notes workCustomer order statuses move as documented for your flow

Procure to pay and inventory

Purchase order, receipt and supplier invoice matching complete end to endCRITICALStock transactions, transfers and counts post correctlyReplenishment and planning runs produce expected proposalsLot and serial tracking works on a sample item

Production

Manufacturing order creation, release, reporting and completion workCRITICALMaterial issue and receipt backflush give expected quantitiesCosting and variance postings are reasonable against previous period

Finance and reporting

Posting to general ledger and subledger reconcilesCRITICALPeriod close steps run in the test environmentStandard and custom reports return the same totals as before

Integrations and go-live

Inbound and outbound EDI and MEC flows tested with partner or simulatorCRITICALAPI consumers and middleware are tested against the new versionGo and no-go meeting held with sign-off from process ownersCRITICALHypercare roster and issue triage process are in placeUsers have been told the downtime window and any changed screens

Do not go live with any critical item unchecked. Record a defect and a named owner for each unchecked item.

Upgrade regression approach

Optional: a short outline of how real transactions can be replayed to compare results before and after an M3 upgrade.

Optional. The tool and every export work without this. No spam.

How to use the checklist

Assign each group to an owner, tick items as they pass and attach evidence such as screenshots or document numbers. Critical items must pass before go-live. Add rows for your own flows: consignment, projects, rental, quality inspection or any process unique to your business. Export the completed list as PDF or Excel for the go and no-go meeting.

Where upgrades usually break

The usual suspects are customisations that depend on screen structure, integrations that depend on message formats or API versions, custom reports with changed tables and security roles that no longer cover new programs. Prepare by listing all customisations and interfaces first and testing those with real data. Standard processes tend to work, but still need a sample test, particularly where your settings are unusual.

Scripts and extensions
Integrations and EDI flows
Custom reports and queries
Security roles and menus
Batch jobs and schedules

Common mistakes

Testing only with a happy path, using a stale or tiny dataset, and letting users test on their own without scripts are the most common errors. Another is leaving finance until last: reconciliation problems found in the last week are painful. Start early with a first cycle to find issues, then a clean second cycle for sign-off.

Frequently Asked Questions

How many test cycles does an M3 upgrade need?

Two is the practical minimum: a first cycle to find problems and a second clean cycle for sign-off. Complex landscapes with many integrations often add a third rehearsal for cut-over timing.

Who should perform the tests?

Business process owners and power users, supported by consultants. Developers test technical items, but only users can confirm that an order, a manufacturing order or a close step behaves as the business expects.

Do I need to test standard functions?

Yes, with a sample. Standard functions work in general, but your settings and data are unique. Use a small set of real transactions per process to find configuration surprises.

What belongs in the go and no-go decision?

Status of critical tests, open defects with severity, readiness of rollback, hypercare staffing and sign-off from process owners. If a critical test fails with no workaround, the answer is no-go.

Netray can help build a regression set from your real M3 transactions and compare outputs before and after an upgrade, with your team approving the findings.

Talk to an Expert Explore More Free Tools

Related Tools

Infor M3 & CloudSuite

More Infor M3 & CloudSuite tools

See all

Infor M3 Upgrade Test Checklist: Technical, Process and Integration Tests