Lotus Domino still runs approval workflows, document libraries, and line of business systems inside thousands of enterprises, even though most organizations moved their Notes email to Microsoft years ago. The applications stayed behind. The developers who built them are retiring, licensing costs keep rising, and few IT teams have a clear picture of what they own. Rivit has worked on this exact problem since 2011.
WithRevive application migrationand the AppAnalyzer assessment platform, Rivit helps organizations understand their Lotus Domino portfolio, decide what to keep, and move business logic onto a modern stack without starting from scratch.
→ Are you still running Lotus Domino applications that nobody on your team fully understands? Rivit can map what you have and show you a realistic path forward.Talk to the Rivit team about your Domino environment.
Where Does Lotus Domino Stand?
The platform has changed hands twice. Lotus Development built Notes in the late 1980s, IBM bought Lotus in 1995, and HCL Software took over the product line in 2019. HCL now sells it as HCL Domino, although most IT teams still call it Lotus Domino, Lotus Notes, or simply Notes.
HCL continues to ship new releases. Domino 2026 (version 14.5.1) arrived in March 2026 with interface updates, security improvements, and Domino IQ, an AI engine that runs language models on the Domino server itself. HCL positions the release as an upgrade that lets customers avoid a migration project. For organizations with active Domino development teams, that may be reasonable. For most enterprises Rivit assesses, the developers needed to maintain those applications are already gone.
Support for older versions is more complicated. In 2022, HCL set June 2024 as the end of support for versions 9 and 10 and said no extended support would follow. It later changed course. HCL now offers paid extended support for versions 9, 10, and 11 through June 30, 2030, arranged through a statement of work on top of standard support, as described in itsextended support announcement for older Domino versionson the HCL developer site. Rivit treatsthe 2030 support deadlineas a planning date for its clients, since four years passes quickly for a portfolio of several hundred applications.
In practice, most enterprises with Lotus Domino sit in one of these positions:
- They upgraded to Domino 12 or 14 and now pay more under HCL’s newer licensing, while the applications themselves have not changed in a decade.
- They remain on version 9 or 10 and pay for extended support to buy time.
- They moved mailto Exchange or Microsoft 365years ago and assumed the Lotus Domino problem was solved, then found hundreds of applications still running on a few servers.
- They tried moving applications to SharePoint ora low code platformand succeeded with simple databases, then stalled on everything with real workflow logic.
All four share the same root issue. HCL still supports the platform, but the skills, documentation, and budget needed to keep custom Lotus Domino applications healthy are draining away inside the organization.
→ Is your organization paying for Lotus Domino extended support without a plan for what happens after 2030? Rivit can help you turn the extra time into a funded, scheduled exit.Start a planning conversation with Rivit.
Why Lotus Domino Applications Have Become a Business Risk
Lotus Domino earned its place because business units could build working applications quickly. Over 20 or 30 years, that speed produced sprawl. Rivit regularly finds that a company expecting a few dozen databases actually has several hundred, many with no owner and no documentation.
The risk comes from several directions at once.
The people who understand the code are leaving. Most Domino developers started their careers in the 1990s. Many have retired, and few graduates want to learn LotusScript or the @Formula language. When a critical agent fails, there may be one person left who can read it, or nobody at all.
The cost of staying keeps climbing. HCL has pushed customers toward newer licensing models and version upgrades. Organizations that delayed a decision now pay more each year to stay on a platform they already plan to leave.
Nobody can say what the applications do. Business rules live inside hide-when formulas, computed fields, and scheduled agents. Without documentation, every change carries risk and every migration estimate becomes a guess.
Earlier replacement attempts left a split environment. SharePoint and low code tools handled simple forms well. Applications with approval chains, granular access control, or heavy LotusScript stayed on Domino, so many enterprises now run two platforms and pay for both.
Traditional rewrites are hard to fund. A manual rebuild of a large Lotus Domino portfolio can take 18 months or longer, with a seven figure budget and no firm end date. Finance teams struggle to approve that spend while the current system still works.
Audit and security pressure is growing. Regulated organizations must show auditors where records live, who can access them, and how long they are kept. Aging servers running older versions make that harder every year.
Waiting makes each of these worse. The application count grows, the knowledge pool shrinks, and the eventual project costs more.
The cost of doing nothing also hides in plain sight. Domino administrators spend time patching servers that host applications nobody opens. Developers who could work on AI or cloud projects spend their weeks keeping 20-year-old agents alive. Business units build workarounds in spreadsheets because changing the Lotus Domino application feels too risky. Rivit sees these patterns in almost every assessment, and they rarely appear in an IT budget line, which is why the true cost of staying on Lotus Domino is usually higher than leadership expects.
→ Is your Lotus Domino environment one retirement away from an outage nobody can fix? Rivit can document what your applications do before that knowledge leaves the building.Book a conversation with Rivit.

