How to Migrate Off Lotus Notes: A 6-Phase Roadmap

A Lotus Notes migration often starts with a simple request: move email to a modern platform. Then someone finds a local archive, a custom approval application, or a shared calendar that an important process still depends on. What looked like a data transfer becomes a business change with many connected parts.

The practical response is to divide the work into six clear phases. A Domino migration is a phased journey, not a single event. The same planning logic applies whether the destination is Microsoft 365 or Google Workspace. Each phase should have a defined outcome, an owner and a decision point before the next one begins.

Assess the current Lotus Notes or Domino environment

Assessment is where the project team discovers what is actually inside the environment. It is routinely underestimated because the visible mailboxes are only part of the picture. Archives may sit on servers or individual computers. Custom Notes Storage Facility (NSF) applications may support approvals, customer records or internal requests. Permissions, integrations and old links can create hidden dependencies that are easy to miss.

Start with an inventory that a business owner can understand. It should account for:

• Active, inactive and shared mailboxes, including their size and ownership.
• Server-based and local archives, along with retention requirements.
• Calendars, contacts, shared resources and delegated access.
• Custom NSF applications, workflows, forms and databases.
• Permissions, groups, connected systems and links between Notes content.

For every application or database, identify an accountable business owner and ask what work it supports. Usage alone does not tell the whole story. A lightly used approval process may still be essential at month-end. An active database may duplicate functionality already available elsewhere. The assessment should expose those distinctions before anyone commits to a schedule.

Security and access also belong in this phase. Document who can open sensitive records, who administers the current system and which accounts are no longer needed. Note encrypted content and any data that cannot be read without an existing credential. These findings influence the tools, sequencing and support needed later.

The output is a verified inventory, not a rough estimate. It determines scope, cost, risk and timing for everything that follows. A useful companion is Cortavo's HCL Domino cost and risk assessment, which helps decision-makers frame the business case before work begins.

Plan the migration path

Planning a Lotus Notes migration means assigning a destination and treatment to every item in the inventory. Microsoft 365 and Google Workspace are both legitimate destinations. The choice affects the specific migration tools and user experience, but the planning questions remain the same: what moves, what changes, what is retained, what is retired and who will own the result?

Place each mailbox, archive, application and workflow into one of four practical categories:

• Migrate: Move content that users still need into the selected platform.
• Replace: Recreate an important workflow with an appropriate service in the new environment.
• Archive: Preserve records that must remain available but do not need to stay active.
• Retire: Remove content or systems that have no valid business, legal or operational purpose.

Then set the migration order. A department that relies on a custom Notes workflow may need that replacement ready before its mailbox moves. Shared calendars and delegated mailboxes need owners and access rules. Historical archives may move on a different schedule from current mail. The plan should show these dependencies in plain language so leaders can approve priorities without interpreting a technical design.

A sound plan also assigns responsibility for communication, training, data validation, security decisions and post-cutover support. Define what success means for each group, including access to current mail, required history, calendars, contacts, files and daily workflows. This turns a migration off Lotus Notes into a set of controlled decisions rather than one high-risk deadline.

Organizations choosing Microsoft can use Cortavo's complete Microsoft 365 migration guide for more detail on that destination. Teams selecting Google Workspace should apply the same inventory, disposition, ownership and validation discipline.

Prepare users, data, mailboxes and applications

Preparation resolves the issues that would otherwise appear during the move. Clean up inactive accounts, confirm mailbox ownership and decide how much historical content each user needs. Match people and groups to their new accounts. Review shared access so assistants, teams and managers retain the permissions required for their jobs.

Archives need an explicit policy. Decide which data will move into an active mailbox, which will go to an approved archive and which can be removed under the organization's retention rules. Local NSF files deserve special attention because they can be invisible to administrators while still containing business records.

Applications require a similar treatment. Replacement workflows should be built and tested before the people who depend on them leave Notes. If records are being archived, confirm that authorized users can search and retrieve them in the new location. If an application will be retired, document the decision and tell affected users what replaces it.

For a Lotus Notes email migration, preparation should also cover calendars, contacts, attachments, recurring meetings and delegated access, not just messages. Test how linked or encrypted content will be handled. Record known exceptions so they can be checked during the pilot instead of becoming surprises at cutover.

Finally, prepare the support material. Create short instructions based on real tasks, such as finding archived mail, booking a shared room, opening a team calendar and accessing a replacement workflow. Identify who will answer questions during the pilot and cutover. Users should hear what is changing, when it is changing and where to get help before their working day changes.

Pilot the migration with a small group

The pilot proves that the plan works with real people and real work. Choose a small group that represents the organization rather than only selecting technically confident volunteers. Include users with shared mailboxes, calendar delegation, archives and at least one important workflow. Keep the group small enough that the project team can investigate every issue.

