Article

HCL Domino Upgrade Guide: Planning an Upgrade to Domino 14.5 and 2026

A Domino upgrade moves your Domino servers, Notes clients and applications to a current HCL release, today Domino 14.5 or Domino 2026 (14.5.1). Most environments can upgrade directly from older versions, and existing applications generally keep working. Success depends on an accurate inventory, testing applications and add-ons in a lab, and upgrading in the right order: administration and hub servers first, then mail and application servers, then clients.

Upgrades are one of the most common projects our Domino consultants deliver, across every version of Lotus Domino, IBM Domino and HCL Domino. This guide covers why to upgrade now, what the current releases add, and a step by step upgrade plan.

Why Upgrade Domino Now

Support status is the main driver. HCL ended standard support for older versions, and Extended Support is a paid, limited option rather than a long term plan.

VersionStandard supportWhat it means
Domino 9.0.x and 10.0.xEnded June 1, 2024Paid Extended Support available until June 30, 2030, limited to usage questions and existing fixes
Domino 11.0.xEnded June 26, 2025Same paid Extended Support option, through June 30, 2030
Domino 12.0.2 and 14Current releasesSupported upgrade targets, but behind the latest features
Domino 14.5 and 2026 (14.5.1)Latest releasesDomino IQ, modern authentication and current security fixes

Check HCL’s product lifecycle page for the dates that apply to your exact versions and contracts. Beyond support, current releases close security vulnerabilities, support current operating systems, and are what auditors and cyber insurance questionnaires increasingly expect.

What You Gain by Upgrading

AreaWhat current releases add
AIDomino IQ runs AI inference inside your Domino environment, callable from LotusScript (14.5 and later)
AuthenticationPasskeys and OIDC sign in (14.5), with OIDC login in the Notes client (14.5.1)
AdministrationLicense administration database, automated client and server updates, container deployment options
SecurityCurrent fix packs, cryptography and operating system support
Web and mobileHCL Verse webmail, HCL Nomad for browser access to Notes applications, Traveler updates

For a fuller view of the platform, see HCL Domino Server explained.

Domino Upgrade Methods

MethodHow it worksFits when
In placeInstall the new release over the existing one on the same serverHardware and operating system already meet the new requirements
Operating system or hardware first, then in placeBring the server up to the new requirements, confirm it runs well, then upgrade DominoThe current platform can be upgraded to meet requirements
New hardware, same server identityInstall the new release on new hardware and move the server’s data and IDThe old hardware cannot meet requirements and a short outage is acceptable
Side by sideBuild a new server, replicate databases and move users and applications to itDowntime must be minimal or there is too much data to copy quickly
Container replacementStart a new container image against the existing data volumeDomino already runs in containers

HCL advises against upgrading hardware and Domino at the same time, because separating the two makes problems easier to isolate.

Domino Upgrade Checklist

  1. Inventory. List every server, its Domino version, operating system and role (administration, hub, mail, application, Traveler, Sametime), plus Notes client versions and add-on products.
  2. Check requirements and compatibility. Confirm the target release supports your operating systems and hardware. Confirm that backup software, antivirus, archiving and monitoring tools support the target version before you upgrade; backup vendors sometimes certify new Domino releases months after HCL ships them.
  3. Back up and test restores. Take full backups of servers, the Domino Directory and ID vault, and prove you can restore them.
  4. Build a test environment. Copy representative applications and mail files to a lab server running the target release. Test business critical applications, agents and integrations with their owners.
  5. Upgrade the administration server first. Then hub and directory servers, then mail and application servers. In clusters, upgrade one cluster member at a time so users fail over.
  6. Update templates and ODS. Refresh the Domino Directory and mail templates to the new design, and upgrade database ODS during maintenance windows.
  7. Roll out clients. Notes clients can follow the servers in waves; older supported clients keep working against newer servers. Use automated client updates or HCL Nomad where it fits.
  8. Stabilize. Monitor routing, replication, performance and logs, then apply the latest fix pack and plan the next upgrade cycle.

Plan for iNotes Retirement

Domino 14.5 no longer includes the iNotes web client; HCL Verse is the webmail client going forward. If users rely on iNotes, plan the move to Verse, including any customizations and redirects, as part of the upgrade.

What Drives Upgrade Effort

FactorLower effortHigher effort
Starting version12.0.2 or 149.0.x or 10.0.x
Number of serversA few servers at one siteDozens of servers across regions and clusters
ApplicationsStandard mail and a few applicationsHundreds of custom applications and integrations
Add-onsFew third-party toolsBackup, archiving, security and Sametime or Traveler dependencies
ClientsCentrally managed clientsUnmanaged desktops in many locations

Common Domino Upgrade Mistakes

  • Skipping application testing. Most applications run unchanged, but the ones that do not are usually business critical.
  • Upgrading before add-ons are certified. Unsupported backup or archiving tools can leave you without recovery.
  • Upgrading servers out of order. Leaving the administration server behind slows directory and template changes.
  • Forgetting templates. New features and fixes reach users only when mail and directory designs are refreshed.
  • Treating licensing as separate. Access to new versions depends on active support or term licensing; review entitlements with your upgrade. See Domino licensing optimization.

Planning a Domino upgrade?

RockTeam’s US based Domino Administrators plan, test and deliver upgrades across all versions of Lotus, IBM and HCL Domino, from single servers to global clusters. RockTeam is an official HCL Business Partner. Start with a no cost assessment.

Talk to a Domino Consultant

Related Articles

Domino Upgrade FAQs

In most cases, yes. Servers can generally be upgraded directly to a current release without installing each version in between, but test applications, templates and add-ons in a lab first and follow HCL’s upgrade guide for your starting version.

Most Notes and Domino applications run unchanged on current releases. Test business critical applications, agents and integrations before upgrading production servers.

No. Servers are usually upgraded first and clients follow in waves. Older supported Notes clients continue to work with newer servers.

Standard support has ended for these versions. HCL offers paid Extended Support until June 30, 2030, limited to usage questions and existing fixes, so new security issues may not be addressed.

It depends on the starting version, number of servers, applications and add-ons. A small environment can be upgraded in days; large, multi-region environments are usually upgraded in planned phases over weeks.