Why moving off Lotus Notes now makes sense
Somewhere in your company, a Notes database built two decades ago still routes purchase approvals. The developer who wrote its LotusScript left years ago, and the server it runs on is due for renewal. Multiply that by hundreds of apps across business units, and you have the reason Lotus Notes migration keeps landing on IT roadmaps.
The support clock adds pressure. HCL, which acquired Notes and Domino from IBM in 2019, ended standard support for versions 9.0.x and 10.0.x on June 1, 2024 and for version 11.0.x on June 26, 2025. Organizations that can't upgrade in time can buy Extended Support through a Statement of Work with HCL, and HCL has set June 30, 2030, as the final end date.
Staying on Domino is a reasonable choice for some apps. HCL still ships new releases, including Domino 14.5, and a stable app on a current version can stay put. The goal is to make that call on purpose for each app, and the five steps below show you how.
This post covers migrating Notes and Domino applications. Mail migration to Microsoft 365 or Google Workspace is a separate project with its own tools and timeline.
Your Lotus Notes migration plan at a glance
Use this table to assign each step and agree on when it's done.
1. Document your application portfolio
IT leader, with app owners
Every app has an owner, usage data, and a dependency map
2. Decide what to do with each app
IT leader and business owners
Each app has an assigned path and a priority
3. Choose the right platform
IT leader, with CISO sign-off
The platform passes security review and a proof of concept
4. Migrate your first app
Delivery team and pilot users
The pilot meets its success measures in production
5. Migrate in waves and keep improving
Delivery team, with COO oversight of operations
The last Domino server is decommissioned, or the apps you kept run on a supported release
1. Document your application portfolio
If you still use Lotus Notes, your organization may have hundreds or even thousands of Notes and Domino applications spread across business units. How confident are you that you know every last one?
That's what I thought. Your first step is to catalog every Notes application to set the scope of your migration. Capture these details for each one.
Purpose and owner
What the app does and which business leader is accountable for it
Usage
How often people open it (daily, monthly, quarterly, or never)
Location
Server, data center, and region
Complexity
Number of forms, views, and agents, plus how much LotusScript and formula language it uses
Dependencies
Other NSF databases, mail-in databases, and external systems it reads from or writes to
Data and access
Record volume, retention rules, e-discovery needs, and the ACLs and roles that control access
Don't skip dependencies and access rules. An app that looks standalone may feed other databases through scheduled agents, and its ACLs decide who sees regulated data. AI tools can speed up this work by reading LotusScript and formula code to extract business rules and map how databases connect.
2. Decide what to do with each app
Once you have your inventory, you can prioritize and make smart decisions about each app. Most apps follow one of four paths.
Retire and archive
Apps nobody has opened in months, or read-only records
Export the data to a searchable archive that meets retention and e-discovery rules, then shut the app down
Keep on Domino
Stable, low-risk apps with no new requirements
Upgrade to a supported Domino release and revisit later
Replace
Document libraries, discussion databases, and team rooms
Move to a best-in-class product such as SharePoint in Microsoft 365, or Google Workspace
Rebuild and re-envision
Custom workflows, approvals, and apps that need integration or mobile access
Rebuild on an enterprise AI development platform, such as an agentic systems platform
You might be tempted to do a direct migration that copies the look, feel, and business logic of each app. In many cases, your business process has changed since the app was built. A rebuild gives you the chance to re-envision the app to solve today's business problems.
Retired apps still need a plan for their data. Map Notes ACLs and roles to the permissions in your archive so the right people keep access.
3. Choose the right platform
Next, select the enterprise AI development platform platform you'll use for the apps you rebuild. Consider these criteria when you evaluate solutions:
- Speed: Make sure the new platform lets you build enterprise-grade applications fast, in weeks.
- Usability. The platform should make it simple to deliver modern, elegant applications built on sound UX principles.
- Cloud readiness. Even if you still run on-premises servers, the cloud is the future. Pick a platform that runs applications on any cloud, public or private, without locking you into a proprietary environment.
- Security and governance. Your CISO will look for role-based access that maps cleanly from Notes ACLs and roles, plus an audit trail for every change.
- In-house skills. Choose a platform your existing team can use without long retraining or scarce outside hires.
- Agentic legacy modernization. Look for an agentic systems platform that helps developers turn legacy business rules into agents and apps, with human review before anything ships.
- Mobility. The new platform should deliver mobile apps without extra development.
- Flexibility. Your new platform should make it simple and fast to update applications as your needs change.
4. Migrate your first app
Treat your first migration as a pilot that establishes your process. Choose a smaller application that people know well and that connects to a key business process. Use the pilot to re-envision the app, and pick a use case that can grow with new features during the migration.
Agree on success measures before you start, such as adoption by the target users and data that reconciles with the Notes source. The pilot also shows your CISO and COO how security reviews and business sign-off will work for every wave that follows.
Use an iterative development approach. Deliver something in a few weeks, then ship regular updates. Early results build buy-in and momentum for the rest of your portfolio.
5. Migrate in waves and keep improving
With the pilot done, group the remaining apps into waves. Put apps that share data or users in the same wave, and schedule simpler apps early to build speed. Follow the same cutover sequence for every app:
- Run the new app and the Notes app in parallel for a short period everyone agrees on.
- Reconcile the data and confirm that permissions match.
- Set the Notes database to read-only and point users to the new app.
- Archive the Notes data you must keep, then decommission the database.
- Retire each Domino server once its last app moves.
Migration keeps going after the last cutover. As your business evolves, your apps need to evolve with it. Give users a way to submit feedback, ideally in the app itself, so you can keep refining it.
How OutSystems powers your Lotus Notes migration
OutSystems provides agentic development and delivery for modernizing aging systems, including Notes and Domino. Your team rebuilds Notes apps in a visual, AI and agent-assisted environment and deploys them as cloud-ready web and mobile apps. The platform also gives you what you need to build agents that update the core systems your Notes apps connect to.
Organizations with large Notes estates already use this approach.Maeda Corporation, a Japanese infrastructure services company, ran Notes for 25 years and had about 3,500 databases. It started modernizing with OutSystems in 2018, delivered more than 200 applications in the first two years, and completed its Notes Domino migration.
Sarawak Energy, a power utility in Malaysia, launched its Notes Domino migration program in 2021 to replace about 280 Notes databases with OutSystems web applications. While upskilling a team of four developers and two interns, the company delivered 16 new apps in 16 weeks.
Ready to plan your own migration? Download our ebook, Lotus Notes Migration: 5 Steps to Success, to get started. To learn more about agentic legacy modernization, read Deniz Arin’s blog, “Modernize legacy systems with any coding agent and full governance.“
Lotus Notes migration FAQ
How do I migrate from Lotus Notes to a modern platform?
Start with a complete inventory of your Notes and Domino applications. Decide whether to retire, keep, replace, or rebuild each one, then choose a platform for the apps you rebuild. Pilot one app to prove your process, and migrate the rest in waves grouped by shared data and users.
What should I do with hundreds of old Lotus Notes applications?
Sort them by usage and business value. You can retire many rarely used apps once you archive their data. Standard collaboration apps can move to products such as SharePoint, and custom workflow apps are strong candidates for a rebuild. Consolidation helps too; Maeda Corporationmoved about 1,000 Notes applications to 200 modern ones in the cloud.
Is Lotus Notes still supported, and when does support end?
HCL supports current releases of Notes and Domino, such as version 14.5. Standard support ended for versions 9.0.x and 10.0.x on June 1, 2024, and for 11.0.x on June 26, 2025. HCL offers paid Extended Support for those versions through a Statement of Work, with a final end date of June 30, 2030.
Is HCL Notes the same as Lotus Notes?
Yes. HCL acquired the product line from IBM in 2019. HCL now sells it as HCL Notes and HCL Domino.
Can low-code replace my Lotus Notes and Domino applications?
Yes, for most custom Notes applications. A low-code platform rebuilds forms, views, workflows, and agents as modern web and mobile apps that connect to enterprise systems. Sarawak Energy is replacing its Notes apps with OutSystems applications thatintegrate directly with Maximo, SAP, Ariba, and SuccessFactors.
How long does a Lotus Notes migration take?
Timelines depend on the size of your estate and how many apps you rebuild. Maeda Corporation delivered more than 200 apps and completed its migration in about two years. Sarawak Energy delivered 16 apps in its first 16 weeks while its new team was still upskilling.
Since she first used a green screen centuries ago, Forsyth has been fascinated by computers, IT, programming, and developers. In her current role in product marketing, she gets to spread the word about the amazing, cutting-edge teams and innovations behind the OutSystems platform.
See all posts from this author












