Liquid Web to Office 365 Email Migration

Liquid Web supports several email environments, including control-panel-hosted email and Premium Business Email. Before migration, identify the source service because the IMAP server name can differ by platform.

For Liquid Web cPanel-hosted email, Liquid Web currently documents secure IMAP using the server hostname with port 993 over SSL/TLS. Legacy Cloud Sites or Rackspace Email environments can use secure.emailsrvr.com. Do not apply one hostname to every Liquid Web mailbox without first identifying the service.

The EdbMails IMAP Migration Tool migrates supported Liquid Web email data to Microsoft 365 with bulk CSV loading, mapping, filters, concurrent processing, incremental follow-up runs, and reports. Standard IMAP is email-focused; contacts, calendars, tasks, chat, hosting data, websites, and databases require separate handling.

Use the Liquid Web control panel or service documentation to confirm the actual source IMAP endpoint before migration. The Microsoft 365 target uses the current EdbMails OAuth-based connection workflow. For destination-wide planning and cutover, use the IMAP to Office 365 migration guide.

1. Liquid Web to Office 365 Migration Considerations

   1. Identify the source email service

      Liquid Web cPanel/Plesk email, Premium Business Email, and legacy Cloud Sites/Rackspace Email can use different server names and administration paths.

   2. IMAP scope

      Standard IMAP transfers supported email/mail folders; contacts, calendars, tasks, hosting configuration and website data require separate handling.

   3. Connection limits and bandwidth

      Source session limits, Microsoft 365 throttling, mailbox sizes, and network capacity affect throughput.

   4. DNS cutover

      Change production MX/DNS only after Microsoft 365 target validation.

   5. Verification

      Review reports and representative target data before retiring the old mail service.

2. Liquid Web to Office 365 Migration Planning

   1. Identify the Liquid Web source service and obtain its current IMAP server/hostname, secure port, encryption mode, and mailbox credentials.
   2. Inventory mailboxes, mailbox sizes, folders, aliases, and any contacts/calendar data that must be handled separately.
   3. Create/provision Microsoft 365 target users/mailboxes and assign licenses.
   4. Add and verify the custom domain if Microsoft 365 will become the production mail destination.
   5. Review source limits, Microsoft 365 throttling, message-size policies, and bandwidth.
   6. Run a pilot mailbox and verify the target before the production batch.
   7. Use incremental follow-up passes where required and change MX/DNS only after target validation.

3. Pre migration activities for Liquid Web to Office 365 Migration

   Liquid Web source

   • cPanel-hosted email: Liquid Web documents secure IMAP on port 993 using the server hostname shown by the hosting account.
   • Legacy Cloud Sites / Rackspace Email: Liquid Web documentation identifies secure.emailsrvr.com for that legacy/Rackspace-hosted service.
   • Premium Business Email: verify the current connection settings in the Premium Business Email control panel/documentation before entering a source hostname.
   • For bulk migration, prepare the EdbMails sample CSV and validate a small test set first.

   Microsoft 365 target

   • Create/provision target users/mailboxes and assign licenses.
   • Add and verify the custom domain if Microsoft 365 will receive production mail.
   • Use the current EdbMails OAuth-based Microsoft 365 target connection and run a pilot before production migration.

