# Infor VISUAL Upgrade Readiness Checklist

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

## Short answer

A grouped checklist covering backups, customisations, reports, interfaces, testing and cutover for a VISUAL upgrade.

## Category

erp-migration

## Erp

Infor VISUAL

## Industry

Discrete Manufacturing

## Audience

- VISUAL administrator
- IT manager
- Project manager

## Tool

**Kind:** checklist

**Scoring Note:** Tick what is complete. Critical items should all be done before you schedule the production cutover.

**Groups:**

#### Scope and inventory

**Items:**

**Text:** Record current VISUAL version, service pack and SQL Server version

**Critical:** true

**Text:** Confirm target version and read the vendor release notes

**Critical:** true

List all modules and options in daily use

Identify the business owner for each module

List all user defined fields and screens in use

**Text:** Agree success criteria and a cutover window with operations

**Critical:** true

#### Customisations and reports

**Items:**

**Text:** List custom macros, stored procedures, triggers and views

**Critical:** true

List every Crystal report and note which are actively run

Mark reports that touch changed tables or columns

Retire reports nobody has run in a year

**Text:** Document any direct SQL writes made by outside tools

**Critical:** true

Export custom code to source control

#### Interfaces and integrations

**Items:**

**Text:** List all EDI, shipping, CAD and accounting interfaces

**Critical:** true

Confirm vendor support for each interface on the target version

Record file paths, schedules and service accounts used

List scheduled SQL jobs and Windows tasks that touch the database

Check barcode, label and shop floor data collection tools

#### Environment and backups

**Items:**

**Text:** Take a full verified backup and test a restore

**Critical:** true

**Text:** Build a test environment from a recent production copy

**Critical:** true

Size server, disk and memory for the target version

Confirm client machine and operating system requirements

Check database compatibility level and collation

Document licensing and keys needed for the new version

#### Testing and training

**Items:**

**Text:** Write test scripts for order to cash, procure to pay and make to stock

**Critical:** true

**Text:** Have each department test with real data in the test environment

**Critical:** true

Compare key report totals before and after

Test every interface end to end

Test printing, labels and barcode scanning

Train users on changed screens

Log defects and agree who signs off

#### Cutover and fallback

**Items:**

**Text:** Freeze changes and stop interfaces before the upgrade window

**Critical:** true

**Text:** Take a final backup immediately before upgrade

**Critical:** true

**Text:** Write a rollback plan with a clear go or no go time

**Critical:** true

Run post upgrade smoke tests before opening to users

Staff a floor support rota for the first week

Hold a lessons learned review and update runbooks

## Content

**Intro:** A VISUAL upgrade usually fails on details around the edges: forgotten reports, an interface nobody owned or a backup that was never tested. This checklist groups the work so you can see readiness at a glance, with critical items flagged.

**Sections:**

#### How to use the checklist

**Body:** Work through the groups in order. Scope and inventory should be finished first, because every later group depends on knowing what you actually have. Tick items as they are completed and export the list for your project plan or steering meeting. Give each critical item a named owner and a date.

**Bullets:**

- Assign an owner per critical item
- Review progress weekly
- Do not schedule cutover with critical items open

#### Why customisations and reports come first

**Body:** Standard screens upgrade predictably. The risk lies in what you added: stored procedures, triggers, user defined fields, macros and years of Crystal reports. A change to a table or column can break a report quietly, producing wrong numbers rather than errors. Inventorying and testing these items against a copy of production is the best protection.

#### Common mistakes

**Body:** Teams often test only the screens they use daily and skip month end, year end and rarely run reports. Others run the test environment against fake data and miss problems that only appear with real volume. Finally, many plans have no rollback decision time. Agree in advance when you will stop and restore instead of pushing on.

**Bullets:**

- Include month end processes in testing
- Test with a recent production copy
- Set a rollback decision point
- Verify the restore, not just the backup

**Cta:** If you want a second pair of eyes on your upgrade plan or help scanning custom code and reports for risk, we can do that review.

**Faq:**

#### How long does a VISUAL upgrade take?

**Answer:** It depends on the size of the database, the number of customisations and the testing you do. The technical upgrade can take hours, while planning and user testing take weeks. Do not compress testing to meet a date.

#### Should we upgrade or move to a cloud product?

**Answer:** That is a business decision. An upgrade keeps familiar behaviour and lower change, while a move may add capability but needs more migration work. Compare total cost and risk over several years before choosing.

#### Do we need a test environment?

**Answer:** Yes. Restoring a recent production copy to a separate server lets you rehearse the upgrade, time it and test reports with real data, without any risk to live operations.

#### What is the biggest risk?

**Answer:** Undocumented customisations and interfaces. They are invisible until something fails after go live. A thorough inventory and end to end interface testing reduce this risk more than any other step.

## Search terms

infor visual upgrade checklist, visual manufacturing upgrade plan, visual manufacturing version upgrade, erp upgrade readiness checklist, visual manufacturing testing checklist, visual upgrade cutover

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