Question 1

What is Office 365 migration?

Accepted Answer

Office 365 migration is the process of moving organizational data — mailboxes, public folders, archives, SharePoint, OneDrive, and Teams — into Microsoft 365, out to another platform, or between two tenants. EdbMails Office 365 Migration Software supports all of these scenarios.

Question 2

How can I migrate to Office 365 using EdbMails?

Accepted Answer

The whole Office 365 migration process using the EdbMails Office 365 Migration Tool is one of the simplest there is – just connect to your source and target servers and let it do its work. Step 1: Download and install EdbMails. Step 2: Connect to the source using a global administrator account. Step 3: Choose which mailboxes and folders to migrate. Step 4: Connect to the destination server and map the mailboxes. Step 5: Begin the Office 365 migration process.

Question 3

What are the reasons for migrating to Office 365?

Accepted Answer

Most teams move to Office 365 for some combination of these: Cost savings: Less spent on on-premise hardware, fewer painful upgrade cycles, and ongoing maintenance becomes someone else's problem. Scalability: Size your environment up or down as the business shifts. Accessibility: Mailboxes, documents, and apps reachable from anywhere, on whatever device the user happens to have. Collaboration: SharePoint, Teams, OneDrive, and Yammer working together for actual teamwork instead of email tag. Security: Built-in threat protection, data loss prevention, and encryption — without needing to bolt on third-party tools. Maintenance: Microsoft handles updates and patches, which frees IT staff for work that actually moves the business. Compliance: Features that help with HIPAA, GDPR, and the rest of the alphabet soup.

Question 4

What types of Microsoft 365 migration does EdbMails support?

Accepted Answer

EdbMails covers all the standard Office 365 mailbox migration types. Cutover migration moves every source mailbox into the Office 365 tenant in a single pass — straightforward when the org is small enough to switch over at once. Staged migration breaks the work into phases, useful when you'd rather not move everyone at the same time. Hybrid migration ties on-premise Exchange and Office 365 together for organizations running both. IMAP migration is also on the menu — Gmail to Office 365 being one of the more common examples.

Question 5

What are the best practices for Office 365 email migration?

Accepted Answer

The best practices guide for Office 365 mailbox migration covers all the key steps and recommendations to ensure a smooth and successful migration.

Question 6

What are the migration challenges with Microsoft 365?

Accepted Answer

There are several common challenges with Office 365 mailbox migration including data integrity, downtime, user access continuity, and large mailbox handling. Detailed breakdown of these challenges is available in EdbMails' migration challenges guide.

Question 7

Can I use EdbMails to migrate Microsoft 365 to On-Premise Exchange server?

Accepted Answer

Yes. EdbMails moves Office 365 mailbox data back to on-premise Exchange, with all server versions supported — Exchange 2010, 2013, 2016, and 2019. Step-by-step guidance for migrating from Office 365 to on-premise Exchange is available separately.

Question 8

What are the steps to migrate Office 365 Public folder with EdbMails?

Accepted Answer

Public folder migration is straightforward with EdbMails — and there's no PowerShell scripting involved at any point. Step 1: Launch EdbMails and choose Office 365 migration. Step 2: Pick 'Connect to Public folder' as the migration operation. Step 3: Connect to the source Office 365 server and select the public folders. Step 4: Connect to the target Office 365 server and start the migration.

Question 9

Can I migrate a Microsoft 365 Public folder to Shared mailbox with EdbMails?

Accepted Answer

Yes - Office 365 public folder to shared mailbox migration is one of the supported scenarios.

Question 10

How to migrate a large Archive mailbox to Office 365 with EdbMails?

Accepted Answer

For migrating a large archive mailbox to Office 365: Step 1: Enable In-Place Archive in your Office 365 tenant. Step 2: Download and install EdbMails. Step 3: Connect to the source Office 365 server. Step 4: Pick the large archive mailbox you want to move. Step 5: Connect to the target Office 365 server. Step 6: Start the migration. Every piece of mailbox data — emails, contacts, calendars, tasks, attachments — comes across with full accuracy. No data loss, no corruption, nothing scrambled.

Question 11

Which license do I need to buy to migrate Office 365 Mailboxes?

Accepted Answer

You'll need an Office 365 Migration license to move your mailboxes from Office 365.

Question 12

Can I migrate only new emails using EdbMails without duplicates on the target server?

Accepted Answer

Yes. By default, the first run is a full migration. From the second run onward, incremental migration kicks in automatically, picking up only new or modified items — no duplicates land on the target. You can also filter by last migration date if you'd rather skip rescanning the whole mailbox each time.

Question 13

Do I need to pay for Shared mailbox migration?

Accepted Answer

Yes — each shared mailbox uses up one license, same as a regular mailbox.

Question 14

Is there a Free Trial version available to test Microsoft 365 migration features?

Accepted Answer

Yes — there's a Free Trial that opens up every Office 365 migration feature for testing. Up to 30 items per folder from every mailbox come across during the trial.

Question 15

Is it possible to migrate specific data from source Office 365 to target Office 365?

Accepted Answer

