Replace Lotus Notes with modern web applications
HCL Notes (formerly Lotus Notes) and IBM Domino still run in many Dutch corporates — often behind a locked glass door, where forms, workflows and knowledge databases have kept working unchanged for twenty years. We migrate NSF databases, LotusScript business logic and Domino forms to custom web applications on a modern stack — preserving data, audit trail and business rules.
HCL Notes (formerly Lotus Notes): when 30 years of legacy turn into accumulated pain
When it was introduced in 1989, Lotus Notes was a revolutionary platform: a groupware environment in which email, calendars, forms, workflows and knowledge databases came together in a single NSF file, with server replication that was far ahead of its time. IBM acquired Lotus in 1995, and in the 2000s the platform became the standard collaboration platform for banks, insurers, ministries and large business service providers. In 2019, IBM sold the entire Notes/Domino portfolio to HCL Technologies. Since then the client has been called HCL Notes and the server HCL Domino, and further development sits with an Indian owner that offers modernisation paths with Volt MX and the HCL Domino REST API.
Many Dutch organisations have been postponing migration to newer platforms for years. Not out of nostalgia, but because the business logic inside is critical and nobody really knows who can still rebuild it. These are the patterns we typically see at clients:
- A handful of NSF databases are business-critical: the contract register, the complaints or incident register, an approval workflow for purchasing, a knowledge base with procedures, or a case management system for cases, members or relations. The rest has been phased out or is read-only.
- The LotusScript developer has retired, works elsewhere, or is on the payroll of an external party that bills by the hour for changes that have been standard practice elsewhere for twenty years.
- Integrations are brittle: integrations with the accounting system, a CRM or a data warehouse run through export scripts or nightly replicas and break with every migration elsewhere in the landscape.
- The UI falls short of current expectations: users want to work on mobile, integrate with Microsoft 365 or Google Workspace, and use SSO via Entra ID. iNotes and HCL Verse don't reach that level.
- GDPR and security questions are becoming uncomfortable: older Domino versions are no longer maintained, audit trails on reader/author fields are hard to export to modern SIEM tools, and pseudonymisation after the fact is a puzzle.
Lotus Notes was great in its day. For a distributed organisation without a permanent internet connection, without cloud and without browser applications, with a development model in which form, view and business logic could live together in one file, it was a marvel. Today there are practical reasons to say goodbye: a shrinking developer pool, integration complexity, mobile users and compliance. We help you say that goodbye in a structured way, without the business grinding to a halt.
The typical pain points of a Notes/Domino environment today
Before we talk about migrating, let's start with an honest diagnosis. These are the pain points we encounter in practice at organisations still running HCL Notes / Domino:
Technical
- NSF databases are document stores with embedded forms and views — not relational schemas. Joins, complex reporting and BI integrations are cumbersome.
- LotusScript & @-formulas: business logic is scattered across form events, view formulas, agents and buttons. Refactoring without a full inventory is risky.
- Replication conflicts: with distributed replicas between offices or branches, save conflicts are a daily administration issue that simply doesn't exist in modern systems.
- Rich Text Format (RTF): legacy Notes RTF is a proprietary format, so converting it to HTML/Markdown requires a DXL export plus a parsing layer.
- Reader/Author fields handle access control at document level. This logic has to be translated one-to-one into row-level security in the new stack.
Organisational
- Domino Designer expertise is becoming rare: there is hardly any training left, and the pool of freelancers shrinks every year.
- Unknown dependencies: a derived app often uses a view from another database via @DbLookup. Nobody knows any more which databases are truly standalone.
- Few modern integrations: connecting to Salesforce, AFAS, Exact, Microsoft 365 or a data warehouse requires custom development or expensive third-party connectors.
- Mobile working via Traveler or iNotes is functional but feels dated; users are asking for native iOS/Android experiences and PWAs.
- Vendor roadmap: HCL is still investing, but its strategic focus is on Volt MX as a low-code layer, not on extending the classic Notes/Designer stack.
In our IT modernisation programme we treat these pain points as input: not everything has to go at once, and not everything in Notes needs to survive at all. An honest audit often shows that 30-40% of NSF databases can simply be archived, 30% need a modern one-to-one replica, and 30% can be extended with new functionality in the new environment (mobile, BI, external chain partners). Also read our broader view on replacing legacy software.
Our migration approach: from NSF to modern web application
A Notes/Domino migration is not a straightforward database export. The value lies in the combination of data, form logic, views, workflow states and access control. We work in four steps, with explicit go/no-go moments so you are never faced with surprises.
Inventory and audit
We map every NSF database, every ACL, every agent and every hidden view. Tools: nsfdump, DXL export via Domino Designer, plus a manual walkthrough with your key users. The result: a complete overview of forms, views, scheduled agents, reader/author rules, replicas and cross-database lookups.
Extract and design
The DXL export delivers XML representations of forms, views and documents. We parse these into a target schema in PostgreSQL or SQL Server, capture the business rules from LotusScript and @-formulas in a specification, and design the new application flow with clickable prototypes for your key users.
Building in sprints
Agile build in two-week sprints, with parallel data migration and validation against the live Notes environment. Reader/author fields are translated into row-level security; LotusScript agents into background jobs or serverless functions; views into tables plus search and filter layers.
Cutover and sunset
Extensive acceptance testing with key users, user training, a parallel run with Notes and a planned cutover. After that we put Notes into read-only mode for archiving and plan the final sunset of the Domino servers, including licence and compliance accountability.
What we typically do during the extract step
load nsfdump -d contracten.nsf -o contracten.dxl
# 2. Parse DXL: forms, fields, views, documents, ACL
python dxl_parse.py contracten.dxl > schema.json
# 3. Generate target schema (PostgreSQL) + business rule spec
python schema_to_sql.py schema.json > migrate.sql
# 4. Migrate documents incl. RTF -> HTML conversion
python migrate_docs.py --batch=500 --validate
The final architecture depends on your landscape (see below), but the pattern of NSF extraction via DXL plus business rule extraction from LotusScript stays constant. We document every conversion step, so that after go-live you don't just have a new application, but also an audit trail showing where the old data and logic ended up.
Three migration paths: which one fits your situation?
Not every organisation wants to leave HCL straight away. Some clients prefer to modernise within the Domino platform first, while others go directly for a complete rebuild. We work out all three paths and help you choose based on your application portfolio, in-house expertise and strategic roadmap.
HCL Domino modernisation with Volt MX
For organisations that want to keep their Domino investment for the time being, HCL offers two modernisation tracks: HCL Domino REST API (to expose existing NSF data through modern endpoints) and Volt MX (HCL's low-code platform with cross-platform UIs on top of NSF data). We build Volt MX front ends and REST bridges so your NSF data is accessible through modern web applications and mobile apps, without having to rewrite all your business logic at once.
A good fit if: you still hold active licences, want to retain in-house Domino expertise, and want to phase the migration over several years.
Full rebuild on a modern stack
For the greatest freedom and the lowest long-term TCO: a complete rebuild on a modern stack. Document storage and collaboration move to Microsoft 365 or Google Workspace; workflow and case logic becomes a custom web application (typically React or Astro on Node.js / .NET, with PostgreSQL or SQL Server, hosted on Azure or a private cloud). Authentication via Entra ID, audit trails to your SIEM, and BI directly via a data warehouse.
Suitable if: you were already due a broader overhaul, or if your current Notes applications have drifted too far from their original design to be worth copying. Take a look at our custom software approach for more details on how we build custom software.
Hybrid approach with a REST bridge
Often the pragmatic optimum for large portfolios: we build a REST layer on top of Domino (our own middleware or the HCL Domino REST API) and migrate applications one by one. Non-critical databases are archived, critical databases are replaced by custom web applications that can temporarily still read or write Notes data via the REST layer, and eventually Domino is sunset.
A good fit if: you have dozens of NSF databases, not all data is equally critical, and you want to migrate in a risk-weighted way without a big bang. It fits well within a broader IT modernisation programme.
| Aspect | A · Volt MX | B · full rebuild | C · hybrid |
|---|---|---|---|
| Lead time | Short — weeks per app | Long — months per app | Medium — portfolio in phases |
| HCL licences | Retained | Phased out | Retained temporarily |
| Mobile UX | Good (Volt MX) | Completely free | Varies per app |
| Microsoft 365 / Salesforce integrations | Limited — via REST bridge | Native | Per app |
| Risk | Low | Medium — rebuild | Low — phased |
| Long-term TCO | Medium | Low | Medium |
Which Notes applications do we see most often in Dutch corporates?
At almost every client with an active Notes environment, we find one or more of these use cases. We have a reference approach for each of them — from data model to UI pattern — so you don't have to wait through four weeks of design meetings before the build starts.
Employee handbook / knowledge base
Procedure manuals, health and safety instructions, quality files. Often hundreds of Notes documents with version history and reader/author rules per department. We migrate these to a custom knowledge portal or a knowledge base web app with search, versions, comments and role-based access.
Contract and relationship database
Contract register, supplier files, customer database. Reader fields for sales versus legal, expiry-date agents and email reminders via LotusScript. We replace these with a lightweight custom CRM or a workflow web app.
Approval and project tracker
Purchase requests, leave requests, change requests, small investment proposals. Notes workflow with status fields, escalation agents and email notifications. Becomes a modern document workflow application with an audit log and BI dashboards.
Complaints or incident register
Compliance and quality reports, incidents, data breaches, security events. High demands on audit trails, segregation of duties and reporting. We build this as a custom app with SIEM export and BI integration, integrated with Microsoft 365 and your existing GRC tooling.
In some cases, the Notes functionality overlaps with what an out-of-the-box product (SharePoint Online, ServiceNow, Salesforce, AFAS) already offers. We have no qualms about advising you to choose a standard package when that makes sense — we only build custom software where it delivers real benefit. For pure document storage, a custom SharePoint alternative or the standard M365 stack is often enough.
Domino jargon: what's what?
Anyone just starting a Notes migration can easily get lost in the platform's own terminology. A short cheat sheet for your own IT team and steering group:
NSF (Notes Storage Facility)
The file format of a Notes database. It contains data, design elements (forms, views, agents) and the ACL in a single file. An NSF can have replicas on multiple servers; replication conflicts are a typical management issue.
LotusScript
A Visual Basic-style procedural language for server-side and client-side scripting. Used for agents, button events and form events. Much of the classic business logic in NSF databases lives here.
@-formulas
Lotus's own formula language for view selections, computed fields and simple logic. @DbLookup, @If, @DocumentUniqueID — recognisable by the @ prefix. Similar to Excel formulas in terms of mental model.
Domino Designer
The Eclipse-based IDE in which Notes applications are built. It includes editors for forms, views, agents, script libraries and application properties, and is also a source for DXL export.
DXL (Domino XML Language)
XML export format for both data and design elements. Our go-to way of getting NSF content out of the platform in a structured form for analysis and migration.
Reader / Author fields
Document-level access control. A Reader field determines who may view a document, an Author field who may edit it. In modern stacks this translates to row-level security or policy-based access.
iNotes / HCL Verse / Traveler
The web client (iNotes / Verse) and the mobile mail gateway (Traveler) on the Domino platform. Functional but dated in terms of UX; often a trigger for end users to ask for a replacement.
HCL Domino REST API / Volt MX
HCL's modern API layer (REST API) and low-code platform (Volt MX). The natural bridge for anyone who wants to modernise within the ecosystem without a full rebuild.
Why Appfront for your Notes migration?
- We understand both the old and the new: experience with DXL export, LotusScript readability and @-formula translation, combined with modern stacks (React, Astro, Node.js, .NET, PostgreSQL).
- No vendor lock-in afterwards: you receive the full source code, infrastructure-as-code and documentation. Switching supplier is no longer a drama.
- Pragmatic advice: wherever possible we recommend standard products (Microsoft 365, SharePoint, ServiceNow) and only build custom software where it genuinely makes sense.
- Compliance-first: GDPR, an ISO 27001-aligned way of working, audit trails by design, SSO via Entra ID, and encryption at rest and in transit as standard.
- Strangler fig over big bang: we phase the work wherever possible, with a live REST bridge between old and new so the business keeps running during the migration.
Our broader legacy modernisation services
A Notes migration rarely stands alone. It is often part of a broader programme: cloud migration, identity modernisation, BI integrations or a new digital workplace. Our broader services:
- Replacing legacy software — general approach for outdated systems
- IT modernisation consultant — strategic advice and programme management
- Modernising old software — modernisation within the existing architecture
- Platform modernisation — complete platform renewal
- Platform migration — delivery service
Frequently asked questions about replacing Lotus Notes / HCL Notes
Lotus Notes is the original product name (Lotus Development, since 1989). IBM bought Lotus in 1995 and kept using the name Lotus Notes for a long time; later it was referred to as IBM Notes. In 2019 IBM sold the entire Notes/Domino portfolio to HCL Technologies, and since then the client has been called HCL Notes and the server HCL Domino. Functionally it is the same platform — only the owner and the roadmap have changed.
A phased migration is almost always the wiser choice. We like to work with a strangler fig approach: we build a REST layer on top of Domino (HCL Domino REST API or custom middleware) and migrate applications one at a time. Non-critical databases are archived, critical databases are replaced with custom software, and eventually the Domino server is phased out. This keeps your business running and spreads the risk over several quarters.
Yes. Using DXL export, we extract forms, views, documents, attachments and metadata from every NSF database, including revision history and reader/author fields. During the migration we validate, both by sampling and at total level, that record counts and content are correct. For compliance, we provide a migration report per database. Notes remains available in read-only mode for archiving during and after the migration.
We extract all LotusScript code and @formulas from the NSF databases and work through them systematically, application by application, with your key users. The goal is a readable specification of what the logic is meant to do, not a one-to-one translation. Sometimes we find that rules are obsolete and can be dropped; sometimes a rule is still critical and we rebuild it in the modern stack. We document every decision.
Reader/author fields provide document-level access control and, in modern stacks, translate to row-level security in the database (PostgreSQL, SQL Server) or policy-based access at application level. We first map the existing matrix (which role may do what per document type) and then build a clean access model. This is often an improvement: existing Notes ACLs have often grown organically and contain duplicates or inconsistencies.
Yes. Your Domino environment stays operational throughout the migration; users simply carry on working in Notes. We synchronise via DXL export or the HCL Domino REST API. On the cutover date we take the new application live, switch Notes to read-only and schedule the final sunset of the Domino servers for a later quarter. So there is no big bang and no period without available data.
A major benefit of modernising: integrations that were complex or batch-based overnight in Notes become real-time as standard in a modern stack. We connect to Microsoft 365 (Graph API, SharePoint, Teams), Salesforce (REST), AFAS (Profit Web Services) and data warehouses using proven patterns. Read more about Microsoft 365 integrations or see our broad experience with ERP integrations.
Volt MX is a serious low-code layer from HCL that can expose NSF data via REST and provide cross-platform UIs. For organisations that want to keep working with HCL for years to come and retain their in-house Domino expertise, it is a legitimate option. For clients who want to decouple completely from HCL and reduce long-term TCO, a full rebuild on an open stack is often the wiser choice. We give independent advice for each situation.
GDPR questions are a frequently cited reason for migrating. On modern stacks, pseudonymisation, data minimisation, retention policies and audit trail export to SIEM tools (Microsoft Sentinel, Splunk) are standard. On older Domino versions this is more cumbersome and sometimes impossible. We recommend combining a Notes migration with a DPIA update, so that compliance and architecture are brought up to date in one go.
Ready for an honest audit of your Notes environment?
A Notes/Domino migration doesn't have to be daunting. With a structured approach — inventory, DXL extract, business rule specification, phased rebuild — you can move your legacy applications to a modern stack without the business grinding to a halt. We're happy to visit for a no-obligation NSF assessment, give you honest advice (Volt MX, full rebuild or hybrid) and build the programme that fits your portfolio.