# Infor VISUAL Upgrade Cutover Window Calculator

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

## Short answer

Estimate the downtime and rollout effort of moving Infor VISUAL to a new version: database window, client installs and retesting macros and reports.

## Category

other-erp

## Erp

Infor VISUAL

## Audience

- ERP administrator
- IT manager
- Project manager

## Tool

**Kind:** calculator

**Inputs:**

#### Database size

**Key:** gb

**Type:** number

**Default:** 60

**Min:** 1

**Step:** 5

**Unit:** GB

#### Backup throughput

**Key:** backup

**Type:** number

**Default:** 200

**Min:** 10

**Step:** 10

**Unit:** MB/s

**Help:** From your last full backup: size divided by duration.

#### Restore-to-test throughput

**Key:** restore

**Type:** number

**Default:** 150

**Min:** 10

**Step:** 10

**Unit:** MB/s

**Help:** Used for the rehearsal estimate.

#### Database upgrade minutes per GB

**Key:** min_per_gb

**Type:** number

**Default:** 2

**Min:** 0.1

**Step:** 0.1

**Unit:** min/GB

**Help:** Measure in a rehearsal on a restored copy. Do not guess this.

#### Workstations needing the new client

**Key:** ws

**Type:** number

**Default:** 80

**Min:** 0

**Step:** 5

**Unit:** PCs

#### Minutes per manual workstation install

**Key:** min_ws

**Type:** number

**Default:** 10

**Min:** 1

**Step:** 1

**Unit:** minutes

#### Technicians in parallel

**Key:** techs

**Type:** number

**Default:** 3

**Min:** 1

**Step:** 1

**Unit:** people

#### Workstations pushed by deployment tool

**Key:** pushed_pct

**Type:** slider

**Default:** 50

**Min:** 0

**Max:** 100

**Step:** 5

**Unit:** %

#### Macros and custom reports to retest

**Key:** items

**Type:** number

**Default:** 40

**Min:** 0

**Step:** 1

**Unit:** items

#### Minutes to retest each item

**Key:** min_item

**Type:** number

**Default:** 15

**Min:** 1

**Step:** 1

**Unit:** minutes

#### Testers in parallel

**Key:** testers

**Type:** number

**Default:** 2

**Min:** 1

**Step:** 1

**Unit:** people

#### Contingency on database window

**Key:** buffer_pct

**Type:** slider

**Default:** 20

**Min:** 0

**Max:** 100

**Step:** 5

**Unit:** %

**Outputs:**

#### Pre-upgrade backup

**Key:** backup_min

**Expr:** gb * 1024 / backup / 60

**Format:** minutes

#### Database downtime window

**Key:** db_window_hours

**Expr:** (backup_min + gb * min_per_gb) / 60 * (1 + buffer_pct / 100)

**Format:** hours

**Primary:** true

**Description:** Backup plus database upgrade, with contingency.

#### Rehearsal run (restore plus upgrade)

**Key:** rehearsal_hours

**Expr:** (gb * 1024 / restore / 60 + gb * min_per_gb) / 60

**Format:** hours

#### Manual client rollout

**Key:** client_hours

**Expr:** ws * (1 - pushed_pct / 100) * min_ws / techs / 60

**Format:** hours

#### Macro and report retest

**Key:** retest_hours

**Expr:** items * min_item / testers / 60

**Format:** hours

#### Total elapsed cutover

**Key:** total_elapsed_hours

**Expr:** db_window_hours + max(client_hours, retest_hours)

**Format:** hours

**Primary:** true

**Description:** Client rollout and retesting run in parallel after the database is upgraded.

**Chart:**

#### Client rollout and total cutover vs workstations

**Type:** line

**X:** ws

**From:** 10

**To:** 400

**Steps:** 40

**Series:**

- client_hours
- total_elapsed_hours

**Disclaimer:** All rates are your inputs. Measure the database upgrade time in a rehearsal on a restored copy of production; it varies with version jump, data volume and hardware.

## Content