Definitely. EdbMails handles selective Office 365 migration through filters that you can shape pretty granularly — message received date, sender address, recipients (CC and BCC included), subject line, attachment names, and read/unread status all work as filter criteria.

Question 16

How do I choose the best Office 365 migration software?

Accepted Answer

Compare migration tools across capabilities like license type, concurrent mailbox migration, automatic throttling management, incremental migration, public folder licensing, and technical support. Tools that offer lifetime licenses, free upgrades, and 24/7 support typically deliver better long-term value than subscription-based options.

Question 17

How does the licensing work?

Accepted Answer

The licensing model is per-mailbox: each migrated mailbox consumes one license, calculated against the source mailbox count. Nothing stops you from running multiple migration jobs in parallel across different machines, as long as you've got licenses left in the pool.

Question 18

Do you have Office 365 Migration checklists?

Accepted Answer

Yes - Office 365 migration checklists are available to help you plan and execute your migration successfully.

Question 19

How many licenses should I purchase for Public folder migration?

Accepted Answer

Public folder migration takes 20 mailbox licenses. Once those are allocated, you can migrate unlimited public folders from a domain — there's no per-folder cost beyond that.

Question 20

Does EdbMails support migrating Shared mailboxes to Office 365?

Accepted Answer

Yes — shared mailbox migration to Office 365 tenants is fully supported. The full set of source items is covered: mailboxes, shared mailboxes, public folders, archive mailboxes, and more. EdbMails handles the shared-mailbox mapping automatically and brings across the contents — emails, attachments, contacts, calendars, tasks, and notes.

Question 21

Is there any size limitation for Microsoft 365 mailbox migration?

Accepted Answer

There aren't any size limits on the EdbMails side. Microsoft does enforce its own restrictions, though — those are detailed in the EdbMails Knowledge Base article on Microsoft 365 mailbox size limitations.

Question 22

Does EdbMails create the mailboxes automatically on the target O365 server?

Accepted Answer

Yes, EdbMails will automatically create the mailboxes for you on the target and allocate the licenses to be assigned.

Question 23

Is it possible to map one source folder to the target folder of my choice on the server?

Accepted Answer

Yes, EdbMails allows customized folder mapping to route source folders to target folders of your choice.

Question 24

How much time does it usually require to migrate Office 365 mailboxes?

Accepted Answer

The duration of Office 365 migration depends on a few moving parts. Detailed breakdown of Office 365 migration duration is available in EdbMails' tenant-to-tenant migration guide.

Question 25

Does the software support all languages during migration?

Accepted Answer

Yes — EdbMails supports all languages during Office 365 migration.

Question 26

Can I access the source and target mailbox during migration?

Accepted Answer

Yes — your mailbox data stays accessible the whole time the migration is running. No server downtime to plan around.

Question 27

Can EdbMails remove deleted source items from the target Office 365 folders?

Accepted Answer

Yes — EdbMails can sync deletions from source to target. Tick the 'Remove deleted source items from target folders' option in the main migration window, then run a follow-up migration.

Question 28

Can I migrate emails from Microsoft 365 to IMAP server using EdbMails?

Accepted Answer

Yes — Office 365 emails can move to any IMAP-enabled server. The supported list covers most of the popular ones: Outlook, Gmail, Zoho, Zimbra, IceWarp, cPanel, Plesk, GoDaddy, Rackspace, AWS WorkMail, Bluehost, and Dreamhost.

Question 29

Does EdbMails support Office 365 to Hosted Exchange migration?

Accepted Answer

Yes — Office 365 to Hosted Exchange is supported. A common example is migrating from Office 365 to a Rackspace-hosted Exchange server.

Question 30

Will I require a different license for Primary mailbox migration and Archive mailbox migration?

Accepted Answer

No, you only need one license if both the UPN (User Principal Name) are identical for the Primary and Archive mailboxes.

Question 31

Does EdbMails manage mailbox mapping from source to target Microsoft 365 server automatically?

Accepted Answer

Yes, EdbMails automates the mailbox mapping between source and target tenants. For the case when there are hundreds or thousands of mailboxes to be migrated, manual mapping would be a terrible job and EdbMails saves a lot of time.

Question 32

Does the software generate duplicates when running consecutive Microsoft 365 migrations?

Accepted Answer

No — incremental migration handles this. Subsequent runs only carry across new and modified items, which keep the target server clean of duplicates.

Question 33

Does EdbMails handle mailbox mapping between source and target Microsoft 365 servers automatically?

Accepted Answer

EdbMails automates mailbox mapping between the source and target Tenants, which is useful for large-scale migrations, saving considerable time and effort compared to manual mapping.

Question 34

Does EdbMails need scripting via PowerShell for Office 365 migration?

Accepted Answer

No. EdbMails Office 365 migration is an all-graphical-user-interface experience without need of using any PowerShell scripts, or any command-line instruments, or making any API calls. This is regardless of whether it is about migrating mailboxes across tenants, public folders or mailbox archives, hybrid configuration.

Concurrent Mailbox Migration

Why Concurrent migration is crucial for modern organisations

Why Choose EdbMails for Office 365 Mailbox Migration?

EdbMails Demo / Trial Version