Lotus Notes & Domino Migration Modernization

Let’s start with what’s true: Lotus Notes and Domino are not dead. IBM sold the platform to HCL in a deal that completed in 2019, and HCL has actively developed it since — shipping Domino 14, then 14.5, with a published roadmap and support for older versions running into 2030. The Notes business applications running on it have served the organization correctly for years, and pretending the platform is failing would be dishonest. The reason to modernize the Notes applications off it is not that Domino is unsupported. It’s that the collaboration market around the platform has been shrinking for a long time, the people who can maintain Notes apps are getting scarce, and those applications are hard to connect to everything else the business now runs on.

The pressures building on Notes and Domino

There’s no support cliff to point at — HCL develops and supports the platform — so the honest framing replaces a date with the pressures that build over time:

Pressure	What it looks like	Why it matters
Platform support	Notes/Domino actively developed by HCL; older versions supported into 2030	Not the problem — the platform itself is supported
Ecosystem	A collaboration market that’s been declining for years	Fewer peers, partners, and current references each year
Skills	Notes/Domino app-development talent aging and scarce	Notes business apps become unmaintainable from the inside out
Integration	Notes-specific apps, limited modern API surface	Hard to connect to cloud, modern identity, and data

The clearest pressure is the ecosystem combined with skills. Notes was once a default for enterprise collaboration; that center of gravity moved years ago, and the developer pool that can build and maintain Notes applications has narrowed with it. New entrants are rare. That’s not a date HCL sets — it’s a market trend — and it means the practical risk lives less in the server and more in the applications: the dozens or hundreds of custom Notes databases the business quietly depends on, maintained by fewer and fewer people who understand them.

What the real risk is — and isn’t

Because there’s no EOL date, it’s worth being precise about where the exposure actually lives.

• The skills cliff is the headline. Each year there are fewer developers who can read and safely change a Notes application, the knowledge of what each app does leaves with them, and routine changes get slower and more expensive to contract out. A set of working apps you can no longer confidently modify is a real liability.
• The ecosystem is declining. The collaboration market around Notes/Domino has been shrinking for years — fewer peers, fewer partners, fewer current tools and references. The support structure around the applications gets thinner over time, independent of HCL’s continued investment in the server.
• Integration is the agility tax. Connecting Notes business applications and their data to modern identity, cloud services, APIs, and analytics is consistently harder than it should be, which slows down everything the rest of the business wants to build.
• What it is not is a security-patch emergency driven by an unsupported runtime. HCL supports the platform. Equating a supported Domino server with an out-of-support Windows or database would be dishonest, and we won’t make that argument.

The migration options

There is no single right move; there’s a right move for your estate, and it usually differs application by application across the Notes databases you run.

• Stay on the platform. Keep Domino, upgrade to a current release, and maintain the applications as they are. Defensible for a stable estate with intact skills where the integration limits aren’t biting — but it’s a bet against a declining ecosystem and a shrinking talent pool, and it doesn’t get easier with time.
• Retire or consolidate. Many Notes estates carry apps that overlap with tools the business already owns, or that almost nobody uses anymore. Some applications are best decommissioned or folded into existing systems rather than migrated at all — and identifying those is real savings.
• Re-platform the applications off Notes. Rebuild the genuinely valuable apps on a modern stack, preserving the durable business logic and data and discarding the Notes-specific delivery. The transformative path — it addresses skills, ecosystem, and integration together — and the one that turns a frozen estate back into systems the business can change.

The decision turns on triaging the estate — separating the apps worth re-platforming from the ones to retire or consolidate, and within each, separating durable business logic from Notes-specific plumbing. That triage is the core of the work, and it’s why a Notes migration is a modernization program rather than a bulk export.

Modernizing a Notes estate app by app

We treat a Notes estate the way we treat any legacy system: not one risky migration of every application at once, but a sequence of small, reversible steps, one application at a time.

A strangler facade sits in front of an application so the legacy Notes app and the modernized path run side by side. We work through the estate slice by slice — an application, a workflow, a bounded set of documents and views — and before any slice carries live work, we prove it behaves identically to the legacy: same outputs, same state, validated against real behavior. AI-accelerated discovery reads the Notes databases, the forms, the views, and the embedded logic end to end and captures what they actually do — including the undocumented rules buried in apps whose authors moved on years ago — under senior-engineer review. Traffic shifts only on green, rollback stays a flag away, and a legacy application is retired only once nothing depends on it.

When staying on Domino is the right call

This is the section where overselling would be easiest, so we’ll be plain. Domino is supported by HCL, and for some organizations staying on the platform for the core, with a deliberate plan to retire the long tail, is the right call for years yet — particularly where the team is intact and the integration limits aren’t biting. If “it still works and we can maintain it” is genuinely true for your key apps, a full migration can wait. The case to re-platform the applications gets compelling when the skills risk is near and real, when the declining ecosystem is leaving you exposed, or when the inability to integrate is actively holding the business back. We won’t sell a migration against a deadline that doesn’t exist — we’ll triage the estate honestly and scope the work that matches your actual pressures.

Where to start

The first step is small and bounded: understand the estate before committing to a path. A discovery call scopes how many Notes applications you run, which ones carry real business value versus which to retire, how exposed you are to the skills and ecosystem decline, and whether the right move is to stay, consolidate, or re-platform — on evidence, not a sales pitch. Reach the team at sales@modernlift.ai.