Lotus Notes to Exchange migration with ZeroIMPACT
Use an intuitive project management console to accurately migrate email and calendar data.
Notes Migrator for Exchange gives you fast, accurate migration and mitigates your risk of data loss. You can easily transfer email, personal address books, calendars, archives, and more. This Lotus Notes migration solution also allows you to move multiple mailboxes simultaneously. Data can be transitioned directly to hosted platforms, and administrative tasks such as mailbox creation and mail-routing can be automated. It also preserves the integrity of your users’ mailboxes, ensuring a seamless and accurate migration from Lotus Notes.
- Finish fast – To finish your migration faster you can transition multiple mailboxes simultaneously on each migration server and install multiple migration consoles to accommodate large-scale migration projects.
- Complete control – Using an intuitive central console, you can monitor your migration project.
- Anytime scheduling – Automate administrative tasks to schedule migration jobs when they will have the least impact to your network bandwidth and operations.
- Self-Service desktop migrator – Easily enables you or your end users to silently migrate local and server data to Exchange, personal archives, or PST.
- Quick Cloud – You can migrate Notes data directly to Office 365 or a hosted Exchange, reducing the risk of data loss and ensuring a quick and secure migration.
- Know, Then Go – To better plan for your project, you can perform a pre-migration assessment of your Notes and Domino environments.
Notes Migrator for Exchange requires the installation and configuration of multiple components on various machines. The admin's migration workstation in particular will host an unusual combination of tools, developed by different vendors, and the combination can cause compatibility problems on some machines. Be sure to see the more detailed System Requirements in the NME Pre-Migration Planning Guide or Quick-Start Guide for tips to get multiple applications from different vendors to cooperate when installed together on an admin workstation.
Supported Exchange platforms include:
- Office 365
- Hosted Exchange
- Exchange 2013
- Exchange 2010
- Exchange 2007
Lotus Domino Server Versions Supported
- 8.5.0–8.5.3 (inclusive)
- 8.0.0–8.0.2 (inclusive)
- 7.0.0–7.0.4 (inclusive)
- 6.x or 5.x
MS Exchange Server and Active Directory Supported
|Exchange Versions Supported:||If migrating to Office 365 via MS DirSync:|
|Access to a Microsoft SQL Server is required, installed on the admin's migration workstation or on a separate server, with a minimum of 20GB free disk space. Note: |
SQL Server Command Line Query Tool also must be installed, on the NME admin migration workstation. You can download it free from the same link provided in the NME Autorun for the Microsoft SQL 2005 Native Client Edition.
On end-user desktops (if running the SSDM):
Operating Systems supported
|32- or 64-bit edition of any of: |
|Required Outlook client||32-bit edition (only) of Outlook 2013, 2010, 2007 or 2003.|
|Required Notes client||Must be running a Lotus Notes client. Unicode support requires one of these versions: |
Also required on SSDM end-user desktops:
- Microsoft .Net Framework version 2.0 must be installed on each end user's workstation.
- If end users will run the SSDM application from a network share (rather than from each user's own local copy): Each user's workstation must also have either .Net 3.5 SP1 (or later) installed, or a Code Access Security (CAS) policy granting full trust to SSDM in the network share. (See Before Running the SSDM in chapter 4 of the NME Scenarios Guide for instructions to set the required CAS policy.)
- May be a virtual machine, but a dedicated "actual" machine will likely yield better performance.
- The MAPI DLLs required to perform a migration must be those that are part of Outlook, not the downloadable Exchange "server" MAPI.
- Prior to running the SSDM: Any antivirus software must be configured to not scan the Quest program files directory or %temp% directory, or may simply be turned off, but may be restored after the program runs. If an antivirus scan misinterprets an NME temporary file as a threat, it will try to "clean" the file, which will generate an error when the SSDM program call fails.
Migration Server Requirements (computer running NME admin components)
(Requirements for migration from Domino BlackBerry to Exchange BlackBerry are documented separately below.)
Windows Server 2003
Win Server 2008
SP2 or R2
SP1 or SP2
Office 365, other
yes, but 32-bit editions only
Important: NME requires the English-language edition OS/PowerShell on the admin workstation.
Migration server hardware:
Also required for ALL destination Exchange versions, including Office 365:
Also required for Exchange 2013, 2010 and Office 365 (only):
Also required for Exchange 2007 (only):
Also required for Admin Account Pooling feature (Admin Guide chapter 14):
Requirements for Migration from Domino BlackBerry to Exchange BlackBerry
Supported Source: Notes BlackBerry Enterprise Server 4.1.x
Required on the Migration Webservice endpoint for BlackBerry migration:
On the server hosting the SSDM Scheduling Utility web service: ASP.net version 2.0 must be installed.
Must have network access.
Required Accounts & Permissions:
Important: In addition to the hardware and software requirements specified above, NME features require the configuration of admin accounts for access to directory and user data in both Notes and Exchange. For these additional configuration requirements, be sure to see the more detailed System Requirements in the NME Pre-Migration Planning Guide or Quick-Start Guide.