Lotus Notes & Domino Migration: The Complete Guide (2026)

If you searched for “Lotus Notes migration” or “Domino migration,” your organization still runs one of the oldest collaboration platforms in history — and you are not alone. Tens of thousands of companies worldwide still run mail, shared databases, and workflow applications on IBM Notes/Domino (now owned and maintained by HCL). The platform works, but it is aging: it cannot keep up with modern security expectations, mobile access, or cloud integration, and the skills to maintain it are disappearing.

This guide covers everything you need to plan a Notes or Domino migration: the real reasons to move, the two main destinations (Microsoft Exchange/365 and the modern web), how NSF application data is handled, the 7-step migration process, coexistence during transition, realistic cost and timeline numbers, the tools involved, and the risks that sink projects.

Why organizations migrate off Lotus Notes and Domino

The pressure is rarely one dramatic failure — it is a slow accumulation of problems:

• Ownership and roadmap. IBM transferred Notes/Domino to HCL in 2019. HCL keeps releasing versions, but the ecosystem is a fraction of what it was. Strategic investment, third-party tooling, and community support have all shrunk.
• Security and compliance. Modern email security, phishing protection, and compliance reporting (GDPR, PIPEDA, retention policies) are far harder to deliver on Domino than on modern platforms. Auditors increasingly flag legacy mail systems.
• Mobile and cloud expectations. Users expect flawless mobile mail, calendar, and document access. Domino's mobile story is workable but dated compared to Outlook/365 or modern web apps.
• Talent drain. Notes/Domino administrators and @Formula/LotusScript developers are retiring. Hiring replacements is slow and expensive, and the knowledge is concentrated in a few aging experts.
• Integration. Every modern SaaS — CRM, accounting, HR, support — integrates with Exchange/365 and web APIs. Domino integrations are custom, brittle, and costly to maintain.

When the email system is the weakest link in a security audit and the only person who understands the workflow databases is retiring, the migration stops being optional.

Two destinations: Notes to Exchange, or Notes to the web

Most migrations follow one of two tracks — and many organizations do both.

Lotus Notes to Exchange / Microsoft 365

Moving mail, calendar, contacts, and tasks from Domino to Exchange (on-premises or Microsoft 365) is the most common migration. It is well-trodden: mature tools exist to migrate mailboxes, and Microsoft provides guidance and support for the process.

• Pros: Proven path, mature tooling, huge talent pool afterward, best-in-class security and mobile experience.
• Cons: Only solves mail. The custom Domino applications (NSF databases) do not move with the mailboxes.
• Best for: Organizations whose Domino footprint is mostly mail plus a handful of simple shared databases.

Domino applications to a modern web stack

The NSFs that run approvals, requests, document management, and workflow are the hard part. These are rebuilt on modern stacks — React + Node.js, .NET, or low-code platforms — with the data extracted from NSF and the workflow re-implemented.

• Pros: Fixes the design debt, enables mobile and cloud, ends the LotusScript dependency forever.
• Cons: Real work: business rules live in @Formula, LotusScript, and agents that must be rediscovered and rebuilt.
• Best for: Workflow-heavy NSFs that still run core business processes.

The winning pattern for most clients: Exchange for mail, modern web for the custom applications, with a coexistence period where both run.

What happens to the data: NSF databases

Everything in Notes lives in NSF databases — mail files, shared address books, and every custom application. Data migration is where projects live or die:

• Mail data migrates mailbox-by-mailbox using mature migration tools that preserve folders, sent items, and calendar entries.
• Application data must be extracted from NSF into a modern database (SQL Server, PostgreSQL, or a document store). NSF structures (forms, views, rich text) do not map cleanly — every form needs a data model decision.
• Attachments and rich text need special handling: documents, embedded images, and file attachments must be extracted, stored, and re-linked in the new system.
• Access control and history — who could read/edit what, and the document history, are often as important as the content itself. Preserve ACLs and audit trails.

Rule of thumb: budget 40% of the project for data extraction and validation. Underestimating NSF data complexity is the most common reason Notes migrations overrun.

The 7-step Notes/Domino migration process