How Rivit Helps You Decide What to Do With Every Lotus Domino Application
Most stalled Domino programs stall at the same point. Nobody can say how many applications exist, which ones matter, or what a migration would cost. Rivit starts there.
AppAnalyzer migration analysisis Rivit’s discovery and assessment platform, and Rivit offers it as a free analysis. It reads the design of every Lotus Domino database in scope and produces a technical blueprint of the environment, including:
- An inventory of databases, forms, views, agents, and script libraries
- Usage data showing which applications people still open and which sit idle
- Complexity scores and dependency maps between applications
- Effort estimates for each application, with a target accuracy of plus or minus 20%
- Candidates for consolidation, archiving, or retirement
With that data in hand, Rivit works with your team to give each application a clear path. Applications that still run core workflows move to a modern stack through Revive. Applications where only the records matter go to Dcom for archiving. Unused applications get switched off. A smaller group may need a fresh build from Rivit’s enterprise application development team because the underlying business process has changed.
A data-backedapplication inventorychanges the budget conversation. Finance and procurement get per application costs based on measured complexity, and IT leaders get a migration sequence that respects dependencies. Rivit’s approach toapplication rationalizationoften removes a large share of the Lotus Domino portfolio before any code is converted, which lowers the cost of every later phase.
The blueprint also helps people outside the migration team. Enterprise architects see how Domino applications connect to directories, mail, and downstream systems. Security teams see who holds access to which databases. Application managers finally get documentation for systems they inherited years ago. For many Rivit clients, AppAnalyzer is the first time anyone has seen the full Lotus Domino estate on one page, and that view alone often secures executive sponsorship for the program.
→ Do you know how many Lotus Domino applications you actually run, and what each one would cost to move? Rivit’s free AppAnalyzer assessment can answer both questions.Request your Rivit analysis.
How Rivit Migrates Lotus Domino Applications With Revive
Revive is Rivit’s AI-powered migration platform. It converts Lotus Domino applications into running full stack applications built on Java 17+, Spring Boot, and React, with data moved to PostgreSQL, MySQL, Microsoft SQL Server, or MongoDB. The output uses standard open source technology that any modern developer can support.
Each Revive migration follows five stages:
- Export and analyze. Rivit exports application designs to DXL and catalogs forms, views, agents, script libraries, access control lists, and computed fields. Dependencies and workflow patterns are mapped before any code is generated.
- Preserve business logic. Revive translates @Formulas, LotusScript, and action buttons into modern equivalents. Selection formulas become database queries, agents become scheduled jobs or REST endpoints, and the original Domino code stays in place as inline documentation.
- Generate code. The migration engine produces a compiling Spring Boot and React application, with form components, data grids, and a REST API layer already wired together.
- Complete with AI assistance. Rivit developers finish the remaining logic using conversion hints, governance documents, and AI tooling. Revive flags low confidence conversions for human review and never emits them silently.
- Deploy. Access controls, groups, and directory entries move across from the Domino address book, and single sign-on keeps the change simple for users.
Revive generates more than 70% of the application code automatically, and Rivit reports cost reductions of 60% to 90% compared with a manual rewrite. Revive matches your code against verified conversion patterns from completed migrations, so its output is checked against translations that have already worked in production. This pattern-based form ofAI-assisted Notes migrationis how Rivit delivers working applications in weeks.
Once applications go live, Revive Hub gives users a single workspace with application cards, migrated access rights, and single sign-on. That lets organizations retire the Notes client completely when the last Lotus Domino application moves.
Quality checks run throughout. Revive validates the structure of every generated project, and optional compile checks catch syntax and dependency errors before Rivit developers begin their review. Every run is recorded, which gives auditors and project sponsors a full history of how each Lotus Domino application was converted and who approved the result.
→ Has a rewrite quote for your Lotus Domino applications come back too expensive to approve? Rivit can show you what Revive produces from your own application designs.See Revive working on your applications.

