Question 1

How to migrate to Microsoft 365 using EdbMails?

Accepted Answer

EdbMails provides a straightforward method for Microsoft 365 migration. The process involves five simple steps:

Download and install the EdbMails software.
Connect to your source server using a Global Admin account.
Select the specific mailboxes and folders you wish to migrate.
Connect to the target Microsoft 365 server and map the mailboxes.
Start the migration.

For a step-by-step walkthrough, see our detailed Office 365 migration guide.

Question 2

What are the reasons for migrating to Office 365?

Accepted Answer

Organizations migrate to Microsoft 365 for several key benefits:

Cost Savings: Eliminates the need for on-premise hardware and maintenance.
Scalability: Easily scale services up or down based on business needs.
Accessibility: Users can access emails, documents, and apps from anywhere.
Collaboration: Tools like Teams, SharePoint, and OneDrive enhance teamwork.
Security: Built-in features like threat protection and data loss prevention.
Maintenance: Microsoft handles all updates and patches, freeing up IT resources.
Compliance: Helps meet regulatory requirements like HIPAA and GDPR.

Question 3

What are the types of Microsoft 365 migration supported by EdbMails?

Accepted Answer

EdbMails supports several Microsoft 365 migration types. You can perform a cutover migration to move all mailboxes at once, a staged migration to move mailboxes in batches, or a hybrid migration to integrate on-premise Exchange with Office 365. We also support IMAP migration from platforms like Gmail.

Question 4

Do you have Office 365 Migration checklists?

Accepted Answer

Yes, we provide a comprehensive Office 365 migration checklist to guide you through the entire process. It covers pre-migration planning, execution steps, and post-migration tasks to ensure a smooth transition. You can view the full Office 365 migration checklist here.

Question 5

What are the best practices for Office 365 email migration?

Accepted Answer

For a successful migration, we recommend planning thoroughly, preparing the source and target environments, communicating with users, and performing a pilot migration first. For a detailed list, please see our guide on Office 365 migration best practices.

Question 6

What are the migration challenges with Microsoft 365?

Accepted Answer

Common challenges include potential data loss, extended downtime, user disruption, and complexities with large mailboxes or public folders. Using a dedicated migration tool can help mitigate these risks. Learn more about the common challenges of Office 365 migration.

Question 7

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

Accepted Answer

Yes, EdbMails supports migration from Office 365 to on-premise Exchange servers, including Exchange 2019, 2016, 2013, and 2010. You can find the steps to migrate from Office 365 to an on-premise Exchange server in our guide.

Question 8

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

Accepted Answer

Migrating Public folders with EdbMails is a script-free process:

Start EdbMails and select the Office 365 migration option.
Choose 'Connect to Public folder' as the migration source.
Connect to the source Office 365 server and select the Public folders.
Connect to the target Office 365 server and start the migration.

For more details, see our guide on Public folder migration to Office 365.

Question 9

Does EdbMails support migrating Shared mailboxes to Office 365?

Accepted Answer

Yes, EdbMails fully supports migrating shared mailboxes to Office 365. The software automatically maps shared mailboxes and migrates all content, including emails, contacts, and calendars, with full integrity.

Question 10

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

Accepted Answer

Yes, EdbMails allows you to directly migrate an Office 365 public folder to a shared mailbox.

Question 11

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

Accepted Answer

To migrate a large archive mailbox, first enable In-Place Archive in your target Office 365 tenant. Then, use EdbMails to connect to the source and target servers, select the archive mailbox, and start the migration. EdbMails handles large mailboxes efficiently, ensuring no data loss.

Question 12

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

Accepted Answer

You will need an Office 365 Migration license to migrate mailboxes from an Office 365 source. Each mailbox you migrate will consume one license.

Question 13

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

Accepted Answer

Yes. After the initial full migration, EdbMails uses incremental migration for subsequent runs. This feature ensures that only new or modified items are migrated, preventing any duplicates on the target server.

Question 14

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

