Organizations still running IBM Notes and HCL Domino face growing pressure to modernize their messaging and collaboration environment. Many IT leaders now plan to migrate Lotus Domino to Exchange as part of a wider move to Microsoft 365, and the project involves far more than moving mailboxes between two systems.
This guide walks through every stage of the work, the risks that derail schedules, and how Rivit handles both halves of the project. Rivit’sAppAnalyzer migration analysisandRevive application migrationplatforms were built for this exact problem, and they are why a Rivit project covers custom applications, not just mail.
Why Organizations Migrate Lotus Domino to Exchange
Lotus Notes and Domino have supported enterprise email, calendaring, and custom applications since the early 1990s. Many organizations built entire departments around Domino applications long before cloud collaboration platforms existed. Over time, the reasons to migrate Lotus Domino to Exchange have become harder to ignore.
Domino administrator and developer talent has become scarce. Fewer IT professionals train on the platform each year, which drives up the cost of support contracts and makes routine maintenance difficult to staff. Meanwhile, Microsoft Exchange and Microsoft 365 have become the default collaboration standard across most industries, so new hires arrive expecting Outlook, Teams, and SharePoint rather than a Notes client.
Security is another driver. Domino environments that have not been consistently patched or upgraded become a compliance liability, particularly in regulated sectors such as financial services, government, and healthcare. HCL’s repeated changes to the support timeline have made long range planning harder, and Rivit’s view onwhat the latest Domino support extension really meansis worth reading before treating an extension as a reason to wait. Add the rising cost of running on-premises Domino servers alongside a parallel Microsoft environment, and the business case to migrate Lotus Domino to Exchange becomes clear.
None of this makes the decision to migrate Lotus Domino to Exchange 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 an accurate picture of what they actually have. Projects that skip this step tend to uncover gaps only after the work is underway, when they are far more expensive to fix. Rivit begins every engagement at this point, because the inventory determines the budget, the sequence, and the realistic completion date.
→ Is your organization still maintaining a legacy Domino environment that is becoming harder and more expensive to support? Rivit can assess your current environment and build a realistic roadmap to migrate Lotus Domino to Exchange.Contact our teamto get started.
What a Project to Migrate Lotus Domino to Exchange Actually Involves
Mail, calendar, contacts, and task data follow a fairly predictable path into Exchange. Vendors have been moving that data for years, and the tooling is mature. The difficulty sits in the layer above it.
Domino was never only a mail platform. It was an application platform, and for twenty years it was an unusually productive one. Business users and departmental developers built approval workflows, claims processing, quality tracking, contract management, and dozens of other systems directly on top of the same infrastructure that delivered email. Those applications share the Domino directory, Notes authentication, and in many cases the mail router itself.
When an organization decides to migrate Lotus Domino to Exchange, the mail portion resolves the messaging problem and leaves the application problem untouched. Exchange has no equivalent for a Notes form, a view, or a LotusScript agent. Every one of those applications needs its own decision: rebuild, replace with a Microsoft 365 equivalent, archive, or retire.
This is the reason Rivit treats messaging migration and application modernization as a single project rather than two. Rivit scopes a project to migrate Lotus Domino to Exchange as one program with two workstreams, sequenced together. The organizations that separate them typically finish the mail move on schedule, then discover that fifty or a hundred applications still require a Domino server to stay online, which cancels most of the savings the project was meant to deliver. Rivit’s article on theroadblocks that stall Notes application migrationscovers this pattern in more detail.
The Rivit Process to Migrate Lotus Domino to Exchange
A successful project follows a structured sequence. Skipping steps, or treating the work purely as a mailbox move, is one of the most common reasons migrations run over budget or leave functional gaps. Below is the process Rivit uses with organizations planning to migrate Lotus Domino to Exchange.
Step 1: Discovery and application inventory
Before a project plan to migrate Lotus Domino to Exchange exists, organizations need a full inventory of every mailbox, distribution list, and custom Domino application in use. This step is consistently underestimated. Many Domino environments have grown organically for 15 to 20 years, and IT teams rarely have visibility into every application still running in production, who owns it, or how often it is used.
Rivit’s AppAnalyzer platform was built to solve this problem. It scans the Domino environment and produces a complete application inventory, including usage statistics, technical complexity scoring, dependency mapping, schema to SQL mapping, and workflow detection based on analysis of the actual code rather than documentation. IT leaders get a data backed view of the environment instead of relying on institutional memory, which is usually incomplete once key staff have left. Rivit offers thisapplication inventorywork as a no-cost assessment, which means the business case can be built before any budget is committed.
Step 2: Assessing migration complexity
Once the inventory exists, each application and mailbox needs a complexity assessment. Mail, calendar, and contact data migrates predictably. Custom applications built on the Domino platform behave differently. Some are simple forms that can be retired or rebuilt in days. Others contain years of embedded business logic, workflow automation, and integrations with ERP, finance, or line of business systems.
This is where organizations planning to migrate Lotus Domino to Exchange decide which applications to migrate as they are, which to modernize into a new architecture, which to archive, and which to retire outright. AppAnalyzer supports that decision by flagging retirement candidates and modernization opportunities based on real usage data, complexity scores, and effort estimates rather than guesswork. Rivit’s guidance onapplication rationalizationexplains how to apply those scores when portfolio budgets are tight.
Step 3: Planning mailbox and directory migration
With the inventory and complexity assessment complete, technical planning begins. This covers the migration method, mapping the Domino directory to Active Directory or Microsoft Entra ID, and establishing coexistence between Domino and Exchange during the transition.
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 with this method because of the time required to provision and move larger volumes.
Larger organizations planning to migrate Lotus Domino to Exchange typically need a staged or hybrid approach instead, moving mailboxes in batches over several weeks while maintaining free and busy lookups and mail routing between the two systems. Rivit sequences these batches against the application inventory, so departments whose applications are being rebuilt in the same window are not moved twice.
Step 4: Data migration and coexistence
During this phase, mail, calendar entries, contacts, and tasks move from Domino to Exchange in batches. Coexistence tooling keeps free and busy calendar lookups working across both systems so meetings can still be scheduled during the transition. This step also validates that distribution lists, shared mailboxes, and resource calendars transfer correctly, since those are commonly overlooked until users report problems after cutover.
Organizations that migrate Lotus Domino to Exchange without a coexistence strategy usually see a spike in help desk tickets during the transition, as users lose visibility of colleagues’ availability or find mail routing unreliable between systems still mid-migration. Rivit’s field notes onintegrating Notes with Outlookcover several of the configuration details that cause these tickets.
→ Are you worried that a mail cutover will overwhelm your service desk before the application work even begins? Rivit can plan your coexistence and batching strategy around your actual user population.Contact our teamto walk through it.
Step 5: Application modernization decisions
This is the point where a project to migrate Lotus Domino to Exchange becomes significantly more complex than a mailbox migration. Domino applications have no direct equivalent inside Exchange or Microsoft 365. Every custom application still in active use needs its own plan, 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.
Rivit’s Revive platform is built for this stage. Revive uses AI-assisted code generation to accelerate redevelopment, preserving existing business logic and workflow rules while rebuilding the application on a modern stack with React front ends, Java or Node.js back ends, and PostgreSQL or MongoDB databases. Forms become React components. Views become data grids. Agents become services.
Rivit reports that Revive converts between 70 and 90% of application code automatically, with confidence scores attached to every transformation so low confidence conversions are flagged and addressed rather than failing quietly. Instead of manually rewriting every application from scratch, teams modernize a far larger share of the portfolio inside the same project timeline. For most enterprises, this is the difference between a project to migrate Lotus Domino to Exchange that finishes and one that stalls halfway.
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. This involves updating MX records, confirming Autodiscover settings, and running a final delta sync to capture 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 the migration is declared complete. Rivit validates application by application as well, so each rebuilt system is signed off by its business owner before the next one moves.
Step 7: Post-migration support and archiving
Not every Domino application or mailbox needs to reach Exchange at all. Many organizations hold years of historical Domino data that must be retained for compliance or legal reasons but does not need to live in a production system. Rivit’sDcom application archivingplatform preserves that data in a secure, searchable archive with full-text search, PDF rendering, and compliance-grade retention, which lets organizations retire the underlying Domino infrastructure and stop paying for servers and licenses that exist only to hold records. Rivit’sapplication decommissioning guidecovers the retirement sequence in detail.
→ Planning to migrate Lotus Domino to Exchange but unsure where to start with your application inventory? Rivit’s AppAnalyzer gives 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 to migrate Lotus Domino to Exchange hit predictable obstacles. Understanding them in advance makes it easier to budget realistic time and resources.
Incomplete application inventories. Many IT teams underestimate how many Domino applications remain in active use, particularly departmental applications built outside formal IT governance. Discovering those applications mid-project rather than during planning is one of the most common causes of schedule slippage. An AppAnalyzer scan resolves this in days rather than the weeks of stakeholder interviews a manual inventory requires.
Underestimating custom application complexity. Mail migration tools handle mailboxes well and do not 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 faster than replacements can be trained. When that knowledge goes, so does the ability to document what an application does and why. Code analysis fills that gap, because the application itself still holds the rules even when nobody can explain them.
Coexistence gaps. Free and busy lookups, shared calendars, and cross-platform mail routing all need careful configuration during the transition. Gaps here create a poor user experience and 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 after active mailboxes have moved. Without an archiving strategy, organizations either keep costly legacy servers running indefinitely or risk losing access to records they are required to produce.
Underestimating timeline and cost. A cutover or staged mailbox migration alone can finish in weeks. Add dozens or hundreds of custom applications that require redevelopment, and the true project timeline is measured in months. Organizations that do not account for the application side from the outset frequently find budgets and timelines falling short midway through. Rivit’s analysis ofmeasuring the true impact of a Domino app migrationsets out the cost categories that usually get missed.
A well-scoped project to migrate Lotus Domino to Exchange accounts for all of these factors before the first mailbox moves. Treating messaging migration and application modernization as one connected effort is the clearest way to avoid the surprises above, and it is how Rivit scopes every engagement.
→ Struggling to plan around these challenges? Rivit has guided organizations through every stage of the work required to migrate Lotus Domino to Exchange.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. The team has specialized in the Notes and Domino platform for roughly 25 years, first as metalogic Consulting and since 2011 as Rivit Technology Partners, and that background is combined with proprietary AI-powered tools that address the application work most migration projects overlook.
AppAnalyzer removes the guesswork from planning. Instead of relying on outdated documentation or staff memory, organizations receive a full inventory of applications, usage data, complexity scoring, dependency graphs, and effort estimates before committing to a timeline or a budget. Because Rivit offers this as a no-cost assessment, IT leaders can build an internal business case and set realistic expectations with executive stakeholders before any money is spent.
Revive addresses the part of the project mailbox tools cannot reach. 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 accumulate. Applications emerge running on a modern, cloud-ready architecture with React front ends and Java or Node.js back ends, backed by PostgreSQL or MongoDB databases.
Every conversion draws on verified patterns from completed migrations, which is what allows Rivit to quote effort with confidence rather than hedging with contingency. That accuracy is what keeps a plan to migrate Lotus Domino to Exchange intact once delivery begins.
For data that must be retained but does not need to stay active, Dcom preserves historical information in a secure, searchable, compliant archive while the servers that once hosted it are retired. Organizations reduce infrastructure costs immediately, even while application modernization work continues in parallel.
Rivit also providesenterprise application developmentservices for organizations that want to rebuild Domino applications with new capability rather than replicate what already exists. That is often the right call when a legacy application no longer matches how the business operates. Rivit’slegacy system modernizationwork covers the same ground for non-Domino platforms.
→ 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.
The Rivit Solutions Behind Every Domino to Exchange Migration
Organizations that set out to migrate Lotus Domino to Exchange usually arrive with one problem in mind and find several more during discovery. Rivit’s solution set is structured so that a single team covers the whole sequence rather than handing work between vendors.
AppAnalyzer migration analysis
AppAnalyzeris the starting point for organizations that need to know what they have before they decide what to do. It produces the application inventory, usage statistics, complexity scoring, dependency mapping, migration readiness assessment, retirement candidates, and cost estimates that turn a modernization conversation into a funded project. It is offered at no cost.
Revive application migration
Reviveis Rivit’s AI-powered migration platform. It handles Lotus Notes application migration and Domino application modernization through AI-assisted code generation, preserving legacy workflows while rebuilding on React, Java, Node.js, PostgreSQL, and MongoDB with cloud-ready deployment. Revive is the reason Rivit can commit to timelines measured in weeks for applications that traditional rewrites quote in years.
Dcom application archiving
Dcomhandles the applications and data that should not be rebuilt. It supports regulatory compliance, long-term retention, secure historical access, searchable archives, legacy system retirement, and application decommissioning, which together let organizations eliminate unnecessary legacy servers without losing historical information. Removing archiving candidates from the plan to migrate Lotus Domino to Exchange reduces rebuild scope before a line of code is written.
Enterprise application development
Rivit’s enterprise application developmentpractice covers custom enterprise software, business application redevelopment, cloud-native applications, workflow automation, system integration, database modernization, and API development. This is the route for organizations using the migration as an opportunity to improve a process rather than reproduce it.
Domino infrastructure and support services
Not every organization is ready to move tomorrow. Rivit’sDomino infrastructure and support serviceskeep mail and application environments stable and supportable in the meantime, covering daily administration, version upgrades, readiness assessments, and Domino application development for teams that still need to maintain or web-enable existing systems while a longer modernization plan takes shape.
→ Not sure which combination of Rivit solutions your plan to migrate Lotus Domino to Exchange needs? A short conversation and a free analysis will tell you.Contact our teamto find out.
Industries Rivit Supports When Organizations Migrate Lotus Domino to Exchange
The core sequence used to migrate Lotus Domino to Exchange is similar across sectors, but the risks and priorities shift depending on the industry.
Finance and bankingorganizations typically carry strict data retention and audit requirements that must be settled before any Domino server is decommissioned. Migration plans need to account for regulatory reporting obligations alongside the technical cutover. Rivit’s work in this sector includes rebuilding amajor bank’s branch operations platform,and clients such as Scotiabank, Manulife, Desjardins, and AGF have relied on Rivit for modernization work.
Government and civil agenciesoften run Domino applications supporting constituent services or internal case management, where downtime during a migration has direct public impact. Rivit’s public sector work focuses on minimizing service disruption throughout the transition.
Manufacturingorganizations frequently rely on Domino applications for production tracking, quality management, or supply chain workflows built decades ago and never documented in detail. Rivit rebuilds these applications with modern integrations to ERP and shop floor systems.
Utilitiesproviders maintain Domino applications tied to asset management, outage tracking, and field service workflows, where reliability during the transition is critical to operations. Rivit sequences this work carefully so operational systems stay available throughout the project.
Life sciences and healthcareorganizations face some of the strictest data privacy requirements of any sector, and legacy Domino applications frequently hold protected health information. Rivit makes sure both the mail migration and the application modernization work meet the compliance standards these organizations operate under. The same discipline applies to Rivit’spharmaclients, where validation and audit trails add another layer to the plan.
Transportation and logisticsoperators run scheduling, dispatch, and documentation workflows on Domino that cannot pause for a migration window, which makes application-by-application cutover essential rather than optional.
Technologycompanies, including independent software vendors, sometimes ship commercial products built on Domino. Rivit has handled that scenario, including aDomino-based investment accounting platformand atax solutions provider’s complex Domino applications,where the migrated product had to keep serving the vendor’s own customers.
→ Not sure how your industry’s compliance requirements affect your migration timeline? Rivit can help you migrate Lotus Domino to Exchange on a plan that meets your regulatory obligations.Contact our teamto discuss your requirements.
Where Rivit Works and Who Rivit Works With
Rivit is headquartered in the Toronto area, in Vaughan, Ontario, and supports clients across Canada, the United States, and internationally. The company describes itself as having the largest team of Notes and Domino experts in North America, which matters for a specialized project of this kind. Domino expertise is thin on the ground and getting thinner, and the depth of bench determines whether a migration proceeds on schedule or waits for a single available specialist.
Discovery, code analysis, redevelopment, and archiving all run remotely, so geography rarely constrains a project to migrate Lotus Domino to Exchange. Rivit works within North American business hours for organizations that want overlapping working time with their delivery team, and has delivered for organizations including Toyota, Honda, Health Canada, and Entegris alongside its Canadian financial services clients.
Rivit is also a premier HCL Domino partner, which gives organizations a direct escalation path on platform issues during a transition period rather than a dead end. For a company still deciding between upgrading Domino and leaving it, Rivit’s assessment ofthe state of HCL Dominois a useful place to start.
→ Wondering whether your organization’s location or time zone complicates a Domino migration? It usually does not, and Rivit can confirm that in a single call.Contact our teamto check.
Why Choose Rivit to Migrate Lotus Domino to Exchange
Most migration vendors focus on moving mail from one system to another. Rivit takes a wider view, built on roughly 25 years of hands-on work developing and maintaining Notes and Domino applications before the company moved into modernization services. That history matters, because understanding how Domino applications were built in the first place is what makes it possible to preserve their business logic accurately during modernization instead of losing functionality end users depend on daily.
Rivit combines that platform expertise with proprietary tools purpose-built for this type of project. AppAnalyzer answers what is actually in the environment and what it will take to move it. Revive accelerates redevelopment of custom applications with AI-assisted code generation. Dcom addresses the historical data that must be preserved but does not belong in a production system.
Enterprise application development services support organizations that want to use the migration to improve, rather than replicate, existing workflows. Together they cover every stage required to migrate Lotus Domino to Exchange, from the first scan to the last decommissioned server.
There is also a difference in how the work is quoted. Rivit’s estimates come from analysis of the actual application code, not from a workshop and a rule of thumb, which is why Rivit publishes effort reduction figures of 70 to 90% rather than a range with no basis behind it. Organizations planning to migrate Lotus Domino to Exchange get more than a technical migration vendor. They get a team that understands both the legacy platform they are leaving and the modern architecture they are moving toward, which is what keeps critical functionality intact along the way.
→ Ready to start planning your migration? Rivit can 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 obligations, staffing constraints, and years of accumulated business logic that most organizations cannot 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 without unpleasant surprises. Rivit’s combination of deep Domino expertise and AI-powered tools like AppAnalyzer, Revive, and Dcom helps organizations finish this work with less risk, a clearer timeline, and business logic that stays intact.
→ Is an aging Domino environment holding back your Microsoft 365 plans? Rivit will map your application portfolio and give you a realistic scope to migrate Lotus Domino to Exchange before you commit to anything.Contact our teamto book your free analysis.
→ Want more modernization insight before you decide? Follow Rivit onLinkedInfor migration guidance, client stories, and Domino platform updates.
Rivit FAQs on How to Migrate Lotus Domino to Exchange
How long does a Rivit project to migrate Lotus Domino to Exchange usually take?
Timelines vary with mailbox count and the number of custom Domino applications in use. A mailbox-only migration for a smaller organization can finish in a few weeks, while a full project including application modernization for a large enterprise runs across several months. Because Revive automates 70 to 90% of code conversion, Rivit projects generally complete faster than traditional rewrites, and AppAnalyzer’s inventory data establishes a defensible timeline before work begins rather than after.
Can Rivit migrate custom Domino applications to Exchange directly?
No, and no vendor can. Exchange handles mail, calendaring, and contacts, and has no equivalent for a custom Domino application. Those applications have to be rebuilt on a modern platform, replaced with a Microsoft 365 equivalent, or retired, and those decisions are made during assessment, before the work to migrate Lotus Domino to Exchange begins. Rivit’s Revive platform is built specifically to accelerate that redevelopment, converting forms into React components, views into data grids, and agents into services while preserving the workflow rules behind them.
What is the difference between a cutover and a staged migration on a Rivit project?
A cutover migration moves all mailboxes at once and suits smaller organizations. A staged migration moves mailboxes in batches over a longer period, which larger enterprises usually require because of directory and coexistence complexity. Rivit sequences those batches against the application inventory, so a department is not migrated for mail in one month and disrupted again for application cutover in the next.
Do we need to keep Domino servers running while Rivit runs the migration?
Yes, until cutover is complete and validated. Domino and Exchange run in coexistence during the transition so users retain access to historical mail and calendar data while new mail routes through Exchange. Rivit’s aim is to shorten that overlap period as much as the application portfolio allows, since running both environments in parallel is where much of the avoidable cost sits.
What does Rivit do with historical Domino data we are required to retain?
Organizations do not need to keep active Domino servers running purely to hold history. Rivit’s Dcom platform preserves that data in a secure, searchable archive with full-text search, PDF rendering, and compliance-grade retention, so the underlying infrastructure can be retired while auditors and regulators keep access to the records they may request later.
How does Rivit’s AppAnalyzer help before we migrate Lotus Domino to Exchange?
AppAnalyzer scans the existing Domino environment and produces a full application inventory, complexity scoring, dependency mapping, and cost estimates, giving IT leaders the data to plan accurately instead of relying on incomplete documentation. Rivit offers the assessment at no cost, which means an organization can build its business case to migrate Lotus Domino to Exchange before committing any budget.
Does Rivit recommend modernizing Domino applications or retiring them?
It depends on how actively an application is used and how much business logic it holds. AppAnalyzer’s usage data identifies which applications are strong modernization candidates and which are better retired or archived, so effort concentrates where it returns the most value. In most portfolios Rivit assesses, a meaningful share of applications turn out to be retirement or archiving candidates, which reduces the scope of the rebuild considerably.
Why work with Rivit instead of a general migration vendor?
General migration vendors focus on moving mailboxes. Rivit’s background in both Domino development and modern application architecture means the messaging migration and the application modernization work sit with one team, which reduces the risk of losing business logic or missing dependencies. With the largest team of Notes and Domino experts in North America and roughly 25 years on the platform, Rivit brings specialist depth that generalist vendors cannot staff.