# Infor EAM 11.x to HxGN EAM 12 Upgrade Checklist

> Source: https://netray.co/tools/infor-eam-11-to-hxgn-eam-12-upgrade-checklist
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

A 40-item checklist for on-premises Infor EAM 11.x customers upgrading to HxGN EAM 12, from customisation inventory to integration retests and cutover.

## Category

maintenance

## Erp

Infor EAM

## Audience

- EAM administrator
- IT project manager
- Integration developer

## Tool

**Kind:** checklist

**Groups:**

#### 1. Inventory the current EAM 11.x system

**Items:**

**Text:** Record the exact EAM version and patch level from the About screen and the server install

**Critical:** true

Record database platform and version (Oracle or SQL Server), character set and size

Record the application server, Java and operating system versions on every EAM server

**Text:** List screen designer changes, custom tabs and user defined fields in use

**Critical:** true

List Flex SQL rules, database triggers, custom views and stored procedures

List custom reports (BIRT, Cognos or other) and the owners who still use them

List Dataspies and Grid Designer grids shared across users

**Text:** List every interface: web service callers, ION BODs, Data Lake extracts, file imports, PLC or meter feeds

**Critical:** true

List mobile usage (which mobile app or browser, how many users, offline needs)

#### 2. Compatibility with HxGN EAM 12

**Items:**

**Text:** Check the HxGN EAM 12 installation guide for supported database, operating system and application server versions

**Critical:** true

Plan any database or OS upgrade as a separate step before the EAM upgrade where required

Confirm supported browsers for all users; old Internet Explorer compatibility settings are a common cause of incompatible browser messages

Confirm the authentication approach (LDAP, SSO with SAML or OIDC) supported in your target release

Confirm licences and the support contract are with Hexagon for the target release

Check that report tools and BIRT designer versions match the target release

#### 3. Integrations and APIs

**Items:**

**Text:** Map each SOAP web service call in use to the target release and test it unchanged first

**Critical:** true

Evaluate the REST web services for new integrations using the Swagger documentation on your server

Set required REST header parameters such as tenant and organization in every client

Retest ION BOD mappings and Data Lake publishing for work orders, equipment and parts

Retest incremental extracts that filter on last saved timestamps (for example EVT_LASTSAVED)

Retest outbound email, alerts and workflow notifications

Update integration service accounts, passwords and certificates for the new servers

#### 4. Data and test

**Items:**

**Text:** Copy production to a test environment and run the upgrade there first

**Critical:** true

**Text:** Capture record counts before and after for R5EVENTS, R5OBJECTS, R5PARTS, R5STOCK and R5TRANSACTIONS

**Critical:** true

Compare stock quantities by store and part between old and upgraded test copies

Test PM work order generation against a known PM schedule

Test stores: issue to work order, return, receipt and stock take

Test purchasing: requisition to purchase order to receipt and invoice match

Test approvals and status changes for work orders, requisitions and purchase orders

Run every custom report and Flex SQL rule and record failures

#### 5. Users and training

**Items:**

Review roles, menus and screen permissions after the upgrade

Give planners, technicians and storeroom users a short UI changes session on the test system

Update work instructions and screenshots used for onboarding

Nominate super users per site to answer first-line questions

#### 6. Cutover and after go-live

**Items:**

**Text:** Agree a transaction freeze window and communicate it to all sites

**Critical:** true

**Text:** Take and verify a full database and application backup before the upgrade

**Critical:** true

Write and rehearse a rollback plan with a decision deadline

Re-enable interfaces one by one and check the first messages end to end

Monitor PM generation, interfaces and performance daily for the first two weeks

Close the project with an updated system inventory for the next upgrade

**Scoring Note:** Critical items are the ones that most often cause rollbacks or lost data. Do not set a cutover date until every critical item is ticked on a full rehearsal in the test environment.

## Content

**Intro:** A practical checklist for on-premises customers moving from Infor EAM 11.x to HxGN EAM 12, the release line Hexagon has developed since acquiring Infor EAM in 2021. It covers inventory, compatibility, integrations, data tests, users and cutover.

**Sections:**

#### How to use it

**Body:** Work through the groups in order. The inventory in group 1 drives everything else: every customisation, report and interface you list becomes a test case in group 4. Tick items as you complete them and export the list to Excel or PDF for the project file. Most of the effort in an EAM upgrade is not the upgrade scripts but retesting customisations and integrations, so do not skip the interface list. Run the full sequence at least once in a test copy of production before you set a cutover date.

**Bullets:**

- Assign an owner to each critical item.
- Keep before and after record counts in the project file as evidence.

#### What changed with Hexagon

**Body:** Hexagon acquired the Infor EAM business in 2021 and continues the product as HxGN EAM, with documentation now published on the Hexagon documentation site rather than Infor's. For on-premises customers the database schema still uses the R5 tables, so most SQL, Dataspies and reports carry over, but support, downloads, licences and release notes now come from Hexagon. Check which entity your support contract is with before planning, and use the HxGN EAM 12 installation and upgrade guides for your target release rather than older Infor EAM guides.

#### Integrations and the REST API

**Body:** HxGN EAM offers REST web services documented with Swagger (OpenAPI) on the EAM server, alongside the older SOAP web services many 11.x interfaces use. Do not rewrite working SOAP interfaces during the upgrade; test them first, then move to REST as a separate project. REST calls carry header parameters such as tenant and organization, which multi-organization sites must set correctly or receive empty or rejected responses. ION and Data Lake integrations should be retested with real work order, equipment and part changes, including extracts that rely on last saved timestamps such as EVT_LASTSAVED.

#### Data checks that catch real problems

**Body:** Record counts for R5EVENTS, R5OBJECTS, R5PARTS, R5STOCK and R5TRANSACTIONS before and after the test upgrade are a cheap first gate. Then compare stock by store and part, because stores issues are where users notice errors first. Generate PM work orders from a known schedule on both versions and compare the results. Run every custom report and Flex SQL rule, since these break most often when columns or screens change. Keep the failed list short and fixed before the production run.

**Cta:** If you want an AI assistant over your upgraded HxGN EAM data that runs on your own servers, we can scope it alongside the upgrade.

**Faq:**

#### Was Infor EAM sold to Hexagon?

**Answer:** Yes. Hexagon acquired Infor's EAM business in 2021. The product continues as HxGN EAM, and new releases, documentation and support for it come from Hexagon. Existing Infor EAM installations keep the same core data model.

#### Why does Infor EAM say the browser is incompatible?

**Answer:** Older EAM releases check the browser and its compatibility mode. The message usually appears when users run an unsupported browser version or Internet Explorer compatibility settings. Check the supported browser list for your exact release and remove compatibility mode settings pushed by group policy.

#### Does HxGN EAM have a REST API?

**Answer:** Yes. HxGN EAM provides REST web services documented with Swagger on the application server, in addition to SOAP web services. Requests include header parameters such as tenant and organization. Check the REST web services guide for your release for available resources and authentication.

#### How long does an EAM 11 to 12 upgrade take?

**Answer:** It depends mostly on customisations and interfaces, not on database size. A site with few interfaces may finish test and production runs in weeks; a multi-site installation with many Flex SQL rules, reports and ION integrations often needs a few months including test cycles.

## Search terms

infor eam hexagon, infor eam sold to hexagon, hxgn eam 12 upgrade, infor eam upgrade checklist, infor eam implementation guide, infor10 eam incompatible browser, infor eam api, hxgn eam rest api

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json