**Intro:** This calculator estimates the downtime and rollout effort of an Infor VISUAL version upgrade, for example from 8.x or 9.x to 10.x. It separates the database window, the client rollout and the retest of macros and reports so you can see which one sets your weekend.

**Sections:**

#### What has to happen in a VISUAL upgrade

**Body:** A VISUAL version upgrade changes the database and the client together. You back up production, run the database upgrade for the target release, then put the matching client on every workstation or shared install before users log in. After that, everything built around VISUAL needs a check: VBScript macros attached to windows, Crystal Reports and other custom reports that read VISUAL tables directly, and any integration that writes to the database. The database step is a hard outage; the client and retest steps can be spread over several people. Do not confuse this with the readiness checklist: that tool decides whether you are ready, this one sizes the window.

**Bullets:**

- Database: backup, upgrade, verify
- Clients: new version on every workstation or shared install
- Retest: macros, custom reports, integrations

#### Formula

**Body:** Backup minutes = GB x 1024 / backup MB/s / 60. Database window hours = (backup minutes + GB x upgrade minutes per GB) / 60 x (1 + contingency). Rehearsal hours = (GB x 1024 / restore MB/s / 60 + GB x upgrade minutes per GB) / 60. Client hours = workstations x (1 - share pushed by deployment tool) x minutes per install / technicians / 60. Retest hours = items x minutes / testers / 60. Total elapsed = database window + the longer of client rollout and retest, because those two run in parallel once the database is up. The upgrade minutes per GB is the number that matters most, and the only reliable source is your own rehearsal.

#### Worked example

**Body:** A 60 GB database backs up at 200 MB/s in about 5 minutes. At 2 minutes per GB measured in rehearsal, the upgrade takes 120 minutes; with 20% contingency the database window is about 2.5 hours. Eighty workstations with half pushed by a deployment tool leave 40 manual installs; three technicians at 10 minutes each finish in about 2.2 hours. Forty macros and reports at 15 minutes with two testers take 5 hours. Total elapsed is about 7.5 hours, driven by retesting, not by the database. The fix is to retest most items during rehearsal so cutover only re-checks the critical ones.

#### Gotchas from real upgrades

**Body:** Rehearse on a restored copy of production, not on a test database from last year: data volume and old data quirks drive upgrade time and failures. Inventory every macro and custom report before the project starts; the ones nobody remembers break on Monday. Check that the workstation operating systems, SQL Server version and report runtime are supported by the target release in Infor's documentation. Freeze macro and report changes after the rehearsal. Define a rollback point: if the database step overruns the contingency, restore the backup and reopen on the old version rather than pushing on into the business day.

**Cta:** If you want your team to ask VISUAL questions in plain English after the upgrade, we can add a private AI layer on your own servers that reads the upgraded database without touching it.

**Faq:**

#### What is the current version of Infor VISUAL?

**Answer:** Infor ships VISUAL in numbered releases, with the 10.x line following 9.0.8. Release numbering and the latest available version change, so check Infor's VISUAL release notes or your support portal for the current release before planning. This calculator works the same for any version jump.

#### Is there an Infor VISUAL version 11?

**Answer:** Confirm the release names and availability in Infor's current VISUAL release notes or with your Infor account team, since roadmaps change. Whatever the target, the cutover has the same parts: database upgrade, matching client rollout and retest of macros and reports, which this calculator sizes.

#### How long does an Infor VISUAL upgrade take?

**Answer:** The database step usually takes hours, not days, for a typical mid-size database, but the real figure comes from a rehearsal on a restored copy. Elapsed cutover is often driven by client rollout and retesting macros and reports. Use the calculator with your rehearsal timings.

#### Do all workstations need the new VISUAL client?

**Answer:** Yes. The client and database are upgraded together, so every workstation or shared install that users log in from needs the client for the new release before go-live. Pushing it with a software deployment tool, or using a shared install, cuts the manual effort shown in the client rollout output.

## Search terms

infor visual erp 10.0.0, infor visual version 11, infor visual current version, infor visual erp latest version, infor visual upgrade, visual manufacturing upgrade downtime, infor visual 9 to 10 upgrade

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