EdbMails Office 365 Migration — Installation

EdbMails can be installed on any Windows computer that has connectivity to the source and target servers. The sections below cover the specific connectivity requirements for each migration scenario.

Office 365 to Office 365 (Tenant-to-Tenant)

Install EdbMails on any Windows machine with a reliable connection to both the source and target Office 365 tenants. The software uses Exchange Web Services (EWS) to connect to both sides, so there's nothing to install on either tenant and no connectors to touch. Stable internet is really the only hard requirement.

Office 365 to Exchange Server

For migrations to an on-premises Exchange server, install EdbMails on a Windows machine with network access to the target Exchange environment. Use the most capable machine you have available — with large mailboxes or high mailbox counts, the hardware does matter. No agents are needed on either side.

Office 365 to IMAP

Any Windows machine with internet access to both the source Office 365 tenant and the target IMAP server will work. EdbMails connects to the target using IMAP protocol, which means it works with virtually any IMAP-enabled service — Outlook, Gmail, Zoho Mail, Zimbra, Yahoo Mail, Hotmail, and most other mail platforms that support IMAP. Nothing needs to be installed or configured on the destination side.

Office 365 to Hosted Exchange

Any Windows machine with internet access to both the source Office 365 tenant and the target hosted Exchange server will work. EdbMails connects to both sides over EWS, covering all major hosted Exchange providers, including Rackspace, GoDaddy, and Intermedia. No agents, no connectors, nothing extra to set up on either end.

Office 365 to PST

You'll need a Windows machine with Microsoft Outlook installed and a stable internet connection to the source Office 365 tenant. Outlook handles the PST file format, so it needs to be present on the same machine running EdbMails. One practical thing worth checking before you kick off a bulk export is disk space. PST files can get large quickly, and running out of space mid-export is an avoidable headache.

PST to Office 365

For this one, you need a Windows machine with Outlook installed and internet access to the target Office 365 tenant. EdbMails reads the PST file through Outlook, so both need to be on the same machine. Also make sure the PST file itself is reachable from that machine. Whether it's sitting locally or on a network share, EdbMails needs a direct path to it before the migration can start.

Installation Steps

Getting EdbMails installed takes just a few minutes. Here is what to do:

• Download the setup file from the EdbMails website.
• Double-click the downloaded file to start the installation wizard.
• Hit ‘Next’ when the wizard opens

  

• Go through the license agreement and click ‘I Agree’ to move forward.

  

• The installer defaults to a standard folder location — that works fine for most setups, so unless you have a reason to put it elsewhere, just leave it.

  

• EdbMails launches automatically once installation is done and is ready to use straight away.

  

Impact on Your IT Infrastructure

Installing EdbMails makes a small number of changes to your environment. None of these touches your actual mailbox data or disrupts how your servers run. They simply give the tool the access it needs to do its job.

Operating System

If .NET Framework 4.0 or later is not already on the machine, EdbMails installs it quietly in the background. Nothing else on your system is touched.

Source Office 365 Tenant

EdbMails has to be registered as an application in Microsoft Entra ID (formerly Azure Active Directory) on the source tenant. If that sounds like extra work, it isn't. The source connection wizard walks you through it automatically, and there is nothing to configure in Entra ID by hand.

Target Office 365 Tenant

The same app registration is needed on the target tenant. Just like the source, the target connection wizard handles it for you automatically.

Target Exchange Server

When migrating to an on-premises Exchange server, the admin account used for the connection needs the ApplicationImpersonation role assigned. This gives EdbMails the access it needs to create and write to mailboxes on the target. Without it, the migration will not have sufficient permissions to complete successfully.