- >
- Low Code>
- Lotus Notes Migration with AI and Low-Code: Steps, Platforms, and Governed Rebuilds
Lotus Notes Migration with AI and Low-Code: Steps, Platforms, and Governed Rebuilds
Lotus Notes migration with AI and low-code is the process of moving HCL Domino applications to a modern platform, where AI maps and translates the legacy logic and a governed low-code platform rebuilds the workflows.
Key takeaways
- AI scans legacy NSF databases to map hidden dependencies and separate critical workflows from redundant data.
- AI-assisted translation turns LotusScript agents and @Formulas into business rules a low-code platform runs.
- Pega Notes to Blueprint handles discovery, while Power Apps, OutSystems, Mendix, and Kissflow serve as rebuild targets.
- Each HCL Domino application is archived, retired, or rebuilt according to its complexity.
- A rebuild without access control and an audit log recreates the sprawl the Notes estate became.
Lotus Notes migration with AI and low-code is a specific kind of modernization project. AI reads the legacy estate, and visual development rebuilds it. IBM defines low-code as a software development approach that lets people build applications with minimal hand coding.
This guide is for a CIO or IT director who is building a migration shortlist. These projects usually start with a support notice for Domino 9 or 10, or the retirement date of the last developer who still reads LotusScript.
Your job is to move decades of approval logic off a platform nobody wants to staff while keeping the rules buried inside it. This roundup covers the standard migration sequence, five platforms used in Notes migrations, and the governance decision to settle before cutover.
Why are enterprises migrating off Lotus Notes now?
Support deadlines and retiring skills are forcing the decision more than cost is. An aging Notes estate costs money to keep running every year, but the money matters less than the risk.
The pressures behind a Notes exit fall into five groups:
- Standard support for Domino 9 and 10 ended on 1 June 2024, so staying on those versions now means paying HCL for Extended Support
- LotusScript skills are retiring, so each year fewer people can maintain the estate
- Documentation rarely exists, and business logic sits scattered across LotusScripts, forms, and agents that no current policy describes
- Technical debt piles up as old applications are patched instead of replaced
- Mendix names an ungoverned "app jungle" as a reason to leave Notes, along with total cost of ownership, poor usability, and lack of openness
Mendix's "app jungle" reason is the one that should shape your platform choice. A jungle is defined by missing controls, not by the age of the software. A fast rebuild that skips access control and audit trails carries the same jungle onto a newer platform.
How does AI and low-code Lotus Notes migration work?
A Lotus Notes migration runs in a fixed order: discovery, then logic translation, then low-code rebuilding, then a governed cutover.
- Automated discovery: The first step inventories every database on the HCL Domino servers before any rebuild decision is made. Pega Notes to Blueprint, for example, analyzes LotusScript, forms, and agents across HCL Domino servers to build a portfolio analysis. Teams see which Lotus Notes applications are still in use before anyone writes new logic.
- AI-assisted logic extraction: Generative AI reads LotusScript agents, @Formulas, and field validations and translates them into business rules a modern platform executes. AI-driven refactoring rebuilds Domino applications in weeks, not years. A process owner still reviews the output, because a cleanly translated approval rule is wrong if the policy behind it changed.
- Low-code rebuilding: Notes forms, views, and workflows become visual components instead of hand-written code. On Microsoft Power Platform, Power Accelerate describes an accelerator that deep-scans forms, views, agents, access control lists, rich text, and attachments, then generates Power Apps on Dataverse with most of the rebuild running unattended. Access lists and attachments carry business meaning too.
- Governed cutover and archiving: Rebuilt Lotus Notes applications go live in phases while redundant data moves to an archive, guided by usage analysis such as Teamstudio's report on which databases people still open. Each rebuilt workflow should go live with role-based access control, single sign-on, and an audit trail that timestamps and attributes every action, so the new estate avoids the old sprawl.
Discovery, logic translation, and low-code rebuilding each have dedicated tools, from Pega Notes to Blueprint to Power Accelerate. Governed cutover decides whether the rebuilt applications pass their first audit.
What does AI actually do in a Notes migration, and where does it stop?
AI shortens the reading, and people still make the decisions. The time saved comes from parsing undocumented LotusScript far faster than a person can, while a human decides whether each rule should survive the move.
The output format matters more than the speed. Some tools hand back generated code. Others hand back structured, inspectable metadata that describes the business logic. For a Notes estate, that difference is the whole point.
You are leaving because nobody can explain the current logic, and generated code that process owners struggle to read can repeat that problem on a newer platform. Compliance will ask the same question it asks today: who approved this rule, and when did it change?
The better split keeps the human in the lead. AI drafts the logic, a process owner approves it, and every later change lands in the same record. Ask each vendor to show you a migrated approval rule six months after go-live, along with who changed it.
Which platforms are used for Lotus Notes migration with AI and low-code?
Pega Notes to Blueprint covers discovery, and Power Apps, OutSystems, Mendix, and Kissflow serve as rebuild targets. Each profile covers the platform's role in a Notes migration, what adopting it requires, and its G2 rating.
Pega
Role in a Notes migration: Discovery tool. Pega Notes to Blueprint scans proprietary NSF databases and generates a portfolio analysis that maps the logic scattered across LotusScripts, forms, and agents.
What adopting it requires: Access to the Notes databases you want analyzed. Notes to Blueprint imports the extracted logic into Pega Blueprint, and clients request access through Pega Marketplace or AWS Marketplace. A version delivered with Capgemini adds services for data migration, validation, testing, and change management.
Review ratings: 4.2 stars on G2 from 278 reviews for Pega Platform (as of October 2026).
Power Apps
Role in a Notes migration: Rebuild target. Notes forms and views are rebuilt as Power Apps within Microsoft Power Platform, and partner accelerators such as Power Accelerate automate extraction into Dataverse.
What adopting it requires: A Power Apps Premium license for every user who runs an app in production. The license includes Dataverse storage and prebuilt, custom, and on-premises connectors.
Review ratings: 4.3 stars on G2 from 569 reviews (as of October 2026).
OutSystems
Role in a Notes migration: Rebuild target. OutSystems migration guidance begins with documenting the application portfolio and deciding what to do with each app, and OutSystems says Notes applications and workflows can be recreated in weeks or even days.
What adopting it requires: A team that can work on the platform without heavy upskilling. OutSystems guidance recommends treating the first migrated app as a pilot project, then delivering in short iterations with user feedback collected inside the application.
Review ratings: 4.5 stars on G2 from 1,810 reviews (as of October 2026).
Mendix
Role in a Notes migration: Rebuild target. Mendix's Notes migration guidance makes the case for moving Notes applications to a cloud low-code platform.
What adopting it requires: Business and IT working together. Mendix's guidance has the business take part directly in development while IT manages the application portfolio centrally, with apps deployed to the cloud.
Review ratings: 4.4 stars on G2 from 417 reviews (as of October 2026).
Kissflow
Role in a Notes migration: Rebuild target. Kissflow is an AI-powered enterprise application platform where business teams and IT build, automate, and govern their core work through business logic, not code. It handles the structured work at the edges of systems of record such as SAP, Oracle, Salesforce, and Workday, and never replaces them.
AI Builder, generally available as of May 2026, generates a complete working app from a single prompt or an uploaded requirements document, refined through conversation. The blueprint it produces covers the data model, pages, roles, workflows, and navigation, and every artifact is a standard Kissflow component a developer can open and read.
What adopting it requires: Business teams to build the apps, IT to govern what they build, and developers to extend them when the logic gets hard. Implementation is delivered directly by Kissflow or through partners.
Review ratings: 4.3 stars on G2 from 590 reviews (as of October 2026).
See how Kissflow approaches the move on the Lotus Notes migration to Kissflow page.
How do these platforms compare side by side?
| Platform | Role in a Notes migration | What adopting it requires | G2 rating (as of October 2026) |
|---|---|---|---|
| Pega | Discovery tool (Notes to Blueprint) | Access to the Notes databases you want analyzed, requested through Pega Marketplace or AWS Marketplace | 4.2 stars, 278 reviews (Pega Platform) |
| Power Apps | Rebuild target on Microsoft Power Platform | A Power Apps Premium license for every user who runs an app in production | 4.3 stars, 569 reviews |
| OutSystems | Rebuild target | A team that can work on the platform without heavy upskilling, starting with a pilot app | 4.5 stars, 1,810 reviews |
| Mendix | Rebuild target | Business and IT working together, with apps deployed to the cloud | 4.4 stars, 417 reviews |
| Kissflow | Rebuild target | Business teams build, IT governs, and developers extend the apps when the logic gets hard | 4.3 stars, 590 reviews |
How should you choose a platform for your Notes estate?
Pick the platform that can still own your rules five years from now. Conversion speed shapes the first quarter of the project. Who changes the rules afterward shapes every quarter after that.
Picture a Notes purchase-request database in which a LotusScript agent sends requests above a spending threshold to finance. After the rebuild, that threshold should be a rule that your procurement lead changes without a release cycle, and the change should appear in the audit log under their name. Test each shortlisted platform against that standard:
- Ask what the AI hands back: code a developer must maintain, or output a process owner can read and approve
- Find out who will change approval rules after go-live, and whether each change needs a development ticket
- Confirm whether role-based access, SSO, and audit trails come with the platform or must be configured for every app
- Model the total price for your builders and for hundreds of occasional approvers on each platform
- Check where the rebuilt app sits relative to SAP or Oracle, so it coordinates the work around those systems of record
- Compare release tooling against your change process, including how a rule change moves from build to live on each platform
An unsanctioned app failing a security review is a fair worry for any IT director who inherits hundreds of Notes databases. The questions on access, audit, rule ownership, and pricing at scale address that worry directly, so give them the same weight as conversion speed.
Where should your Notes migration start?
Start with governance, before you rebuild anything. Agree who owns each business rule, who may change it, and what the audit log must record. Settle those answers once, and every migrated Notes application inherits them at go-live instead of being reviewed one by one afterwards.
Pull the Domino usage report, tag every NSF database as archive, retire, or rebuild, and decide who owns each business rule after go-live.
Upload the requirements document for your first rebuild candidate to Kissflow AI Builder to get a working app you can test against your governance checklist.
Frequently asked questions
What happens to application data that was previously embedded in Lotus Notes apps?
Live records that a rebuilt workflow still needs move into the new platform's data model, and closed records go to a read-only archive that stays searchable for audits and retention rules. Decide that split for each database during discovery, before any rebuild starts.
Can this be done in phases rather than a single cutover?
Yes. Group databases into waves by business owner or dependency, rebuild one wave at a time, and keep each Notes application read-only until its replacement passes user acceptance testing. The first wave then sets the access and audit pattern that later waves reuse.
What is the fastest way to pilot a Notes migration on one application?
Pick one approval database from your usage report and run it through the four steps: discovery, logic extraction, low-code rebuild, and governed go-live. Have a process owner review every translated rule, and test the result against your access and audit checklist. Kissflow AI Builder can generate a working app from an uploaded requirements document for this test.
Book a demo to test one of your Notes approval rules against these checks on Kissflow.
