Get a Free Quote
Article

Domino Migration Playbook for CIOs: Stay, Modernize or Migrate Off

A Domino migration is any project that moves HCL Domino workloads: upgrading and moving Domino servers to new infrastructure or the cloud, consolidating Domino environments, or migrating mail and applications off Domino to platforms such as Microsoft 365. For most enterprises the decision is not all or nothing. The three strategic paths are to stay and optimize on Domino, modernize Domino and integrate it with other platforms, or migrate off, and many organizations combine them.

This playbook gives CIOs a decision framework, a program structure and the governance points that keep a Domino migration on track. RockTeam has delivered Lotus Domino migration projects on and off the platform for decades as part of our Domino consulting and support services.

Types of Domino Migration

Migration typeWhat movesTypical reason
Infrastructure migrationDomino servers to new hardware, operating systems, a new data center or cloud infrastructureHardware refresh, data center exit, cloud first strategy
Platform moveDomino servers on IBM i (AS/400) or other platforms to Windows or LinuxPlatform retirement, hardware cost and skills
ConsolidationMultiple Domino domains or servers into fewer, current serversMergers, cost reduction, simpler administration
Version migrationOlder Lotus or IBM Domino releases to current HCL DominoEnd of support and security
Mail migration off DominoMail, calendars and contacts to Exchange Online or another platformStandardizing on Microsoft 365
Application migrationDomino applications to other platforms, or retirementPlatform strategy or application replacement

Version upgrades are covered in our HCL Domino upgrade guide; this playbook focuses on the strategic decision and program.

Why Domino Migration Is on the CIO Agenda

  • Legacy application risk. Critical processes often run on custom Domino applications with little documentation or clear ownership.
  • Shrinking talent pool. Experienced Domino administrators and developers are harder to hire.
  • Security expectations. Zero trust, modern authentication and SOC integration are now baseline requirements.
  • Microsoft 365 standardization. Many organizations want Outlook, Teams and SharePoint as their standard tools.
  • AI strategy. Domino IQ and other AI platforms force a decision on where AI driven workflows will run.

Decision Framework: Stay, Modernize or Migrate Off

PathWhat it meansBest whenWatch for
Stay and optimizeUpgrade to current HCL Domino, harden security, right size licensingDomino runs well and hosts many critical applicationsKeeping Domino skills available
Modernize and integrateKeep Domino for applications, connect it with Microsoft 365, update interfaces, add Domino IQMail standardization matters, but applications are valuableCoexistence design and identity integration
Migrate offMove mail and applications to other platforms in stagesA firm platform decision, few complex applicationsHighest cost and risk when applications are extensive

When Staying on Domino Makes Sense

  • Complex applications. Heavily customized applications would be expensive and risky to re-platform.
  • Sovereignty and residency. Data must stay on infrastructure you control, which Domino supports fully on premises.
  • Operational stability. A well managed Domino environment with strong support is already performing.

The Hybrid Model Many Enterprises Choose

A common outcome is to move mail and calendaring to Exchange Online while keeping complex applications on a smaller, modernized Domino environment, with unified identity and security across both. See Lotus Notes to Office 365 migration for the mail side and Domino application modernization for the applications that stay.

Comparing Total Cost of Ownership

Cost areaStay or modernizeMigrate off
LicensingDomino entitlements, often reduced by right sizingNew platform subscriptions, plus Domino during coexistence
Migration effortUpgrades and selective modernizationMail migration, application rebuilds, coexistence and testing
OperationsDomino administration and supportNew platform operations, plus Domino until it is retired
RiskSkills availabilityBusiness disruption and lost application behavior

Key Steps in a Domino Migration Program

  1. Inventory and discovery. Catalogue servers, databases, applications, mailboxes, integrations and security dependencies.
  2. Dependency mapping. Map links between applications, data flows, authentication and external systems.
  3. Target selection. Decide which workloads stay on Domino, which move and where AI will fit.
  4. Pilot. Migrate representative workloads to validate tooling, performance and user adoption.
  5. Coexistence design. Plan directory synchronization, mail routing, free/busy and application access during transition.
  6. Phased cutover. Execute in waves, monitor closely and refine runbooks.
  7. Decommission. Retire servers only after applications, archives and retention needs are handled.

For Microsoft 365 bound workloads, this sequence fits with our enterprise Microsoft 365 migration checklist.

Handling Domino Applications, Not Just Mail

The hardest part of most Domino migrations is the long tail of applications. Classify each one to retire, replace, rebuild or re-platform; our article on migrating complex Notes applications explains how.

Governance, Security and Licensing

  • Identity. Align Domino authentication with your enterprise identity strategy, including SSO and MFA.
  • Retention. Preserve mail and application retention and legal hold requirements on the target platforms.
  • Licensing. Right size Domino entitlements as workloads move; see Domino licensing and renewals.

Planning a Domino migration?

Our Domino consultants will assess your environment and help you decide whether to stay, modernize or migrate, then deliver the program. RockTeam is an official HCL Business Partner. Start with a no cost assessment.

Talk to a Domino Consultant

Related Articles

Domino Migration FAQs

Any project that moves Domino workloads: moving Domino servers to new infrastructure or the cloud, consolidating environments, upgrading versions, or migrating mail and applications off Domino.

It depends on your applications, security requirements and platform strategy. Many enterprises choose a hybrid: mail moves to Microsoft 365 while complex applications stay on a modernized Domino environment.

Yes. Domino runs on cloud infrastructure, in hosted services and in containers, so servers can move from on premises data centers without leaving the platform.

It ranges from weeks for an infrastructure move to many months for a full migration off Domino with extensive applications. A pilot gives the most reliable estimate.

Each application is classified to retire, replace, rebuild or keep on Domino. Applications that stay can be modernized and integrated with the new platform.