Accepted Answer

Yes, we offer a Free Trial version that allows you to test all migration features. The trial lets you migrate up to 30 items from each folder per mailbox, so you can verify the process before purchasing. You can download the Free Trial here.

Question 15

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

Accepted Answer

Yes, EdbMails provides advanced filtering options. You can include or exclude items based on criteria like date range, sender/recipient address, subject, and attachment name. This allows for highly selective and customized migrations. Learn more about applying filters for Office 365 migration.

Question 16

How does the licensing work?

Accepted Answer

EdbMails uses a per-mailbox licensing model. One license is required for each source mailbox you migrate. Once purchased, you can use these licenses across multiple migration jobs until they are all utilized. You can check your license status within the software. For more details, see our FAQ on licensing.

Question 17

How many licenses should I purchase for Public folder migration?

Accepted Answer

Migrating public folders from a single domain requires a 20-mailbox license pack. This allows you to migrate an unlimited number of public folders from that source domain.

Question 18

Do I need to pay for Shared mailbox migration?

Accepted Answer

Yes, migrating a shared mailbox requires a license, just like a standard user mailbox.

Question 19

Is there any size limitation for Microsoft 365 mailbox migration?

Accepted Answer

EdbMails does not impose any size limitations for migration. However, your migration will be subject to the size restrictions and throttling policies of the target Microsoft 365 environment. You can read more in our Knowledge Base article.

Question 20

Does EdbMails automatically create mailboxes on the target Office 365 server?

Accepted Answer

Yes, EdbMails has a feature to automatically create mailboxes and assign licenses on the target Office 365 server, which simplifies the setup process.

Question 21

Can I map one source folder to the desired folder on the target server?

Accepted Answer

Yes, EdbMails includes a folder mapping option that allows you to manually map a source folder to any specific folder on the target server.

Question 22

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

Accepted Answer

Migration time depends on several factors, including the number and size of mailboxes, network bandwidth, and Microsoft's server throttling. You can find more information on estimating Office 365 migration duration here.

Question 23

Does the software support all languages during migration?

Accepted Answer

Yes, EdbMails is designed to handle non-English character sets and supports all languages during migration, ensuring that content is migrated with full fidelity.

Question 24

Can I access the source and target mailbox during migration?

Accepted Answer

Yes, EdbMails performs the migration in the background without locking the mailboxes. This allows users to continue accessing their source and target mailboxes with zero downtime during the process.

Question 25

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

Accepted Answer

Yes. EdbMails has an option to 'Remove deleted source items from target folders'. When you enable this and run a subsequent migration, it will synchronize the target by removing any items that were deleted from the source since the last migration. See our mailbox migration options for more details.

Question 26

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

Accepted Answer

Yes, EdbMails supports migrating Office 365 mailboxes to any IMAP-enabled server, such as Gmail, Zoho, or cPanel. You can find the steps to migrate from Office 365 to IMAP here.

Question 27

Does EdbMails support Office 365 to Hosted Exchange migration?

Accepted Answer

Yes, EdbMails can migrate from Office 365 to a Hosted Exchange server environment, such as those provided by GoDaddy or Rackspace.

Question 28

Do I need a separate license for Primary mailbox and Archive mailbox migration?

Accepted Answer

No, you do not need a separate license. As long as the primary mailbox and its corresponding archive mailbox share the same User Principal Name (UPN), a single license will cover the migration of both.

Question 29

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

Accepted Answer

Yes, EdbMails provides an automatic mailbox mapping feature. It matches mailboxes between the source and target tenants based on their email addresses, which saves significant time and reduces errors in large-scale migrations.

Question 30

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

Accepted Answer

No. EdbMails uses an incremental migration process. After the first migration, any subsequent migrations to the same target will only copy new or changed items, preventing duplicate data from being created.

Batch migration support

Concurrent migration for faster results

Automated migration workflow

Scalable and flexible for various migration needs

Incremental migration support

Customization and control

Additional resources: