Skip to main content
Blue Sky

Domino Upgrade Reality: What to Expect

By Patrick Lavan, Domino Expert, Blue Sky

Published · Updated · 3 min read

A simple paperclip

For many organisations, the idea of upgrading a Domino environment feels like a major project.

Concerns about disruption, risk, and complexity often lead to upgrades being delayed sometimes for years.

In reality, most Domino upgrades are far more straightforward than expected.

This article outlines what a typical upgrade actually involves, and where the real challenges tend to sit.

Why Domino Upgrades Are Often Delayed

Pieces being reviewed before an upgrade

It's common for Domino environments to remain unchanged for long periods.

These systems are often stable and continue to support critical business processes without issue.

As a result, upgrades can feel:

  • Unnecessary
  • Risky
  • Potentially disruptive
  • Difficult to justify internally

In many cases, the concern is not based on previous experience but on uncertainty about what an upgrade involves.

What a Typical Domino Upgrade Looks Like

Laboratory testing equipment

Most Domino upgrades follow a predictable and well understood process.

A typical approach includes:

Review/Planning

  • Confirm current Domino versions
  • Review server operating systems
  • Identify key applications and integrations

Test Environment

  • Upgrade a non-production environment
  • Validate mail flow and applications
  • Confirm compatibility

Production Upgrade

  • Upgrade servers in phases
  • Validate services and replication
  • Monitor post-upgrade behaviour

Client Rollout

  • Pilot group deployment
  • Phased rollout across users

Where Complexity Can Arise

A light marking the step into production

When upgrades become difficult, it is usually due to the surrounding environment rather than Domino itself.

Common factors include:

  • Unsupported or outdated operating systems
  • Lack of documentation
  • Unknown or unused applications
  • Third-party integrations that haven't been reviewed
  • Environments that haven't been assessed for many years

These issues can be addressed with upfront planning.

What About Downtime?

A person using a software client

A common concern is user disruption.

In most cases:

  • Downtime is limited to planned maintenance windows
  • Server upgrades involve controlled restarts
  • Users experience minimal impact

With proper planning, upgrades can be completed with very little disruption to day-to-day operations.

Final Thoughts

A complex network of connections

Domino upgrades are often perceived as complex because they are infrequent, not because they are inherently difficult.

When approached in a structured way, upgrades are predictable and manageable.

In many cases, the greater risk comes from delaying upgrades for too long, rather than undertaking them.

Regular reviews help ensure upgrades remain planned activities rather than reactive projects.

Blue Sky provides Domino hosting and management for UK organisations, including upgrades to Domino 14.5.

Let's upgrade your Domino Environment

About the author

Patrick Lavan, Domino Expert, Blue Sky

Patrick has worked with Notes and Domino for 30 years, from the Lotus and IBM eras through to HCL Domino 14.5, and looks after upgrades, administration and security for Blue Sky's customers.

Patrick Lavan on LinkedIn

Accredited and certified