1. Discovery and inventory. List every Domino server, mail file, NSF application, agent, and integration. Identify what is actually used — many NSFs are dead code nobody has opened in years.
2. Application triage. Classify each NSF: migrate as-is, rebuild on a modern stack, replace with a SaaS product, or retire. This decision drives 80% of the cost.
3. Business-rule extraction. Interview the users. The real logic lives in @Formula, LotusScript, and agent code — document it before the experts retire.
4. Data model and architecture design. Design the target schema, API contracts, and the Exchange/365 tenant structure before touching production.
5. Coexistence setup. Run Notes and the new system in parallel: directory sync, mail routing between the two, and shared calendar visibility. Users must not notice the transition.
6. Migration and parallel run. Move mailboxes in waves, rebuild applications module by module, and validate real transactions against the old system.
7. Cutover and decommission. Freeze the old servers, archive the NSFs for audit and reference, and shut Domino down. Then the maintenance bill ends.

Tools for Notes and Domino migration

• Mail migration tools (commercial, e.g. Quest, Binary Tree, Transend) — automated Notes-to-Exchange/365 mailbox migration with folder and calendar fidelity.
• NSF data extraction tools — export NSF documents, rich text, and attachments into modern formats and databases.
• Directory synchronization — keep Notes names and Exchange identities in sync during coexistence so mail flows both ways.
• Automated regression testing — capture current application behavior before rebuilding, so parity can be proven.
• Custom rebuild tooling — modern frameworks (React, Node.js, .NET) plus database tools for the rebuilt applications.

Tools handle the mechanical moves. The judgment — which NSFs rebuild vs retire, how business rules map, how data transforms — is where an experienced partner earns their keep.

Cost and timeline: what to expect

Planning ranges for Canadian organizations (2026):

• Assessment and discovery: 2–4 weeks, typically $4,000–$10,000 CAD.
• Mail-only migration to Microsoft 365 (up to 200 mailboxes): 1–3 months, roughly $15,000–$50,000 CAD depending on data volume and coexistence needs.
• Application rebuilds: $25,000–$150,000+ CAD per NSF application, scaling with workflow complexity — this is the real budget driver.
• Full program (mail + 5–20 applications): 6–18 months, $100,000–$500,000+ CAD spread across phases.

These are planning ranges, not quotes. The dominant cost is almost never the mail migration — it is the custom NSF applications and the hidden business rules inside them.

Risks most Notes/Domino migrations ignore

• Undocumented applications. Nobody knows what some NSFs do — until they are turned off and a business process breaks. Inventory and triage first.
• Data transformation loss. Rich text, attachments, and ACLs are the first casualties of careless extraction. Test on real documents, not samples.
• Coexistence failure. If directory sync or mail routing breaks, users lose trust in the project within a day. Plan coexistence explicitly, with monitoring.
• Key-person risk. The admin or developer who understands the system retires mid-project. Extract their knowledge in writing during discovery.
• Zombie NSFs. Applications nobody uses keep costing money to migrate. Retire them instead — it is a legitimate outcome of triage.

Frequently asked questions

Is Lotus Notes still supported in 2026?

HCL continues to release and support Notes/Domino versions, so it is not disappearing tomorrow. But the practical problem is trajectory: shrinking ecosystem, shrinking talent pool, and growing security expectations that the platform struggles to meet.

Can we migrate Lotus Notes to Exchange without losing mail history?

Yes. Mature mailbox migration tools preserve folders, sent items, calendar entries, and attachments. The key is choosing a tool with good fidelity and testing on real mailboxes before the full run.

What about our custom Domino applications (NSFs)?

Mail migration does not move them. Each NSF is triaged: rebuild on a modern stack, replace with a SaaS product, or retire. Application triage is the single biggest cost lever in the project.

Do we have to migrate everything at once?

No — the standard pattern is coexistence: mail migrates in waves while Notes and Exchange run side by side, and applications migrate module by module. The old system only shuts down at final cutover.

What does Uphill Tech charge for a Notes/Domino migration?

We start with a fixed-cost assessment and triage, then quote per phase so you control the budget. Canadian rates, Canadian team, and the old system keeps running until you say the word.

Where Uphill Tech fits

We assess your Notes/Domino environment, then execute the migration in phases: mail to Microsoft 365 where that is the right home, and custom NSF applications rebuilt on React + Node.js + Tailwind (or .NET where that fits your team) — with coexistence, data preserved, and the old system running until cutover. You stay in business the whole time.

Start with the assessment — the first conversation is free: (204) 918-5534 or get in touch.