Migrate vs. Restart: Replace Domino or modernize it?
Domino has been supporting core business processes in many companies for years. Applications manage approvals, document customer interactions, and consolidate project knowledge. At the same time, expectations are rising: browser access, modern interfaces, and AI support are intended to simplify everyday work.
This leads to an important investment decision: Should the existing platform be replaced or further developed in a targeted manner? A well-founded answer begins with the requirements and the value of the existing applications.
What you actually replace during a replacement
The visible part of an application consists of forms, views, and documents. Its operational value often lies deeper: in permissions, audit rules, exceptions, interfaces, and processes that have been improved over years.
During a migration, these functions must be identified and taken into account on the target platform. This also includes data transfer, testing, training, and potentially a longer period of parallel operation. An archiving solution for historical information may also be required.
These tasks do not fundamentally preclude replacement. However, they must be included in the calculation. A comparison based solely on license fees or surface area is insufficient.
What “restart” means for your environment
HCL's "Migrate vs. Restart" campaign is aimed particularly at customers who wish to resume manufacturer support. Whether such an offer is suitable depends on the individual contract and licensing situation.
For our consulting services, we take a broader approach: An existing Domino environment receives a current technical upgrade and a concrete development plan. Customers with active maintenance naturally do not need to initiate new support. For them, the focus is on upgrades, operational optimization, and new usage possibilities.
A restart is therefore a conscious investment in the continued use of the platform. This also includes the decision as to which applications will be retained, modernized, replaced, or decommissioned.
From version change to practical benefits
Domino 2026 is the starting point. Which extensions are subsequently useful depends on your operational requirements.
HCL Nomad enables access to Domino applications in browsers and on mobile devices. Before implementation, we assess the suitability of each application and identify potential customizations. HCL Nomad documentation is available.
DominoIQ enables the integration of generative AI into Domino applications. A manageable starting point could be, for example, summarizing selected content. Data sharing, model quality, and expert review are part of the implementation. HCL documentation on Domino IQ
Other approaches include integrating external systems and improving existing workflows. The crucial factor in each case is a specific task: Which tasks become simpler, which media breaks are eliminated, and how do we recognize success?
We will compare the available CCB license scope with your contract and the associated usage rights. Any included component still needs to be installed, configured, and operated. Therefore, we will consider licensing and implementation together.
Five questions to help you decide
What is actually being used? Identify business-critical applications, responsible parties, and dependencies. Unused databases do not automatically need to be modernized or migrated.
What requirements are currently missing? Describe specific problems, such as restricted access or duplicate data entry.
What is the total cost of each option? Compare modernization and replacement over the same timeframe, including operation, personnel, testing, training, and the transition phase.
What risks arise? Assess functional coverage, permissions, interfaces, and impact on daily business.
How quickly will verifiable benefits be achieved? Define an initial project and measurable success criteria, such as fewer manual work steps.
A realistic roadmap to Domino 2026
We begin with applications, infrastructure, and licensing. From this, an upgrade plan is developed, including compatibility testing, a test environment, backups, and fallback options.
We then implement a clearly defined modernization step. Only after evaluating its benefits do we add further applications or components. This ensures that efforts and priorities remain transparent.
Our goal is to support our customers on their journey to Domino 2026 and to make more comprehensive use of the appropriate CCB functionality. Where a replacement is technically or economically compelling, it should be included in the same evaluation.
Do you want to plan your next investment on a sound basis?
Together we will examine which applications should be retained, what is required for the upgrade, and where modernization promises the greatest benefit.
Discuss your Domino 2026 roadmap now.
Back to blog overview