Download Buy Now

Office 365 Public Folder to Exchange Migration

Office 365 Public folder to Exchange migration comes up when businesses are dealing with infrastructure upgrades, consolidation of email systems, or staying compliant with organizational policies. Organizations shift from Office 365 to on-premises or hosted Exchange environments when they want better data control, reduced costs, or to meet regulatory requirements. EdbMails Office 365 migration tool steps in here, giving IT teams a straightforward way to handle Public folder migration with these needs effectively. Folder data, mail items and permissions all move across to the target Exchange server — no PowerShell scripts, manual procedures. Key features include incremental migration, automatic mapping of source and target public folders, and detailed migration log reports — everything an IT administrator needs to move Public folders across to Exchange 2019, 2016, 2013, 2010, and Hosted Exchange servers.

The following sections cover migration planning, pre-migration requirements, and the steps to migrate Office 365 Public folders to a live Exchange server using EdbMails.

Office 365 Public folder to Exchange migration

Planning a Public Folder Migration to Exchange Server
Jumping straight into a Public folder migration from Exchange Online to an on-premises Exchange server without any prerequisites is where most teams run into trouble. A quick checklist of items to identify and prepare your environments.
1. Identify the size and number of Public folders you want to migrate
2. The Exchange server should be installed, and the target environment should be prepared before migration.
3. Public folders on the target server need to exist and be mail-enabled.
4. Determine whether you want to move everything at once or in stages.
5. Your internet speed and network setup can make or break a migration — check both.
6. Decide if you plan to move Public folders to Public folders, primary mailboxes, or Shared mailboxes.
7. Communicate the plan and the changes to your end users.
8. Always run a test migration first. Never go straight into the real thing.
9. Start the migration, verify the endpoint and add DNS records.
10. Create new Outlook profiles and check if you are receiving mails correctly.
Office 365 Public Folder to Exchange Migration: Pre-Migration Activities
- Step 1: Make sure the following are in place on the Office 365 side before you do anything else:
  1. Ensure that you have a global admin account that has an active mailbox — this is what the Manual registration method uses to connect to the source Office 365 server.
  2. The admin user also needs the right Public folder permissions assigned to their account. See the steps to assign the required permissions to the admin user
  3. Ensure the required network and bandwidth are available for the migration. See performance factors and best practices for Office 365 Public folder migration.
- Step 2: Check that your system meets the Exchange server setup requirements.
  The links below cover what you need to know about network, hardware, and operating system requirements for whichever Exchange version you're migrating to.
  Note: Exchange 2010 hit end of support on October 13, 2020 and Exchange 2013 followed on April 11, 2023. If you're still on either of these, moving your mail data and Public folders to Exchange 2016 or 2019 is strongly advisable at this point.
- Step 3: Prepare your target system before you start the Exchange server installation.
  Work through the prerequisites below for Active Directory, Windows Mailbox server, and Windows Edge Transport servers — these need to be sorted out before you actually install Exchange.
- Step 4: Setup Exchange Server for Migration
  Below are the key things to take care of when installing and getting the Exchange server ready for migration.
  1. Prepare AD and domains
    1. The Active Directory forest and its domains need to be prepped for the new Exchange version before anything gets installed.
    2. If a separate team looks after your Active Directory schema, you need to first extend the Active Directory schema — otherwise, jump straight to preparing Active Directory.
    3. Running multiple domains? You'll also need to go through preparing the Active Directory domains as an additional step.
  2. Install Exchange server on your computer
    Double-check that your system meets the requirements and prerequisites covered in the earlier steps. Once that's confirmed, use the setup wizard to install Exchange 2016 or install Exchange 2019, depending on your target version.
  3. Prepare a clean Exchange target environment
    - Set up and configure a Send connector so the Exchange organization can send mail outside its boundaries.
    - Exchange sets up receive connectors on its own when the mailbox server gets installed — but if your setup needs something specific, here's how to configure receive connectors manually.
    - Add accepted domains so recipients can send and receive email across different domains.
    - Set up the default email address policy to push the accepted domain out to every recipient in the organization.
    - Configure external URLs (domains) on the virtual directories in the Client Access (frontend) services on the Mailbox server to allow clients to connect to your server from the internet (outside the organization's network).
    - Configure internal URLs on the virtual directories in the Client Access (frontend) services on the Mailbox server to allow clients to connect to your server from the internal network.
    - Get your SSL certificates configured from a third-party certificate authority — this covers services like Outlook Anywhere and Exchange ActiveSync.
    - Once everything's in place, verify the Exchange server installation by running Get-ExchangeServer in the Exchange Management Shell (EMS).
  4. Create Public Folders on the Exchange Server
    Get the Public folders created on the target server first, then assign the admin permissions needed to manage them.
    Steps to create Public folder in Exchange server
  5. Assign Management Roles to the Admin Account
    If you're connecting to the Exchange server through a global admin account, impersonation rights need to be set up before things will work properly.
    See the steps to set impersonation rights on Exchange server
  6. Configure the Throttling and Message-Size Limits
    Before the migration runs, it's worth setting up custom throttling policies and maximum message size limits on the target Exchange server. The links below walk through both:
    - Custom EWS throttling settings on Exchange server
    - Change message size limits on Exchange
Steps to migrate Public folders from Office 365 to Exchange
1. Step 1: Download and install EdbMails software
  - Download EdbMails and install EdbMails application on a computer running Windows OS.
    Explore the full System requirements for EdbMails Office 365 migration.
  - Enter the appropriate details and click ‘Login’ or click ‘Start Your Free Trial’
2. Step 2: Select ‘Office 365 to Live Exchange migration’ operation
  - Select the 'Office 365 Migration' option.
  - Choose the 'Office 365 to Live Exchange Migration' option..
  - Keep the default job name or type your own, then click 'Next.'
3. Step 3: Connect to source Office 365 server
  - Click ‘Add New Connection’ to set up a new connection to the source Office 365 account. To use an existing connection, select it from the list and click ‘Connect to Existing’ to proceed.
  - Select ‘Connect to Public Folders’ and click ‘Next’ to continue.
  - Choose one of the methods for secure OAuth 2.0 authentication and click the ‘Login’ button to proceed.
  - Connect to Office 365 server using secure modern authentication
    Sign in on the Microsoft authentication page using a global admin account.
  - Once authentication is successful, select the method to load public folders.
    
    Tip: If this is the first time you’re migrating with EdbMails, the migration is a full migration. On subsequent migrations from the same source to the target, the migration is incremental.
4. Step 4: Select the Office 365 Public folders
  - Select the public folders you want to migrate from the source Office 365 server.
  - Then click ‘Next’ to proceed.
5. Step 5: Connect to target Exchange server
  - Click ‘Add New Connection’ to establish a new connection to the target Exchange server. To use an existing connection, select it from the list and click ‘Connect to Existing’ to proceed.
  - Choose the necessary connection options and click ‘Next.’
    Explore various methods to connect to the Exchange server in EdbMails.
  - Enter the Exchange server details and click the ‘Login’ button
  - Choose one of the methods to load public folders.
6. Step 6: Public folder mapping between source and target servers
  - EdbMails automatically maps public folders between the source and target servers. You can also manually map source folders to the required target folders and map the source and target folders using a CSV file.
7. Step 7: Start Public folder migration to Exchange server
  - Click the 'Start Migration’ button to initiate the migration process.
  - The migration process will now begin. Once it’s complete, you’ll be prompted to review the migration status. Click the ‘View Logs’ button to view the migration report. Then, log in to the target server to check the migrated items.
Office 365 Public Folder to Exchange Server Post Migration Tasks
- Step 1: Update the MX Records to Point to the Exchange Server
  To receive messages on Exchange, change the DNS records known as MX records to enable email to work with the new server you have migrated to. In addition, configure the Autodiscover record to allow Outlook to connect to the migrated mailboxes.
- Step 2: Create a New Outlook Profile for Users in the New Domain
  - Check that the latest Outlook version is on every machine to avoid compatibility issues.
  - Configure the Outlook profile for each user in your domain if Outlook has problems connecting to Office 365 mailboxes.
  - Configure the new server address, username and password in Outlook.
  - Test email flow to confirm that users can send and receive emails.
- Step 3: Remove the Old Office 365 Subscription Plan
  Data verified, migration done — now cancel the Office 365 subscription on the source and drop any domains tied to it that you no longer need.
Office 365 Public Folder to Exchange Migration Troubleshooting
- Running into errors mid-migration happens — check the Office 365 migration troubleshooting guide and the Public folder troubleshooting page for fixes to the most common issues. Got questions about how EdbMails handles Office 365 migration? The frequently asked questions page covers a lot of ground.
- If Public folders aren't migrating and permissions are the suspected cause, this one's worth a look — unable to migrate Public folders due to insufficient permissions.

Benefits of EdbMails for Office 365 to Exchange Public Folder Migration

Manually moving Public folders to a live Exchange server is tedious, error-prone, and frankly unnecessary. EdbMails handles it automatically — and the graphical interface shows the full Public folder hierarchy right there on screen. This allows you to migrate folders, subfolders and mail items — all of it moves across without touching a single PowerShell script.

EdbMails Office 365 migration software ensures secure migration is built in, with modern authentication and TLS encryption covering every transfer between Office 365 and Exchange.
The incremental migration feature in EdbMails ensures that only new and modified items, which were not included in previous migration runs, are migrated. This reduces overall migration time, saves bandwidth, and prevents the migration of duplicate items during subsequent migrations.
Whatever folder and subfolder structure exists on the Office 365 side lands exactly the same way on the target Exchange server.
EdbMails automates Public folder mapping between the source and target servers.
You can migrate Public folders of any size without any downtime or data loss while the business keeps running.
Facility for free trial to test the software's working and free 24x7 technical support and migration assistance.