What Makes the Rivit Approach to Lotus Domino Different
Enterprises with Lotus Domino applications usually weigh four options: upgrade and stay, rewrite by hand, rebuild on a low code tool, or work with a migration specialist. Rivit built its business around the fourth option, and several things set its method apart.
Rivit concentrates on Domino. Rivit has focused on Notes and Domino migration since 2011, and its team has worked on the platform for more than 25 years. That depth shows up in the details, such as how Rivit handles rich text, multi-value fields, reader and author fields, and access control lists.
Business logic carries forward. Workflows, approval chains, business rules, and access controls move across with each application. Users get the same functions in a modern interface, which keeps retraining to a minimum.
Pricing is fixed from real data. AppAnalyzer measures each application before work begins, so Rivit can offer fixed cost engagements. Clients avoid scope creep and surprise change orders, and finance gets a number it can defend to the board.
Migration moves one application at a time. The existing Lotus Domino application keeps running until its replacement is validated. There is no single cutover weekend and no business-wide freeze.
Clients own the result. Revive produces standard Java, Spring Boot, React, and SQL code that deploys to Azure, AWS, Google Cloud, or on premises servers. There is no proprietary runtime and no license fee after the move.
AI output is checked. Revive scores its confidence on every translation, and Rivit developers review anything the system marks as uncertain.
Each alternative has a cost. An upgrade to the latest HCL release keeps applications running but leaves the skills gap and licensing spend in place. Hand rewrites deliver modern code at a high price and on long timelines. Low code tools suit simple forms and struggle with complex Domino logic. Rivit gives enterprises maintainable applications at a fraction of rewrite cost, and theapplication modernization strategyRivit builds with each client keeps the program tied to business priorities.
→ Is your team weighing a Domino upgrade against a full rewrite and finding neither option convincing? Rivit can compare both against a Revive migration using your own data.Ask Rivit for a side by side assessment.
What a Lotus Domino Modernization Project With Rivit Looks Like
Every Rivit engagement follows a predictable sequence, which gives sponsors clear checkpoints and avoids the open-ended timelines that sink many Lotus Domino projects.
Discovery and blueprint
AppAnalyzer runs against your Domino servers and produces the technical blueprint. Applications that nobody inside the organization understands get documented, often for the first time in years.
Portfolio decisions and business case
Rivit reviews the findings with IT and business owners. Each application receives a decision to migrate, archive, rebuild, or retire, along with a fixed price and a place in the sequence.
Pilot migration
Rivit migrates one representative application with Revive. Users test it against the original, and the pilot confirms estimates before the wider program begins.
Migration waves
Groups of related applications move in dependency order. The original Lotus Domino versions stay available until the new versions pass validation, so daily operations continue throughout.
Archive and decommission
Dcom archives the applications that only need their records preserved. Once the last application moves, servers shut down and HCL licensing ends. Rivit’s approach toretiring legacy applications safelyguides this final phase.
Rivit followed this pattern when itmodernized the branch operations platform for a major bankthat had run non-core transactions through nine interconnected Domino databases. Clients can thenmeasure the impact of a Domino migrationagainst the baseline AppAnalyzer captured at the start.
→ Would a phased plan with fixed costs make your Lotus Domino program easier to approve internally? Rivit can build that plan around your portfolio and your deadlines.Plan your migration with Rivit.
Industries Rivit Supports With Lotus Domino Modernization
Lotus Domino took hold in organizations that needed controlled workflows and strict access rules, which is why the remaining applications cluster in regulated and operations-heavy sectors. Rivit works across all of them.
Rivit helpsfinance and bankingorganizations migrate loan approval, branch operations, and compliance tracking applications while keeping audit trails intact. Public sector teams ingovernment and civil agenciesrely on Rivit to address Domino risks flagged by internal IT audits, often with only one or two staff members left who know the applications.
Organizations inlife sciences and healthcareandpharmause Rivit to move validated quality and document control systems without losing the record history regulators expect to see. Rivit supportsmanufacturingcompanies with engineering change, supplier quality, and plant workflow applications that have run on Domino for decades.
Operators inutilitiesandtransportation and logisticsdepend on Rivit for field service, safety, and asset applications where downtime is not acceptable. Rivit also works withtechnology companiesthat built commercial products on Lotus Domino, including the tax software provider Vertex, whichremoved its Lotus Notes footprint with Rivitafter years of complex custom development.
The common thread across these sectors is risk. A failed Lotus Domino application in a bank, a hospital, or a power utility affects customers, patients, or public safety, so Rivit plans every migration around validation, audit evidence, and continuity of service.
→ Is your industry’s audit or uptime requirement holding back your Lotus Domino migration? Rivit has delivered projects under those exact constraints.Discuss your sector with Rivit.

Other Rivit Solutions That Support Your Lotus Domino Exit
Revive and AppAnalyzer handle most of the migration work, and Rivit offers further services that cover the rest of the program.
Dcom application archivingpreserves historical Lotus Domino data with full-text search, document rendering, and retention controls suited to compliance teams. Dcom has been in production for more than ten years, and it lets organizations shut down Notes servers without losing access to old records.
Enterprise application developmentcovers applications that need a new design. Rivit builds cloud-native systems, APIs, and integrations around business processes that have outgrown their original Domino form.
Infrastructure servicesfrom Rivit prepare the hosting, security, and deployment environment for migrated applications, whether they run on Azure, AWS, Google Cloud, or your own data center.
Rivit is based in Vaughan, Ontario, and has what it describes as the largest team of Notes Domino experts in North America. Rivit runs projects for enterprises across Canada and the United States, and its work often feeds a widerdigital transformation strategyonce Domino is gone. Rivit’s consultants work alongside internal IT teams, architects, and project managers, and they hand over code, documentation, and deployment pipelines that your own staff can run after the engagement ends.
→ Do you need one partner to migrate, archive, and rebuild across your Lotus Domino estate? Rivit covers every stage with its own tools and team.Connect with Rivit today.
Lotus Domino and Rivit: FAQs
Does Rivit work with Lotus Domino applications on older versions like 9 and 10?
Yes. Rivit migrates applications from every common Domino release, including versions 9 and 10 that now depend on HCL’s paid extended support. Revive works from DXL design exports, so the server version does not limit what Rivit can convert.
How does Rivit decide which Lotus Domino applications to migrate, archive, or retire?
Rivit uses AppAnalyzer to measure usage, complexity, and dependencies for every database. Rivit then reviews those results with your IT and business owners and assigns each application to Revive migration, Dcom archiving, a new build, or retirement.
How long does a Lotus Domino migration with Rivit take?
Timelines depend on portfolio size and complexity. Revive produces a running application in hours, and Rivit typically delivers completed applications in weeks rather than the 18 months or more common with manual rewrites. AppAnalyzer gives you a schedule before you commit.
What technology stack does Rivit migrate Lotus Domino applications to?
Rivit delivers applications built on Java 17+, Spring Boot, and React, with data in PostgreSQL, MySQL, Microsoft SQL Server, or MongoDB. You can deploy them on Azure, AWS, Google Cloud, or on premises servers, with no proprietary runtime. Because the stack is mainstream, your internal developers or any future partner can maintain and extend the applications.
How does Rivit keep the business running during a Lotus Domino migration?
Rivit migrates one application at a time. Each original Lotus Domino application stays live until its replacement passes validation, and users see familiar screens and workflows in the new version. Rivit schedules cutovers with business owners so changes land outside peak periods such as month-end or audit season.
Is the Rivit AppAnalyzer assessment really free?
Yes. Rivit offers AppAnalyzer as a free analysis so you can see your inventory, complexity scores, and effort estimates before making a budget decision. There is no obligation to proceed with a migration. Many organizations use the AppAnalyzer report to build an internal business case or to compare vendor proposals against real numbers.
Can Rivit archive Lotus Domino data that we need to keep for compliance?
Yes. Rivit’s Dcom product archives Domino databases with full-text search, document rendering, and retention controls. Your teams keep secure access to historical records after the Notes servers are switched off. Dcom suits applications where the data matters but the workflow no longer runs, which often covers a large part of a Lotus Domino portfolio.
Why should we choose Rivit over upgrading to the latest HCL Domino release?
An upgrade keeps your applications on Domino, along with the shrinking skills pool and ongoing license costs. Rivit moves them to an open stack your own developers can maintain, at a fixed price based on measured data, and ends your dependence on the platform.

Planning Your Lotus Domino Future With Rivit
Lotus Domino will keep running for years, and HCL will keep releasing updates. The harder question is whether your organization can keep supporting its own Domino applications as experienced staff retire and costs rise. Rivit gives IT leaders a measured way to answer it.
AppAnalyzer shows what you own, Revive moves the applications that matter, Dcom preserves the records you must keep, and Rivit’s development team rebuilds what needs a new design. Every decision rests on data, and every engagement runs at a fixed price.
→ Is now the right time to put a real plan behind your Lotus Domino applications? Rivit can start with a free analysis of your environment.Contact Rivit to get started.
→ Follow Rivit onLinkedInfor ongoing insights on Lotus Domino modernization and enterprise application strategy