Chat now with support
Chat with Support

Migrator for Notes to Exchange 4.15.2 - Scenarios 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's Office 365
Pre-migration preparations Batch migration process Post-migration activities
SSDM (per-desktop) migration

Directory coexistence with Office 365

A Microsoft-hosted Active Directory (for Office 365) imposes strict access restrictions that prevent direct directory coexistence between Notes and a hosted AD. With Quest’s CMN, however, you could establish a "two-step" coexistence between Domino and Office 365 by this process:

1
Configure the CMN Directory Connector for bidirectional updates between Notes and a local, proprietary Active Directory.
2
Configure Microsoft’s AD Sync tool to synchronize the local AD with Office 365.

The combination of the two configures an effective directory coexistence between Domino and Office 365.

Mail, calendar and free/busy coexistence with Office 365

Mail, calendar and free/busy coexistence with Office 365

Office 365 introduces new options for coexistence and hybrid deployments. These include identity and calendar federation options that can be leveraged for Notes projects. Microsoft’s calendar federation requires a local Exchange server, but enables bi-directional free/busy lookups with Office 365 users.

Quest’s CMN can leverage this configuration to provide free/busy lookups with Notes users, although free/busy queries in the Exchange-to-Notes direction require that Notes users (awaiting migration) not already have an Exchange mailbox, which in turn requires that Office 365 be provisioned from a local AD by Microsoft’s AD Sync tool. (This is explained in more detail in the Provisioning and mailbox creation section above.)

Quest’s CMN also enables direct email and calendar coexistence with Office 365.

Offline migration

Migrator for Notes to Exchange supports scenarios where it is impossible or impractical for the source and target servers to both be connected to Migrator for Notes to Exchange at the same time, so the data cannot be copied directly from the source to the target. An offline migration is a strategy in which Notes source data that was previously extracted from Notes is migrated directly to the Exchange target. An offline strategy can be valuable:

•
if problematic bandwidth makes direct connection impractical (e.g., if the source and target servers are far apart—geographically and/or from a network perspective); or
•
if the Domino environment is managed by a third party that does not allow admin access; or
•
in a disaster scenario, where the Domino server is destroyed, but backup NSF files survive.

An offline migration can be accomplished by either of these two approaches:

•
Notes source data is saved to replica or otherwise-disconnected NSFs, and Migrator for Notes to Exchange’s Data Migration Wizard then migrates from the NSF files directly to Exchange.
•
Migrator for Notes to Exchange’s Data Migration Wizard migrates Notes source data to PST files (rather than directly to an online Exchange target), and the PST files are then imported into the Exchange target by some other application. Quest’s Migration Manager for PSTs would be a good choice for this purpose.

The subtopics below provide specific requirements and guidance for these offline scenarios.

How to save Notes data to NSF or PST files

Remember in either case (NSFs or PSTs) that you will need:

•
the main Notes Address Book containing all the objects you intend to migrate;
•
all mail files and archives;
•
all personal address books; and
•
an admin ID file that can decrypt all of the above.

Saving Notes data to NSFs is a native Notes/Domino feature. If necessary, see the IBM documentation for more information.

Using Migrator for Notes to Exchange to migrate Notes data to PST files
•
Configure Migrator for Notes to Exchange’s Data Migration Wizard to migrate all data types to PST files either in the program UI, or by setting these parameters in the Task Parameters or Global Defaults:
[General]
PABDest=PST
ServerMailDest=PST
ArchiveDest=PST
•
Migrator for Notes to Exchange may try to query and set information in the Exchange environment as part of the migration conversions, but the attempt will return an error if there is no direct connection to an Exchange server. To disable these verifications, set ACLs=0 in the [General] section of Task Parameters or Global Defaults.
•
In Migrator for Notes to Exchange’s Notes Migration Manager, on the Notes Server Configuration screen: Make sure the Always use these values checkbox is not checked.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating