Cross-forest and cross-domain migration
EdbMails handles cross-forest and cross-domain Exchange migration by moving mailboxes between Active Directory forests and domains directly. Doing this the Microsoft way means PowerShell cmdlets, prepared move requests, two-way trust relationships, and a flowchart of dependencies that breaks if any one piece is off. EdbMails skips the trust setup entirely. Connect to the source forest, connect to the target, and run it. Going from Exchange 2010 in one forest to Exchange 2019 in another? One job, no staging server, no intermediate version. Mail, calendar items, contacts, and folder permissions arrive on the other side the way they left.
Directly migrate from legacy servers to Exchange 2019 or 2016
EdbMails migrates directly from older Exchange servers, such as Exchange 2007 or 2010, to the latest builds like 2016 or 2019. The complicated intermediate-version dance the native path forces on you simply isn’t required. Mailbox content — messages, contacts, calendar items — moves over without loss. The migration runs in fewer steps, downtime stays short, and people keep working through the upgrade instead of waiting for it to finish.
Migration from hosted Exchange to on-premises Exchange
EdbMails migrates mailboxes from hosted Exchange environments, including Intermedia, Rackspace, and GoDaddy, as well as Exchange 2010, 2013, 2016, and 2019, straight onto Exchange Server 2019 or 2016. The tool was put together specifically for teams pulling email back from a hosted provider onto their own Exchange. Admins keep full control of the migration — how it’s scoped, when it runs, what happens when something throws an error — and any issues that come up are dealt with inside the same workflow rather than punted to a different tool.
Incremental data transfer without creating duplicates
After the first run, EdbMails incremental data transfer only moves what changed. New messages since last time, replies that came in overnight, items somebody dragged into a different folder — those go across. Anything that was already migrated stays where it is. Bandwidth use drops, the second run finishes in a fraction of the time the first one took, and you can keep running incrementals as often as you need to without worrying about ending up with two copies of the same email in the target mailbox.
Migrate from Exchange to any IMAP enabled server
EdbMails gives you a clean path for migrating emails from an Exchange environment to any IMAP-enabled server, whether the destination is Google Workspace, Zimbra, IBM Notes, Zarafa, or Kerio Connect. The traditional way to move email between Exchange and IMAP gets messy fast — the EdbMails wizard handles the heavy lifting so you don’t. Group mailboxes into batches, point at the source, point at the target, and let it run. What you end up with is a well-organized transition into whatever IMAP platform you’re landing on.
Universal language support
If your users email in more than English, universal language compatibility for Exchange migration is doing real work behind the scenes. Cyrillic, Chinese, Arabic, Japanese, Hebrew, Thai — all of it goes across with Unicode intact. Subject lines stay readable. Inbox and Sent Items folder names in non-English locales don't turn into question marks on the target. Diacritics on European names survive the trip. Language-specific metadata is read and written correctly, which matters when audit logs and retention policies are tied to that metadata. So a Tokyo user, a Berlin user, and a São Paulo user all see their mailbox the way they left it.
Select your preferred target folders
You decide where data lands on the target. EdbMails lets you select your preferred target folders so source content goes exactly where it should in the new Exchange environment — not wherever the tool decides. Want everything to stay in the same structure it had on the source server? Done. Need to route specific folders to consolidated locations on the target? Also done. The user-defined mailbox and folder mapping is flexible enough to fit compliance rules, organizational structure, or whatever else dictates how your data has to be filed.
Exchange migration with zero downtime
EdbMails runs Exchange migration with zero downtime, so people don’t lose access to email while the move is happening. The migration runs in the background — users keep sending and receiving as if nothing is going on, because from their side, nothing is. There’s no service window to schedule, no maintenance email to send out, and no business hours to dodge. The transition to the new Exchange environment finishes without anyone in operations having to clear their calendar around it.
Unlimited Public folder migration
EdbMails moves an unlimited number of public folders directly between Exchange Servers. The whole folder structure carries over to the target — permissions, subfolders, and mail-enabled folders all come across the way they were configured. Migrating Exchange public folders feels the same as migrating user mailboxes; the steps line up. Single-hop migrations between forests are supported, and so are double-hop scenarios like Exchange 2010 to Exchange 2019, with no PowerShell scripting needed. Incremental updates work too, so subsequent runs only pick up what's changed.
Automatically create mailboxes on target server
EdbMails automatically creates mailboxes on target Exchange servers, so you don’t have to set them up by hand. Whether it’s a handful of accounts or a few hundred, mailbox provisioning happens inline as part of the migration workflow rather than as a separate prep job. Configure mailbox settings once, run individually or in bulk, and let the tool take it from there. The migration moves faster, the kind of small typos that slow these projects down stop happening, and every account is wired up correctly by the time data starts flowing.
Ensure accuracy with automatic mailbox mapping
EdbMails automates mailbox mapping so source and target accounts line up the way they should. The match logic compares first and last names — or display names if those are what’s available — on both servers and pairs them automatically. It works in batches for bulk migrations, and the matching algorithm catches edge cases that catch out a manual pass. On a 500-mailbox migration, this is the difference between the project finishing on schedule and somebody spending half a day fixing mismatches.
Detailed Exchange migration reports for insightful analysis
EdbMails automatically generates detailed Exchange migration reports at the end of every job, so you have something to actually point to when somebody asks how the migration went. The reports break down per job, per mailbox, or across all configured tasks, with item counts at the mailbox and folder level and a record of whatever filters were applied. Progress sits at three layers — mailbox, folder, item — so if anything didn’t move, you find it fast. Useful during the run, more useful once it’s over.
Exchange to IMAP with CardDav and CalDav Migration
IMAP only handles email — contacts and calendars sit outside what the protocol covers — so EdbMails leans on CardDAV and CalDAV to move that data across when you migrate from Exchange to IMAP servers.Contact records go across with phone numbers, email addresses, job titles, and notes intact. Calendar appointments come over with their date, time, attendees, and reminders set the way they were. Recurring meetings stay recurring instead of collapsing into a single entry. For an individual user or a whole team switching to an IMAP platform, the address book and calendar show up on the new side ready to use, not as a stripped-down version of what was on Exchange.
Support for CSV File Based Mailbox and Folder mapping
Mapping mailboxes one at a time gets old fast on bigger migrations. EdbMails supports CSV file-based mailbox and folder mapping, where you define each source mailbox path — folders and subfolders included — and point it at the right target mailbox in a spreadsheet. Anything that doesn’t exist on the target gets created on the fly. This pays off when source and target folders are in different languages, or when you need source folders ending up in customized locations on the target. You decide where everything lands.