Upgrade Fatigue Is Real. Here's How Prominic Handles It for You
The HCL Domino upgrade has been on your list for a while. It has survived a planning cycle or two, maybe a budget review. You know it should happen, but it keeps stalling. Maybe because your internal team has run out of bandwidth, risk appetite, or specialized expertise.
Luckily, Prominic is set up to take all three off your plate. We run upgrades as a service, not as a quarterly fire drill you have to staff.
Here’s what that looks like, project shape included.
Why the upgrade keeps being pushed off
There are four standard reasons, and you’ve probably lived at least two of them:
-
Competing priorities: Something always outranks a release the business never sees.
-
Admin turnover: The person who knew the environment moved on.
-
Fear of breaking custom apps: Nobody wants to own the outage.
-
Unclear payoff: It’s hard to fund a release users won’t notice.
None of those is a technical problem. They’re organizational.
We see the same thing from the other side of the table. When a customer comes to Prominic still on Domino 11.x, 10.x, or even earlier, it’s almost always one of three patterns:
-
a custom app nobody wants to touch,
-
an admin who left without a runbook, or
-
a renewal cycle that kept stretching.
The technical lift is rarely the actual blocker.
What a managed upgrade actually includes
When Prominic runs the upgrade, the project has five parts:
-
Environment assessment.
-
A staging environment build.
-
Your app validation, in staging.
-
A cutover window, with Prominic engineers on call.
-
Post-cutover verification.
One project, one owner, one number to call.
Who does what
We propose a simple split. Prominic owns the infrastructure, the version, the fix packs, and the upgrade execution itself. You own app-logic validation, because you know what “correct” looks like for your workflows.
That split keeps the project moving. Neither side gets asked to do work it isn’t set up for.
Production goes last
Typically, the upgrade goes first to a non-production server in your cluster where you can test and verify the functionality of your apps. Then the upgrade is pushed to the production server or servers.
That order usually avoids the need to roll production back at all.
The backstop is still there. Every managed upgrade has a defined rollback path before cutover starts. You’re not betting production on the upgrade going clean the first time.
How long it takes
A typical hosted-customer environment upgrade is completed within weeks, not months.
Complexity scales with two things: your custom-app footprint and how far behind your starting version is. In our experience, a 14.0 → 14.5.1 hop is straightforward. A 9.x → 14.5.1 jump wants more discovery time.
Far behind means more homework, not no path. HCL’s server upgrade options cover servers older than 9.0.1, too.
As for the target, HCL released Notes/Domino 14.5.1 in March 2026. Fix Pack 1 then followed on July 16, 2026 and HCL recommends it for every 14.5.1 customer.
Staying current is our job, not yours
Getting current is one project. Staying current is the part that quietly slips.
Once you’re current, point releases and fix packs are part of the service. Fix packs are scheduled in advance, in your preferred weekday window: overnight for North American customers, US business hours for international ones.
Not a 9 PM email asking whether you’re free Saturday.
What you still own
Two things stay with you, on purpose.
Your custom-app logic. Prominic can run the upgrade and confirm the server and the integration layers come up clean. What we can’t tell you is whether your custom application workflow is producing the right business outcome. Someone on your team has to look at it in staging and confirm it is functional on the new version.
The go-live call. We’ll tell you what we found, what we tested, and what we’d do. The call to go live is yours. The side that has to live with the result makes the final call — that’s how a customer-vendor relationship stays honest.
The first concrete move
If the upgrade has been on your list for a while, a scoping call with Prominic is the first concrete move. We’ll tell you what your version looks like from our side and what the project would actually involve. We’ll also cover what staying current looks like once you’re there.
Start with our HCL Domino cloud hosting overview , or reach us at Support@Prominic.NET or +1-217-356-2888.