A company can move every employee mailbox and still be unable to switch off Domino. The usual reason sits outside the inbox: an NSF database still runs an approval, stores a shared archive or supports a daily workflow. That gap makes the 2026 market for Lotus Notes migration tools easier to misunderstand than a normal email software comparison.
The current choices are also narrower than older round-ups suggest. Quest and Teamstudio still publish products for Domino work, while the HCL partner network offers a service-led route. BitTitan MigrationWiz and CloudM Migrate no longer list Domino or Notes as a supported source on their current platform pages. That distinction matters before a business spends time testing, budgeting or planning a cutover.
This article compares those named options as they exist now. Readers who need the wider sequence can use Cortavo's complete 2026 migration guide. For an assessment of a specific environment, contact Cortavo.
A product list is useful only when the evaluation criteria match the estate. Destination is the first filter. A tool that writes only to Exchange or Microsoft 365 cannot serve a direct Google Workspace migration. Workload is the second. Mail, calendars, and contacts are different from custom databases, workflows and archives. The third is delivery capacity: buying software still leaves somebody responsible for discovery, testing, cutover and user support.
Use the following questions to keep a shortlist grounded:
NSF support deserves explicit weight. Mailbox migration is usually the more straightforward half. Custom applications, shared databases, approvals, workflows and archives create the harder decisions: retire, replace, rebuild, modernize, or preserve. A mailbox tool cannot make those decisions simply because it can read an NSF file.
Quest offers Migrator for Notes and Migrator for Notes to Exchange. The products migrate Domino mail, calendars, contacts, to-do lists and notebook entries. They can also handle databases such as Rooms and Resources, while retaining text formatting, images, attachments and links.
The operational controls are a genuine strength. Quest offers a pre-migration assessment of the Notes and Domino environment, a central console, job templates and result reports. Those capabilities suit a team that already has enough internal IT capacity to plan and operate the project but wants structured software for the transfer itself.
The destination limit is decisive. Quest's listed targets are on-premises Exchange, hosted Exchange and Exchange Online in Microsoft 365. There is no Google Workspace destination. A Google-bound business should remove Quest from its direct-migration shortlist rather than assume that broad mailbox support implies a Google path.
Quest covers mail and associated resources well within the published scope, but it should not be mistaken for a complete answer to custom NSF applications. Shared business logic, approvals, and workflows still need their own disposition plan.
Teamstudio has two relevant products, and together they address a different part of the problem. Teamstudio Usage analyzes a Domino estate to show which databases and user IDs remain active and which are dormant. That evidence gives a business a practical starting point for deciding what to retire, replace or rebuild.
Teamstudio Export archives or migrates Notes and Domino data to modern platforms. It can convert NSF content into formats including HTML and PDF, and move data to Microsoft 365, SharePoint, cloud databases and custom applications.
This is the option in the named set that is aimed most directly at the application and archive problem rather than the mailbox. That does not make it an automatic winner. It makes Teamstudio especially relevant when a Domino estate contains important shared databases, historical records or custom applications that cannot be treated as ordinary email.
The pairing also illustrates why discovery belongs before product selection. If usage analysis shows that many databases and IDs are dormant, a business may avoid migrating material nobody uses. Active applications can then receive a deliberate plan instead of being discovered late in mailbox testing.
HCLSoftware runs a Business Partner program that includes resellers, system integrators, solution partners and managed services partners. HCLTech also publishes a Domino alliance. This is a service-led route: the buyer engages a partner rather than purchasing a standalone migration product and running it alone.
HCLTech's Advisor tool inventories a Domino estate and sorts applications into four paths: re-platform, retire, move to cloud and modernize. That makes the route relevant when application decisions are central to the project and the business wants outside help assessing them.
A partner and a tool solve different problems. Software executes supported data movement. A partner assesses what needs to move, plans the work, manages risk, supports users and checks that the destination works after cutover. The partner route may suit a company without spare internal capacity or one whose NSF applications make the work broader than mailbox transfer. The business should still ask what is included, who owns each decision and how exceptions will be handled.
BitTitan MigrationWiz is still recommended for Domino in older round-ups, but BitTitan has dropped Domino from its current published source support. Its sources and destinations page no longer lists Lotus Notes or Domino. It continues to list Microsoft 365, several Exchange versions, Google Gmail and generic IMAP among its supported mailbox sources.
CloudM Migrate has also dropped Domino from its current published source support. Its supported-platforms page no longer lists Lotus Notes, HCL Notes or Domino as a source platform.
Both changes are checkable on the vendors' own current pages. There is no need to speculate about why Domino was dropped or attach an unsupported date to the change. The practical conclusion is enough: neither product is a direct Domino migration choice based on its current published source list.
This is the clearest sign that the Domino tool market has thinned. A buyer following a 2023 listicle, or an AI-generated recommendation based on stale pages, can easily shortlist software that cannot directly read the source data. Current vendor documentation should therefore be a basic gate in every evaluation.
BitTitan and CloudM both still support generic IMAP sources into Microsoft 365 and Google Workspace. A Domino estate can therefore expose mail over IMAP and use that route. For a Google-bound business, this is a real option where Quest has no Google Workspace destination.
The tradeoff is severe for a full business migration. IMAP is an email-only protocol. Calendars, contacts and tasks do not come with it, and metadata fidelity suffers. It also does nothing for NSF applications, shared databases, approvals or workflows. The route can make sense when the accepted scope is email only, but it should not be described as equivalent to a Domino-aware migration.
That distinction belongs in the written scope and the pilot. A successful transfer of sample messages proves only that email can move. It does not prove that the business can retire Domino or that users will have everything they need in the destination.
For Microsoft-bound mailbox content, Quest offers the clearest dedicated product path in this set, including assessment, central control and reporting. For estate analysis, application data and archives, Teamstudio addresses the part of the problem that ordinary mailbox comparisons miss. The HCL partner network offers a partner-led route for organizations that need assessment and execution support rather than software alone.
BitTitan MigrationWiz and CloudM Migrate should not appear on a 2026 shortlist as direct Domino-source tools. Their IMAP support keeps them relevant only as limited email routes into Microsoft 365 or Google Workspace. That limitation needs to be accepted deliberately, not discovered after licensing.
No product should be selected from a feature page alone. Test a proof of concept against real mailboxes, archives and representative NSF data. Define what must be preserved, inspect the results and record what requires manual work. For a separate view of delivery approaches, cost factors and likely timing, see Lotus Notes to Office 365 migration options, costs and timeline.
A migration ends one project, but it starts a new operating routine. Someone must manage users, security, access, backups, support, and the wider workplace environment after cutover. That work is outside the core job of a data-moving tool.
Cortavo provides fully managed IT for US small and mid-sized businesses for a flat monthly fee per user. It supports both Microsoft 365 and Google Workspace and includes a 24/7/365 service desk. Businesses that want the migration and the ongoing environment considered together can review Cortavo's end-to-end email migration services. The point is not that every migration requires a managed provider. It is that the owner of post-cutover operations should be named before the tool is chosen.
Schedule a Domino migration assessment with Cortavo.
There is no single winner for every estate. The deciding factors are the destination platform, whether custom applications and archives are in scope, and how much internal capacity is available. Quest is focused on Microsoft mailbox destinations and related content. Teamstudio is more relevant to application data, archives and usage analysis. An HCL partner may fit when assessment, planning and delivery need to be handled as a service. A proof of concept should confirm the choice against real data.
Some can address more than email, but support varies sharply. Quest migrates mail and associated content, including databases such as Rooms and Resources, but custom application logic still needs a separate plan. Teamstudio Usage helps identify active and dormant databases, while Teamstudio Export can archive or migrate NSF content into HTML, PDF, Microsoft 365, SharePoint, cloud databases and custom applications. HCLTech's Advisor supports disposition decisions. IMAP moves email only.
Licensing is usually priced per user or per mailbox, while application work is normally priced separately. A list price alone cannot show the manual remediation a particular estate will require. Run a proof of concept on representative real data, inspect fidelity and failures, and estimate the labor around the tool. That is what tells a buyer whether the licence is worth purchasing.
A small business with capable internal IT, a mailbox-focused scope and time to test may be able to run a tool directly. A managed service is more suitable when internal capacity is limited, users need coordinated support or custom NSF applications broaden the project. The deciding issue is not company size alone. It is whether someone can own discovery, testing, cutover, exception handling and ongoing administration.
A migration tool moves the data types and destinations it supports. A migration partner assesses the estate, helps decide what should move, builds the plan, manages risk, supports users and verifies the environment after cutover. The tool can be part of the partner's work, but it does not replace those responsibilities. Buyers should identify who owns both the transfer and ongoing operations.
1 min read
.png?width=30&name=MKT%20Email%20Marketing%20300x300px%20(18).png){kind=small}
Team Cortavo : Apr 30, 2026, 2:04:04 PM
Managing Microsoft 365 and Google Workspace Coexistence Running both Microsoft 365 and Google Workspace is rarely a strategic choice. Usually, a...
1 min read
Team Cortavo : Dec 23, 2025, 4:54:28 PM
How Secure is Cloud Storage for Protecting Your Sensitive Data? When you think about it, you’re already relying on the cloud. Your email, files you...
-2.png)
1 min read
The start of a new year is the perfect time for small businesses to set fresh goals and plan for growth. A key part of this planning? Getting your IT...
.png)
Team Cortavo