Organizations that still run IBM Notes and HCL Domino are under growing pressure to modernize their messaging and collaboration environment. Many IT leaders are now planning to migrate Lotus Domino to Exchange as part of a broader move toward Microsoft 365, but the process involves far more than moving mailboxes from one system to another.
This guide walks through each stage of a successful migration, the risks organizations commonly encounter, and how proper planning protects business continuity. Along the way, we’ll show how Rivit’s application discovery and modernization expertise helps enterprises complete an IBM Notes migration with less disruption and greater confidence.
Why Organizations Migrate Lotus Domino to Exchange
Lotus Notes and Domino have supported enterprise email, calendaring, and custom applications for decades. Many organizations built entire departments around Domino applications long before cloud collaboration platforms existed. Over time, however, the reasons to migrate Lotus Domino to Exchange have become harder to ignore.
Domino administrator and developer talent has become scarce. Fewer IT professionals are trained on the platform each year, which drives up the cost of support contracts and makes routine maintenance more difficult to staff. At the same time, Microsoft Exchange and Microsoft 365 have become the default collaboration standard across most industries, which means new hires often expect Outlook, Teams, and SharePoint rather than Notes clients.
Security is another driver. Domino environments that haven’t been consistently patched or upgraded can become a compliance liability, particularly in regulated industries such as financial services, government, and healthcare. Add in the rising cost of maintaining on-premises Domino servers alongside a parallel Microsoft environment, and the business case to consolidate onto Exchange becomes clear.
None of this means the decision to migrate Lotus Domino to Exchange is simple. Domino environments frequently include hundreds of custom applications built on top of email and calendaring, and those applications rarely migrate on their own. Before any technical work begins, organizations need a clear picture of what they actually have. A Lotus Notes migration that skips this step tends to uncover gaps only after the project is already underway, when they’re far more expensive to fix.
→ Is your organization still maintaining a legacy Domino environment that’s becoming harder and more expensive to support? Rivit can assess your current environment and help you build a modernization roadmap.Contact our teamto get started.
Understanding the Process to Migrate Lotus Domino to Exchange
To migrate Lotus Domino to Exchange, a successful migration follows a structured sequence. Skipping steps, or treating the project purely as a mailbox move, is one of the most common reasons migrations run over budget or leave gaps in functionality. Below is the process we recommend to any organization planning to migrate Lotus Domino to Exchange.
Step 1: Discovery and Application Inventory
Before writing a project plan, organizations need a complete inventory of every mailbox, distribution list, and custom Domino application in use. This step is frequently underestimated. Many Domino environments have grown organically for 15 to 20 years, and IT teams often don’t have full visibility into every application still running in production, who owns it, or how frequently it’s used.
Rivit’s AppAnalyzer platform was built specifically to solve this problem. It scans the Domino environment and produces a complete application inventory, including usage statistics, technical complexity scoring, and dependency mapping between applications. This gives IT leaders a data-backed view of the environment instead of relying on institutional memory, which is often incomplete once key staff have left the organization.
Step 2: Assessing Migration Complexity
Once the inventory is complete, each application and mailbox needs to be assessed for migration complexity. Straightforward mail, calendar, and contact data typically migrates in a fairly predictable way. Custom applications built on the Domino platform are a different story. Some are simple forms that can be retired or rebuilt quickly. Others contain years of embedded business logic, workflow automation, and integrations with other enterprise systems.
This is the stage where organizations decide which applications should be migrated as-is, which should be modernized into a new architecture, which should be archived, and which can be retired outright. AppAnalyzer supports this decision by flagging retirement candidates and modernization opportunities based on actual usage data and cost estimates, rather than guesswork.
Step 3: Planning Mailbox and Directory Migration
With the inventory and complexity assessment complete, the technical planning phase begins. This includes deciding on a migration method, mapping the Domino directory to Active Directory or Microsoft Entra ID, and establishing coexistence between Domino and Exchange during the transition period.
According toMicrosoft’s own migration documentation, a cutover migration supports moving fewer than 2,000 mailboxes at once, though Microsoft recommends migrating no more than 150 mailboxes using this method due to the time required to provision and migrate larger volumes.
Larger organizations planning to migrate Lotus Domino to Exchange typically need a staged or hybrid approach instead, migrating mailboxes in batches over several weeks while maintaining free/busy lookups and mail routing between the two systems.
Step 4: Data Migration and Coexistence
During this phase, mail, calendar entries, contacts, and tasks move from Domino to Exchange in batches. Coexistence tools keep free/busy calendar lookups working between the two systems so meetings can still be scheduled across both platforms during the transition. This step also includes validating that distribution lists, shared mailboxes, and resource calendars transfer correctly, since these are commonly overlooked until users report problems after cutover.
Organizations that migrate Lotus Domino to Exchange without a coexistence strategy often see a spike in help desk tickets during the transition period, as users lose the ability to see colleagues’ availability or send mail reliably between systems still in mid-migration.
Step 5: Application Modernization Decisions
This is where a Lotus Domino to Exchange migration project becomes significantly more complex than a typical mailbox migration. Domino applications don’t have a direct equivalent inside Exchange or Microsoft 365. Organizations need a separate plan for every custom application still in active use, whether that means rebuilding it as a modern web application, replacing it with a Microsoft 365 equivalent such as Power Apps or SharePoint, or retiring it entirely.
Rivit’s Revive platform is built for exactly this stage. Revive uses AI-assisted code generation to accelerate the redevelopment of Domino applications, preserving existing business logic and workflow rules while rebuilding the application on a modern stack using React front ends, Java or Node.js back ends, and PostgreSQL or MongoDB databases. Instead of manually rewriting every application from scratch, teams can modernize a much larger share of the application portfolio within the same project timeline.
Step 6: Cutover and Validation
Cutover is the point where mail routing shifts fully to Exchange and the Domino mail environment is decommissioned for messaging purposes. This typically involves updating MX records, confirming Autodiscover settings, and running a final delta sync to capture any mail that arrived during the cutover window. Validation should include spot-checking mailbox contents, confirming shared mailbox permissions, and testing mobile device and Outlook client connectivity before declaring the migration complete.
Step 7: Post-Migration Support and Archiving
Not every Domino application or mailbox needs to move to Exchange at all. Some organizations have years of historical Domino data that must be retained for compliance or legal reasons but doesn’t need to live in an active production system. Rivit’s Lotus Notes archiving services allow organizations to preserve that historical data in a secure, searchable format while retiring the underlying Domino infrastructure, reducing licensing and server costs without losing access to records that regulators or auditors may request later.
→ Planning to migrate Lotus Domino to Exchange but unsure where to start with your application inventory? Rivit’s AppAnalyzer can give you a complete, data-backed view of your environment at no cost.Contact our teamto schedule an assessment.
Common Challenges When Organizations Migrate Lotus Domino to Exchange
Even well-planned projects run into predictable obstacles. Understanding these challenges in advance makes it easier to budget realistic time and resources.
Incomplete application inventories. Many IT teams underestimate how many Domino applications are still in active use, particularly departmental applications built outside formal IT governance. Discovering these applications mid-project, rather than during planning, is one of the most common causes of schedule slippage.
Underestimating custom application complexity. Mail migration tools handle mailboxes well, but they don’t touch custom Domino applications. Organizations that treat a Lotus Notes migration as purely a mailbox project are frequently surprised when business-critical workflow applications are left with no migration path at all.
Loss of institutional knowledge. Domino developers and administrators with deep knowledge of legacy applications are retiring or leaving organizations faster than replacements can be trained. When that knowledge leaves, so does the ability to accurately document what an application does and why.
Coexistence gaps. Free/busy lookups, shared calendars, and cross-platform mail routing need careful configuration during the transition period. Gaps here create a poor user experience and can undermine confidence in the project even when the underlying migration is going well.
Compliance and data retention requirements. Regulated industries often need to retain years of historical Domino data even after migrating active mailboxes. Without a clear archiving strategy, organizations either keep costly legacy servers running indefinitely or risk losing access to records they’re required to retain.
Underestimating timeline and cost. A cutover or staged mailbox migration alone can be completed in weeks. Add in dozens or hundreds of custom applications that require redevelopment, and the true project timeline is often measured in months, not weeks. Organizations that don’t account for the application side of the project from the outset frequently find their budgets and timelines falling short midway through.
A well-scoped Domino migration accounts for all of these factors before the first mailbox is ever moved. Treating the messaging migration and the application modernization work as a single connected project, rather than two separate efforts, is one of the clearest ways to avoid the surprises above.
→ Struggling to plan around these challenges? Rivit has helped organizations navigate every stage of the IBM Notes migration process.Contact our teamto discuss your project scope.
How Rivit Reduces Risk When You Migrate Lotus Domino to Exchange
Rivit approaches every Domino migration to Exchange as more than a mailbox move. Decades of hands-on Domino development experience, combined with proprietary AI-powered tools, allow Rivit to address both the messaging migration and the application modernization work that most migration projects overlook.
AppAnalyzer removes the guesswork from planning. Instead of relying on outdated documentation or staff memory, organizations get a full inventory of applications, usage data, technical complexity scoring, and cost estimates before committing to a project timeline or budget. This no-cost assessment gives IT leaders the data they need to build a business case and set realistic expectations with executive stakeholders.
Revive addresses the part of the project that mailbox migration tools can’t touch: the custom applications. Rather than manually rebuilding every workflow application from the ground up, Revive uses AI-assisted code generation to accelerate redevelopment while preserving the business logic that took years to build. Applications come out the other side running on a modern, cloud-ready architecture with React front ends and Java or Node.js back ends, backed by PostgreSQL or MongoDB databases.
For data that needs to be retained but doesn’t need to remain active, Rivit’s Lotus Notes archiving services provide a secure, searchable, and compliant way to preserve historical information while retiring the servers that once hosted it. This lets organizations reduce infrastructure costs immediately, even if application modernization work is still in progress.
Rivit also provides enterprise application development services for organizations that want to rebuild Domino applications with new functionality rather than simply replicate what already exists. This is often the right approach when a legacy application no longer matches how the business actually operates today.
→ Want to understand how much of your Domino environment could be modernized alongside your Exchange migration? Rivit can walk you through the assessment process.Contact our teamto learn more.
Industry Considerations for a Lotus Domino to Exchange Migration
The core migration process is similar across industries, but the risks and priorities shift depending on the sector.
Financial services and banking organizations typically have strict data retention and audit requirements that must be addressed before any Domino server is decommissioned. Migration plans need to account for regulatory reporting obligations alongside the technical cutover. Rivit’s experience infinancial servicesmigrations helps organizations balance modernization speed with compliance obligations.
Government and public sector agencies often run Domino applications that support constituent services or internal case management, and downtime during a migration can have a direct public impact. Rivit’s work withgovernment and civil agenciesfocuses on minimizing service disruption during the transition.
Manufacturing organizations frequently rely on Domino applications for production tracking, quality management, or supply chain workflows that were built decades ago and never documented in detail. Rivit’smanufacturingexperience includes rebuilding these applications with modern integrations to ERP and shop floor systems.
Utilities providers often maintain Domino applications tied to asset management, outage tracking, or field service workflows, where reliability during the transition is critical to operations. Rivit’sutilitieswork emphasizes careful sequencing so operational systems remain available throughout the project.
Healthcare and life sciences organizations face some of the strictest data privacy requirements of any industry, and legacy Domino applications frequently contain protected health information. Rivit’slife sciences and healthcare experience ensures that both the mail migration and any application modernization work meet the compliance standards these organizations require.
→ Not sure how your industry’s compliance requirements affect your migration timeline? Rivit can help you plan a project that meets your regulatory obligations.Contact our teamto discuss your requirements.
Why Choose Rivit to Migrate Lotus Domino to Exchange
Most migration vendors focus exclusively on moving mail from one system to another. Rivit takes a broader view, built on decades of hands-on experience developing and maintaining Domino applications before the company shifted into modernization services. That background matters because understanding how Domino applications were built in the first place makes it possible to preserve their business logic accurately during modernization, rather than losing functionality that end users depend on every day.
Rivit combines that platform expertise with proprietary tools purpose-built for this exact type of project. AppAnalyzer answers the question of what’s actually in the environment and what it will take to move it. Revive accelerates the redevelopment of custom applications using AI-assisted code generation. Lotus Notes archiving addresses the historical data that needs to be preserved but doesn’t need to remain in an active production system. Enterprise application development services support organizations that want to use the migration as an opportunity to improve, not just replicate, existing workflows.
Organizations planning to migrate Lotus Domino to Exchange gain more than a technical migration partner. They gain a team that understands both the legacy platform they’re leaving behind and the modern architecture they’re moving toward, which reduces the risk of losing critical functionality along the way.
Ready to start planning your migration? Rivit can help you scope the project with a no-cost application assessment.Contact our teamtoday.
Conclusion
Deciding to migrate Lotus Domino to Exchange is rarely just a mail platform decision. It touches application portfolios, compliance requirements, staffing constraints, and years of accumulated business logic that most organizations can’t afford to lose. A structured process, starting with a full application inventory and ending with a clear archiving strategy, gives IT leaders the confidence to move forward without unexpected surprises along the way.
Rivit’s combination of deep Domino expertise and AI-powered tools like AppAnalyzer and Revive helps organizations complete this journey with less risk, a clearer timeline, and business logic that stays intact throughout the transition.
Migrate Lotus Domino to Exchange: FAQs
How long does it take to migrate Lotus Domino to Exchange?
Timelines vary significantly based on mailbox count and the number of custom Domino applications in use. A mailbox-only migration for a small organization can take a few weeks, while a full migration including application modernization for a large enterprise often takes several months. AppAnalyzer’s inventory data helps establish a realistic timeline early in the project.
Can Domino custom applications be migrated to Exchange directly?
No. Exchange handles mail, calendaring, and contacts, but it has no direct equivalent for custom Domino applications. These applications need to be rebuilt on a modern platform, replaced with a Microsoft 365 equivalent, or retired. Rivit’s Revive platform is designed specifically to accelerate this redevelopment work.
What’s the difference between a cutover and a staged migration?
A cutover migration moves all mailboxes at once and works best for smaller organizations, while a staged migration moves mailboxes in batches over a longer period, which is typically necessary for larger enterprises with more complex directory and coexistence requirements.
Do we need to keep our Domino servers running during the migration?
Yes, until cutover is complete and validated. Domino and Exchange typically run in coexistence during the transition so users can still access historical mail and calendar data while new mail routes through the new system.
What happens to historical Domino data we’re required to retain for compliance?
Organizations don’t need to keep active Domino servers running solely for historical data. Rivit’s Lotus Notes archiving services allow that data to be preserved in a secure, searchable format so the underlying infrastructure can be retired.
How does AppAnalyzer help before we migrate Lotus Domino to Exchange?
AppAnalyzer scans the existing Domino environment and produces a full application inventory, complexity scoring, and cost estimates, giving IT leaders the data they need to plan the project accurately instead of relying on incomplete documentation.
Is it worth modernizing Domino applications instead of just retiring them?
It depends on how actively an application is used and how much business logic it contains. AppAnalyzer’s usage data helps identify which applications are strong modernization candidates and which are better suited for retirement, so the project focuses effort where it delivers the most value.
Why should we work with a specialist instead of a general migration vendor?
General migration vendors typically focus only on moving mailboxes. Rivit’s background in both Domino development and modern application architecture means the messaging migration and the application modernization work are handled by the same team, reducing the risk of losing business logic or missing critical dependencies along the way.