Infor VISUAL Upgrade Readiness Checklist (Free)

0%

0 of 36 items complete

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

Download checklist:

Scope and inventory

Record current VISUAL version, service pack and SQL Server versionCRITICALConfirm target version and read the vendor release notesCRITICALList all modules and options in daily useIdentify the business owner for each moduleList all user defined fields and screens in useAgree success criteria and a cutover window with operationsCRITICAL

Customisations and reports

List custom macros, stored procedures, triggers and viewsCRITICALList every Crystal report and note which are actively runMark reports that touch changed tables or columnsRetire reports nobody has run in a yearDocument any direct SQL writes made by outside toolsCRITICALExport custom code to source control

Interfaces and integrations

List all EDI, shipping, CAD and accounting interfacesCRITICALConfirm vendor support for each interface on the target versionRecord file paths, schedules and service accounts usedList scheduled SQL jobs and Windows tasks that touch the databaseCheck barcode, label and shop floor data collection tools

Environment and backups

Take a full verified backup and test a restoreCRITICALBuild a test environment from a recent production copyCRITICALSize server, disk and memory for the target versionConfirm client machine and operating system requirementsCheck database compatibility level and collationDocument licensing and keys needed for the new version

Testing and training

Write test scripts for order to cash, procure to pay and make to stockCRITICALHave each department test with real data in the test environmentCRITICALCompare key report totals before and afterTest every interface end to endTest printing, labels and barcode scanningTrain users on changed screensLog defects and agree who signs off

Cutover and fallback

Freeze changes and stop interfaces before the upgrade windowCRITICALTake a final backup immediately before upgradeCRITICALWrite a rollback plan with a clear go or no go timeCRITICALRun post upgrade smoke tests before opening to usersStaff a floor support rota for the first weekHold a lessons learned review and update runbooks

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

Customisation and report scan

An optional review of your custom code and reports before an upgrade or move.

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

How to use the checklist

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.

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

Why customisations and reports come first

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

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.

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

Frequently Asked Questions

How long does a VISUAL upgrade take?

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?

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?

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?

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.

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.

Talk to an Expert Explore More Free Tools

Related Tools

Other ERPs

More ERP Migration & Selection tools

See all

Infor VISUAL Upgrade Readiness Checklist