Chat now with support
Chat with Support

Migrator for Notes to Exchange 4.16.3 - SSDM User Guide

About the Migrator for Notes to Exchange documentation Scenarios overview Migration to a proprietary Exchange
Migration to a proprietary Exchange target Pre-migration preparations Batch migration process Post-migration activities
Migration to Microsoft 365
Pre-migration preparations Batch migration process Post-migration activities
SSDM (per-desktop) migration

Visit our Quest online communities

Visit our Quest online communities

The Quest Communities web site is an interactive online community dedicated to issues relating to:

The community is designed to foster collaboration between Quest Migration experts and users. It’s a place where you can:

You can browse around the forums and the library, but to take full advantage of the community, post new threads, respond to messages from others, and rate our documents and downloads, you must Join the community. If you already have a Quest account or are a member of another Quest community, Sign in. The Sign in and Join features are both available from links near the top-right corner of the page at the Quest Communities web site.

Scenarios overview

About Migrator for Notes to Exchange scenarios

The Scenarios Guide provides an overview of the process instructions that show how Migrator for Notes to Exchange (MNE) is used within a migration project. The processes described include steps that are performed outside the scope of Migrator for Notes to Exchange—within Notes and Exchange, and with coexistence tools such as the Quest Coexistence Manager for Notes (CMN)—because the sequence and interplay among the solutions and environments are important. Flow charts illustrate the correct sequence of steps for common scenarios.

Most migrations follow a similar basic process, with variations to accommodate each organization's circumstances and needs—collectively called a scenario. Most variations to the process result from:

Migration Destination (the Exchange target type):
A proprietary Exchange environment is one whose hardware and software are wholly under the control of the migrating organization. Ordinarily this is a local Exchange network—on the same premises as the Notes source, or at least near enough to use high-performance network cables. But a proprietary Exchange target can also reside in a different location from the Notes source.
A hosted Exchange platform is one in which the hardware and software are owned and controlled by a third party. The hosting entity sells, as a service, access to disk space and the Exchange software. This service model is also known as cloud computing. The overwhelming majority of migrations to a hosted Exchange are to Microsoft 365.
Pre-Migration State of Existing Local Active Directory: Part of the migration process depends on whether your organization already has a local Active Directory running for login and security purposes and, if so, the state of any objects already provisioned there.
If you are migrating to a proprietary Exchange: Do you already have an Active Directory up and running? If an existing AD has already been provisioned, are its objects already mail-enabled, mailbox-enabled, or neither?
If you are migrating to Microsoft 365: Will you use a proprietary local Active Directory to provision the hosted environment and, if so, will you keep the local AD active after the migration? This method of provisioning permits single sign-on, also called identity federation, so users can access Microsoft 365 services with the same corporate credentials (user name and password) they use for the local Active Directory. Alternatively, you could provision Microsoft 365 without a local AD by using Migrator for Notes to Exchange to provision Microsoft 365 directly from the Notes/Domino source.

Different combinations of target types and states of an existing local AD produce an array of migration scenarios. This Scenarios Guide describes these combinations and summarizes the migration process for each:

This guide also describes three special scenarios, each of which would occur in combination with one of the previously described scenarios:

Offline Migration: A migration strategy in which Notes source data, previously extracted from Notes, is migrated directly to the Exchange target. This option supports scenarios in which it is impossible or impractical for the source and target servers to be connected to Migrator for Notes to Exchange at the same time and where data cannot be copied directly from the source to the target.
Phased (Staged) Migration Options: A migration strategy in which all but the most recent source data is “pre-migrated” to Exchange while users remain active in Notes so that the remaining Notes data (a smaller volume) can be migrated much faster. Often users can be migrated together in a final cutover migration. Users continue to receive and send mail and manage their calendars in Notes throughout the transition period while their older data is migrated to Exchange. If the final cutover can be accomplished in a single day or weekend, this strategy can eliminate the need for email, calendar, and free/busy coexistence.
Silent Mode Options: A strategy to configure the MNE Self-Service Desktop Migrator (SSDM), the per- desktop migration application, to hide some or all its screens, and obtain some or all of its required values from a pre-configured .ini file, thus eliminating or minimizing any need for interaction with the end user.

Chapters 2 and 3 of this guide provide step-by-step process instructions that cover these scenarios. Since all migrations follow the same basic process, with a few variations for particular needs and preferences, there are two linear procedures that are suitable for most scenarios:

Some steps in both scenarios are optional or conditional, depending on local variations in needs and preferences, and these are marked by an “If” icon and note:

Conditional Step: Conditional steps appear within the process instructions (in chapters 2 and 3) marked with this “If” branching-arrows icon.

Chapter 4 explains the administrative activities and considerations associated with per-desktop migrations which can occur with or without batch migrations, or may not be used at all—depending on your needs.

Migrator for Notes to Exchange pre-migration preparations and batch-migration processes are illustrated in two flow charts for each primary target type: proprietary (on-premises) and hosted (Microsoft 365). The flow charts appear in this chapter as introductory process overviews, and appear again as references with the process instructions in chapters 2 and 3.

The process instructions are also meant to serve as summary checklists so they do not include the operational details and screen-by-screen field notes for the Migrator for Notes to Exchange component applications. Many steps in these procedures refer to those details in particular chapters and sections of the Migrator for Notes to Exchange Administration Guide.

Migration to proprietary Exchange

A proprietary or on-premises Exchange environment is one where the hardware and software are wholly under the control of the migrating organization. A proprietary Exchange server is commonly in the same location as the source Notes environment, but might reside at another location.

When you are migrating to a proprietary Exchange, some steps in the procedures depend on the state of any objects that already exist in Active Directory (AD). An organization might have an existing Active Directory for login and security purposes. If user accounts already exist in Active Directory, Migrator for Notes to Exchange can use these objects to preserve the same credentials and security within the environment. AD objects must also be mail-enabled and mailbox-enabled before data can be migrated for those users. (An object is said to be mail-enabled when Exchange can accept a message for it because the object record contains a forwarding address to which mail can be routed. An object is said to be mailbox- enabled only when it has an active mailbox in Exchange.)

If your target AD has is not yet installed and configured, or if your migrating Notes users are not provisioned into the target AD, pre-migration preparations include optional steps to install and configure the target Exchange environment, and provision and mail-enable AD objects.

Since many organizations use the Coexistence Manager for Notes (CMN) Free/Busy Connector during the transition period, pre-migration preparations provision mail-enabled objects into Active Directory without mailboxes. Objects must be mail-enabled for mail-forwarding, but not before, so you do not create users’ mailboxes until prior to their migration—in the batch migration process (per user batch). This mitigates the effects of the Exchange free/busy limitation by limiting its duration (the time between mailbox creation and migration).

If mailboxes already exist in target Exchange, free/busy queries to not-yet-migrated Notes users do not work until those users are migrated to Exchange. Optional pre-migration steps can be skipped, but some configuration and administrative tasks are still required before the migration can begin.

All scenarios include optional steps for coexistence, as described later. And pre-migration preparations include steps to verify all object target/forwarding addresses to ensure correct mail routing.

In these scenarios, an administrator runs Migrator for Notes to Exchange applications using accounts that are configured with the necessary permissions to access the directories and user data in both the source and the target environments.

Step-by-step instructions and detailed notes for migrations to proprietary Exchange targets appear in chapter 2.

Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating