For years, organizations have told themselves they have already transformed away from Notes (aka Lotus Notes or HCL Notes). But a closer look reveals a different reality. The user email platform has moved. Document repositories have been modernized. Simple applications have been retired. Yet a Domino server is still running somewhere in the environment: not because of one or two applications, but because of dozens, hundreds, or even thousands of business-critical applications that remain deeply embedded across the organization.
If Notes transformation programs have been around for so long, why are so many organizations still running it today? The answer is simple. The easy applications were never the problem. The difficult ones were.
The industry optimized for the first 80%
Many Notes modernization projects focused on applications that were relatively straightforward to move: user email, document libraries, basic lists, and standard workflow applications. These had clear destinations, were low risk, and could be handled by available platforms with minimal customization.
As a result, many organizations successfully transformed hundreds or even thousands of Notes databases. But this approach never addressed the final 20%. The applications nobody fully understands. The ones that run critical business processes with years of undocumented logic, supported by only one or two people, integrated with remaining applications, and where failure could impact customers, regulators, suppliers, or revenue. These are the applications that remain: the ones that didn't transfer easily to an out-of-the-box solution and would require significant workarounds, development, and future support costs.
Why many organizations never finish their Notes journey
This is the uncomfortable reality of many Notes modernization projects. Organizations successfully modernize 80–90% of their environment. Then progress slows. Projects stall. Budgets shrink. SMEs retire. The remaining applications become increasingly expensive and risky to transform. Many organizations declare victory while continuing to run Domino indefinitely. Not because they want to. Because they don't know how to safely tackle what's left.
Several roadblocks compound this challenge.
Organizational silos create fragmented transformation efforts. Notes applications often act as quick workarounds for limitations in other platforms, creating hidden dependencies that affect the scope, cost, and timing of other projects. Because these dependencies are frequently unbudgeted and unplanned, they introduce risk late in the program. When each silo chooses its own target platform and approach, delivery becomes slower, more expensive, and harder to govern.
Traditional SDLC models force organizations to start over on every application. IT owners and business stakeholders are interviewed again. Requirements are rediscovered. Processes are mapped manually. Developers rebuild functionality from scratch. Because many remaining Notes applications are poorly documented and supported by only a handful of subject matter experts, this redevelopment phase quickly becomes the longest and most expensive part of the entire project.
Disconnected teams create another failure point. A common pattern is a handoff between a transformation team focused on data and a redevelopment team tasked with understanding the application, documenting requirements, and rebuilding on the new platform, often without direct input from business users. Communication becomes fragmented, timelines stretch to months or years, and costs escalate.
Scope framing matters more than most organizations realize. The common like-for-like approach – rebuild exactly what you have today within a fixed budget – sets the wrong tone from the start. Business stakeholders expected transformation. What they receive is an expensive recreation of the past, complete with the same technical debt, on a newer platform. When users are anchored to how things used to work, true transformation rarely follows.
Transformation needs a radical rethink
The first signs of complexity in any modernization program usually emerge quietly. A rebuilt workflow pulls data from a Notes database that was never documented. An integration surfaces that nobody remembers building. A downstream reporting process turns out to rely on something created years ago by a developer who left a long time ago. Organizations frequently rush into build before completing discovery, assuming they already know their estate. That assumption is almost always wrong.
Most analysis tools were built to answer technical questions about the current state of a Notes estate, not future-state business outcomes. They tell you what you have. They rarely tell you what to do with it. The right questions are: Why does this application still exist? Who depends on it? Is all the functionality still used? What business benefit could it provide in the future? Moving from assumptions to evidence, through structured discovery, is what separates transformation programs that succeed from those that stall.
This is why transformation needs a different starting point. Analysis should not just inventory applications; it should provide transformation intelligence. The ability to understand business value, identify what can be retired or archived, and rapidly reimagine an application's future, all before a single line of code is written. Know what you have. Understand why it still exists. Then decide what it should become.
Where Pega Notes to Blueprint changes the game
Most vendors ask: Where can this application go?
We ask: How could it deliver better outcomes for your business quickly?
That distinction changes everything. Pega Notes to Blueprint™ begins with discovery that goes beyond inventory. It collects metrics specific to what matters when transforming applications and retiring Domino: activity, complexity, utility, and hidden dependencies. It quickly surfaces what to prioritize, what to retire, and what to archive or move to a records management system.
Those insights feed directly into Pega Blueprint™. Most analysis vendors produce reports. Blueprint produces outcomes. Stakeholders come together to rapidly generate a functional, AI-integrated, platform-ready application, including UI, workflow, data models, and integrations. Instead of spending months rediscovering how a legacy application works, teams can focus on how the business wants to operate in the future.
One of our partners, Aaseya, operationalizes this through ARISE methodology (AI-led Rapid Intelligent Solution Engineering), a Blueprint-first, AI-led delivery model designed to compress the journey from discovery to value realization. Across engagements, this approach has helped reduce discovery effort by 50–70%, accelerate testing cycles by 30–40%, and improve overall time to market by as much as 45%. Tools such as RevBot and QABot automate governance, code quality checks, and testing directly from Blueprint-driven requirements, ensuring speed does not come at the cost of quality or architectural integrity.
Transform: Don't recreate the past
Many modernization projects unintentionally recreate technical debt. The objective should not be to rebuild a newer version of a 20-year-old application. The goal should be a better business outcome.
By transforming Notes applications into modern Pega workflows, organizations gain enterprise workflow automation, case management, business rules and decisioning, AI-powered process optimization, agentic AI capabilities, governance and compliance, cloud-native scalability, and continuous evolution without rebuilding. Rather than replacing one application platform with another, organizations establish a modern operational foundation built for the next decade.
Migrate data with purpose
Data migration remains a critical part of transformation, but it should support transformation, not define it. Notes to Blueprint Migrate uncovers the data structures of Notes applications: forms, rich text, attachments, document relationships, and application-specific design. Unlike target-specific or custom scripting approaches which export and import, it enables organizations to migrate data that belongs in Pega while providing archive capability for data that must be preserved, in a repeatable and auditable way.
Why Pega is the right destination
The remaining Domino applications survive because of the business processes they enable. They manage cases. They orchestrate work. They route approvals. They enforce decisions. They coordinate people, systems, and information. In other words, they do exactly what Pega was designed to do, but without governance, AI integration, or an easy way to adapt, extend, and reuse.
The future is reimagining, not just rebuilding
The Notes migration industry spent 20 years helping organizations move the easy applications. Notes to Blueprint and Pega Infinity™ are built to finish the transformation, and to do it in a way that builds a better business, not just a newer system.