| Product Documentation
Efflux Migrator
Pre-requisites for Cross Forest Migration
This page lists minimum System Requirements for cross forest migration. For more details please consult our support team.
- Efflux will be installed in the target forest on a machine that has only the Exchange Management Shell installed. The machine should not host the Mailbox role or any other Exchange roles. In the case of Microsoft 365 (Office 365), Efflux will be installed in the source forest.
- Before commencing installation of Efflux, ensure that both source and target environments are functioning normally in terms of mail flow, without exceptions and are fully ready for migration.
- MRS Proxy endpoint should be enabled on the Mailbox servers in the source forest.
- The number of MRS Proxy concurrent connections should be set slightly larger than the default value for Exchange. See article.
- Ensure Microsoft Exchange Mailbox Replication service is running on Exchange servers in both the environments.
- For Exchange 2010, while on the target server, the URL: https://yourdomains.com/EWS/mrsproxy.svc to the source forest should browse without encountering certificate errors. Any certificate errors should be resolved before proceeding.
- For Exchange 2013 onwards, while on the target server (where Efflux is installed), the EWS URL must be resolvable, and HTTPS should be enabled on it.
- Create Send and Receive Connectors on both source and target environments.
- In case of export of mailbox passwords, ADMT tool is needed on the target server, Password Export Server on the source and a trust relationship established between the source and target DCs.
Microsoft does not provide any mechanism to expose or directly migrate existing mailbox passwords. As a result, Efflux uses Microsoft’s ADMT and Password Export Utility to migrate passwords to the target environment. Due to this process, a trust relationship between the source and target domains is required. - In case of Exchange 2010 the servers should be equipped with SP3 or above.
- Efflux communicates with the Exchange servers through Remote PowerShell therefore PS Remoting should be enabled on them.
Machine Where Efflux is installed
Efflux will be installed in the target forest on a machine that has only the Exchange Management Shell installed.
The following set of software and hardware is required on the machine:
Software Requirements |
Hardware Requirements |
||||||||
|
|
||||||||
Ports
Following ports should remain open for communication between the source and target servers:
| Port | Protocol | Description |
| 636 | LDAPS | Secure LDAP (LDAP protocol over TLS/SSL) |
| 389 | LDAP | Without SSL |
| 5985 - 5986 | WinRP HTTP/HTTPS | Microsoft Windows Remote Management uses port 5985 for HTTP and 5986 for HTTPS by default |
| 443 (TCP) | HTTPS | Mailbox Replication Proxy uses port 443 to communicate with other Exchange CAS servers via HTTPS |
| 135 (TCP) | RPC | To remain open on the source Exchange server |
Efflux does not support migrations in coexistence mode. Coexistence refers to the scenario where two versions of Exchange coexist in the same Active Directory. This in most cases happens when you’re already using an earlier version of Exchange, like Exchange Server 2010 or Exchange Server 2013, and now want to introduce a newer version like Exchange 2016 to the architecture. Here for the purpose of transitioning your mailboxes to the newer version, both the versions co-exist in the same Active Directory. Efflux does not support such scenarios as it’s built to deliver cross-domain and cross-forest migrations.