Move the pilot group's data and confirm that mail arrives in the correct place, calendars and contacts are usable, permissions work and required historical items can be found. Ask users to complete normal daily tasks in Microsoft 365 or Google Workspace. Their experience will reveal gaps that a migration log cannot, especially confusing folder structures, missing instructions or a replacement process that takes too many steps.

Adoption starts here. Give the pilot group role-based guidance before the move, accessible support during it and a short follow-up afterward. Capture their questions and revise the training materials for everyone else. A successful technical transfer with confused users is not a successful pilot.

Document what passed, what failed and what changed. Do not scale until the team understands the exceptions and can repeat the process. The pilot is the point to improve the runbook, validation checklist, communications and support coverage while the impact is contained.

Cut over to Microsoft 365 or Google Workspace

Cutover moves the remaining users to the selected platform in a controlled sequence. The destination may be Microsoft 365 or Google Workspace, and both require the same business discipline: clear timing, verified accounts, tested data transfers, visible support and a named decision-maker for each migration group.

Send communications that tell users exactly what to expect. They need to know when to stop working in Notes, where new email and files will appear, how calendars and contacts will behave, and what to do if something is missing. Managers should know which business workflows changed and how their teams will complete those tasks after the move.

Training should focus on the first working day, not on a tour of every platform feature. Show people how to perform the tasks they already rely on. Provide concise guides, scheduled sessions where useful and a clear support route. Without this work, an organization can change platforms while keeping the same daily friction.

During each cutover group, validate delivery, mailbox contents, calendars, contacts, shared access and the workflows required by that team. Track exceptions through resolution. Keep an agreed fallback available until the group passes its checks, and confirm completion with the business owner rather than relying only on a technical status report.

Decommissioning follows successful validation. Confirm that no current mail or active workflow still depends on Domino. Preserve required records and migration logs, remove obsolete access, and document the final disposition of every server, archive and application. Shut down legacy components only after their owners agree that the replacement or archive is usable. This closes the old environment without taking the sixth phase away from the work that protects the new one.

Operate the new environment

The data may have moved, but the migration is not finished. Microsoft 365 or Google Workspace now needs someone responsible for running it properly. That responsibility includes security, user support, administration, backups, access management and ongoing improvement. Leaving these duties split among busy employees simply replaces one fragile operating model with another.

Start by naming the owner for routine administration and the path for support. New starters need accounts and appropriate access. Departing employees need prompt offboarding. Roles, shared mailboxes, groups and external access need regular review. Backup and recovery procedures need owners and tests. Security settings and user guidance should continue to evolve as the organization and the platforms change.

Support is also part of adoption. Questions often appear after users have worked in the new environment for several days, not only during cutover. A dependable service desk helps people find mail, use shared resources and adjust to replacement workflows without routing every issue to the person who managed the project. Patterns in those requests can then guide better documentation, training and configuration.

This is where managed information technology (IT) protects the migration investment. Cortavo supports US small and mid-sized businesses for a flat monthly fee per user. Its 24/7/365 service desk provides an ongoing place for users to get help. Cortavo reports that around 95% of support requests are resolved remotely and that 85% of break-fix tickets are resolved within 48 hours, most in a single call.

Cortavo is platform agnostic and can run either Microsoft 365 or Google Workspace. That makes the operating model the natural continuation of the migration rather than a separate project. Administration, cybersecurity, help desk support and platform ownership can sit within one managed relationship, while onsite support is dispatched when needed.

Review the environment after cutover and at regular intervals. Look for recurring support questions, unused services, access that no longer fits a person's role and workflows that could be simplified. Beyond keeping the new platform available, the goal is to make it easier to use, easier to govern and clearly owned as the business changes.

Migrating off Lotus Notes means moving data into an environment someone is responsible for running properly. Assessment makes the work visible, planning sets the route, preparation removes avoidable problems, the pilot tests reality, cutover moves the business and operations sustain the result.

Talk with Cortavo about your Lotus Notes migration and ongoing IT operations.

Frequently Asked Questions

What are the steps to migrate off Lotus Notes?

Assess the current environment, plan a destination and treatment for every item, prepare users and data, run a representative pilot, cut over to Microsoft 365 or Google Workspace, and operate the new environment. Each phase should have an owner, clear acceptance checks and a decision before the project advances.

How long does each phase of a Lotus Notes migration take?

It depends on mailbox volume, archive size and the number of custom NSF applications. Permissions, workflow dependencies and data condition can also affect the sequence. The only reliable estimate comes after the assessment has established what exists and what each item requires. A schedule created before that point is an assumption, not a project plan.

What is the first step in a Domino migration?

Begin with a complete assessment of mailboxes, archives, applications, workflows, permissions and dependencies. Confirm business ownership and current use, then document the findings. This inventory sets the scope and determines the cost, timing and risk of every later phase.

What happens after the migration is done?

The new environment enters the operate phase. Someone must own user support, security, administration, backups, account and access changes, and ongoing improvement. Cutover completes the transfer, but disciplined operations protect the investment and help users work effectively over time.