Domino Application Migration: Moving Domino Apps to a Modern Stack

Still running the business, still invisible

Lotus Domino applications were the backbone of a generation of business process: approvals, time tracking, inventory forms, customer records. Built in the 1990s and 2000s, many are still running today — quietly handling workflows that employees open every single morning.

That's the trap. A Domino app that works doesn't feel urgent, so it gets left alone. But the platform around it — the vendor investment, the expertise, the integrations — has been winding down for years.

What a Domino app migration actually looks like

A Domino migration is not a mail migration. Moving Notes mail to Exchange or Microsoft 365 is well understood. Applications are different: they contain business logic, data models, and years of accumulated workflow decisions.

The practical path: inventory every database, map what each one actually does, and classify. Dead apps get retired. Simple apps get rebuilt on a modern database and web front end. Complex workflows get re-architected one function at a time, with data migrated and validated in stages.

Parallel running is the safety net — the new system and the old one coexist until users, data, and reports all match. Then the cutover is a formality, not a leap of faith.

The cost of waiting

Every year you wait, the skill pool shrinks. The people who can maintain Domino apps are retiring, and their knowledge leaves with them. Meanwhile the business keeps asking for mobile access, integrations, and faster changes — things Domino apps were never built to deliver.

The end state is a web app your team actually enjoys using, maintained by developers who are easy to hire, integrated with everything else you run, and owned by you — not by a platform's sunset schedule.