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

Step 1: Provision Notes groups into Microsoft 365

Groups are typically provisioned separately, after all users are migrated in the Batch migration process (the preceding section of this chapter). Since the only data associated with a group is its member list, group migration consists only of the group being provisioned into the target directory. Use the MNE Groups Provisioning Wizard to provision groups either directly from Notes to Microsoft 365, or to a local “staging” AD from which you can use Microsoft AD Sync tool to provision the groups from the local AD to Microsoft 365.

Before you run the Groups Provisioning Wizard, you can divide the groups into collections using the MNE Collection Wizard for convenient processing. If necessary, you can update group membership and attributes in the SQL database (via TSV export and import) prior to provisioning the groups into Active Directory. For instructions, see the Groups Provisioning Wizard chapter of the Migrator for Notes to Exchange Administration Guide.

To provision groups before all Notes users are migrated, check the Message Delivery Restrictions for any Exchange group to which you want Notes users to be able to send messages. Any such Exchange group must be of the universal distribution type to be mail-enabled.

In the Exchange Management Console under Recipient Configuration | Distribution Group, select and double-click the group you want to edit.
Click the Mail Flow Settings tab and highlight Message Delivery Restrictions and click Properties.
Clear the check box for Require that all senders are authenticated.
Click Save and restart the Exchange transport service.

Step 2 (optional): Configure ongoing directory coexistence

Conditional Step: This step applies only if you will also maintain a local proprietary AD in addition to the hosted platform.

If you are going to keep a local Active Directory up and running, you can configure the Microsoft Online Services AD Sync tool to regularly synchronize the local and hosted AD. Refer to Microsoft documentation to configure the Microsoft AD Sync tool for these ongoing synchronizations.

If you intend to keep your Domino directory running for a time, or indefinitely, you should also configure the CMN Directory Connector to regularly update the Domino directory and your local AD.

Step 3: Update mail routing

Migrator for Notes to Exchange is commonly used to automatically update mail forwarding in both systems to ensure proper routing during the migration. Migrator for Notes to Exchange can set and remove forwarding rules in both environments, as long as the mail routing domains or smart hosts are properly configured.

When the users and groups are all migrated, routing can be permanently updated to direct external incoming (Internet) mail to Microsoft 365 instead of to the Notes environment. This step includes modifying the MX record(s) to redirect the inbound external mail. In some environments, updating mail routing also includes updating routing tables and/or firewall modifications.

Most organizations prefer to update mail routing only after the last user has been migrated, to minimize change before and during the migration process. But the MX modification can occur at any time after all Notes users have been provisioned into Microsoft 365 as mail-enabled objects. (If routing is updated to send inbound mail to Microsoft 365 before a particular user is provisioned, there will be no forwarding address in Microsoft 365 to relay the user’s mail back to Notes.) The timing of this step depends on how you provisioned Microsoft 365:

If you provisioned Microsoft 365 from a local AD using Microsoft AD Sync: Notes users are provisioned into Microsoft 365 as mail-enabled objects in the Pre-migration preparations.
If you provisioned Microsoft 365 directly from the Notes/Domino source: Notes users are not provisioned into Microsoft 365 until prior to their migration, per user batch.

Step 4: Post-migration cleanup

To clean up after the last user has been migrated:

Verify the Notes server is inactive. Ensure that the Notes server is no longer processing mail traffic or utilized for active applications.
If you were using SMTP mail coexistence: Delete the temporary mail routing MX domain(s) you created in the Pre-migration preparations to support routing between Notes and Microsoft 365 during the transition. Now that all users have been migrated to Microsoft 365 and inbound traffic is routed directly to Microsoft 365, the temporary routing domain(s) should no longer be required.
If you no longer need the Notes environment: After you have verified Notes is inactive, you may take a final backup and decommission the environment.
Related Documents

The document was helpful.

Select Rating

I easily found the information I needed.

Select Rating