4. Steps to Migrate from Liquid Web to Office 365

   • Step 1: Download and Install EdbMails migration software

     • Download EdbMails and install the application on a supported Windows computer that can connect to the source and target environments.

       

     • Launch the EdbMails application on your computer.
     • Enter your registered email address and password, then click ‘Login’. If you’re using EdbMails for the first time, select ‘Start Your Free Trial’ to continue with the trial version.
        Note: The EdbMails IMAP trial lets you evaluate the workflow and migrate up to 30 items from each folder. To migrate all eligible items for licensed mailboxes, purchase the required IMAP migration license.

        View current IMAP migration pricing.

       

     • Select the option ‘IMAP (Gmail, Outlook & more) Migration’.

       

     • Select ‘IMAP to Office 365 Migration’.

       

     • Use the default job name or select ‘New Job’ to customize the name.

       

   • Step 2: Connect to source Liquid Web server

     • To connect a single Liquid Web mailbox, select ‘Single User / Account Migration’, choose ‘Connect to IMAP Server’, and click ‘Next’.

       

     • Enter the IMAP connection details for the actual Liquid Web email service. For cPanel-hosted email, use the server hostname shown by the control panel with secure IMAP port 993. For legacy Cloud Sites/Rackspace Email, secure.emailsrvr.com can apply. Verify the source service before connecting.
     • Click the ‘Login’ button.

       

     • To migrate multiple mailboxes from Liquid Web to Office 365, choose ‘Multiple (Bulk) Users/Accounts Migration’ and select the appropriate connection option, either ‘Connect to IMAP Server’ or ‘Connect to POP3 Server’.
     • Click ‘Next’ to continue.

       

     • Click ‘IMAP Migration CSV File’ and specify the location to save on your local drive.

       

     • Open the CSV file and fill in the necessary details, including the email address, password, IMAP server hostname, and port number for each mailbox. After completing the entries, save the CSV file and close.

       

     • Now, click the 'Load Modified CSV File' button, open the CSV file and click ‘Next’ to proceed

       

   • Step 3: Select source Liquid Web server mailboxes

     • Select the mailboxes or specific folders you want to migrate, then click ‘Next’ to proceed with the migration process.

       

   • Step 4: Connect to target Office 365 server

     • Click on ‘Add New Connection’ to create a connection with your target Office 365 account.
     • To use the previous connection, select it from the list and choose ‘Connect to Existing’ to continue.

       

     • Select the required connection options and click the ‘Next’ button.

       

     • Select the authentication method and click the ‘Login’ button to continue.
     • Choose your preferred method for secure OAuth-based authentication. The recommended ‘Auto Registration’ option simplifies setup and requires Global Admin rights to configure permissions automatically. For more control, you can opt for ‘Manual Registration’, which works with either a Global Admin or any user account that has full mailbox access. Once you've made your selection, click the ‘Login’ button to proceed.

       

     • Authenticate on Microsoft sign-in page.

       

     • Click the ‘Next’ button to continue.

       

   • Step 5: Liquid Web to Office 365 mailboxes mapping

     • Select the mapping option that best aligns with your requirements.

       

     • Where supported and selected, EdbMails can assist with target mailbox creation and automatic mapping. Verify Microsoft 365 licensing and review every source-to-target mailbox mapping before starting the production migration.

       

   • Step 6: Start Liquid Web to Office 365 migration

     • After mapping the mailboxes, click the ‘Start Migration’ button to initiate the migration process.

       

     • Click the ‘View Log’ button to view the migration report, which includes mapping details and the total count of migrated emails.

       

     • Login to your target server and verify the migrated items.

5. Liquid Web to Office 365 Post Migration Tasks

   • Verify the target

     Review migration reports and representative folders, messages, attachments, item counts, and user access in Microsoft 365.

   • Update MX/DNS when ready

     If Microsoft 365 becomes the production mail service, update the required DNS records only after target validation.

   • Validate Outlook/client access

     Confirm Microsoft 365 sign-in and Autodiscover behavior and recreate Outlook profiles only where required.

   • Handle non-IMAP data separately

     Complete any required contacts/calendar migration before retiring the Liquid Web email service.

   • Retain the source during validation

     Keep the source mailboxes available for the agreed transition period before canceling or decommissioning them.

6. Troubleshooting Guide for Liquid Web to Office 365 Migration

     For common migration issues, check the knowledge base articles. For more information on EdbMails IMAP migration, visit the frequently asked questions (FAQs) section or contact our technical support team.

 Learn more about EdbMails IMAP Migration Tool

---

Additional resources:

• IMAP to Office 365 migration
• EdbMails IMAP migration software
• IMAP migration filters and incremental settings
• IMAP to Office 365 screenshots
• IMAP migration FAQ