BigRock to Office 365 Email Migration

Move BigRock-hosted email to Microsoft 365 while keeping the domain or website hosting with BigRock if required. The correct IMAP endpoint depends on the BigRock email product, so identify the source service before migration. BigRock currently documents different secure IMAP endpoints for cPanel Hosting, Plesk Hosting, Business Email, and Titan Email; all use secure IMAP port 993, but the server name differs by service.

The EdbMails IMAP Migration Tool supports bulk CSV loading, mailbox mapping, selective migration, concurrent processing, incremental follow-up runs, and reports. Standard IMAP migrates supported email/mail folders rather than contacts, calendars, tasks, websites, databases, or hosting configuration. Use this provider-specific page together with the main IMAP to Office 365 migration guide.

1. BigRock to Office 365 Migration Considerations

   1. Identify the BigRock email service

      cPanel Hosting, Plesk Hosting, Business Email, and Titan Email use different IMAP server names.

   2. IMAP scope

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

   3. Source and target limits

      Mailbox size, connection limits, bandwidth, Microsoft 365 throttling, and message-size policies affect throughput.

   4. DNS cutover

      Change production MX/DNS only after the Microsoft 365 target is verified.

   5. Verification

      Use migration reports and target-side checks before decommissioning the source service.

2. Reasons for BigRock to Office 365 Migration

   While BigRock provides useful features like Global Address Book, IMAP sync, distribution lists, and SSL certificate support, it still falls short of Office 365’s dedicated and fully integrated email environment for below key reasons.

   1. Although BigRock offers features like Global Address Book, IMAP sync, distribution lists, and SSL support, it lacks the fully integrated, collaborative, and feature-rich email environment provided by Office 365.
   2. Office 365 has a much collaborative and dedicated email service with Public folder, Archive and Shared Mailbox facility making it ideal for teams and organizations.
   3. It also includes access to SharePoint, OneDrive, Yammer, and other productivity apps all integrated under a single Microsoft 365 license.
   4. Office 365 comes with 50GB mailbox storage as opposed to BigRock’s Advanced and Business plans.
   5. Office 365 also includes desktop versions of Word, Excel, and Outlook, allowing users to work seamlessly across devices and access their tools from virtually anywhere.

3. BigRock to Office 365 Migration Planning

   • Identify whether the source is BigRock cPanel Hosting, Plesk Hosting, Business Email, Titan Email, or another BigRock-provided mail service.
   • Inventory mailboxes, mailbox sizes, folders, aliases, and active users.
   • Confirm the correct secure IMAP server name for the source service and use port 993 with SSL/TLS.
   • Create/provision Microsoft 365 target mailboxes and assign licenses.
   • Add and verify the custom domain if it will continue to be used for email.
   • Run a pilot mailbox and verify the target before production migration.
   • Use incremental follow-up passes where required and change MX/DNS only after target validation.

4. Pre-migration Activities for BigRock to Office 365 Migration

   BigRock source

   • cPanel Hosting: IMAP server mail.yourdomainname, secure port 993.
   • Plesk Hosting: use the domain/server name shown by the hosting account, secure port 993.
   • Business Email: us2.imap.mailhostbox.com, secure port 993.
   • Titan Email: imap.titan.email, secure port 993.
   • Use the mailbox credentials required by the source service and test a small CSV batch before loading all users.

   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 connection and run a pilot before production migration.

5. Steps to Migrate from BigRock to Office 365

   • Step 1: Download and Install EdbMails software

     • Start the migration process by downloading and installing the EdbMails application on your Windows computer.

       

     • Open the EdbMails application on your system.
     • Enter your registered email address and password, then click ‘Login’. If you are accessing EdbMails for the first time, choose ‘Start Your Free Trial’ to proceed 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’.

       

     • By default, a job name is assigned automatically. If you'd like to make it easier to identify, click ‘New Job’ and choose a custom name.

       

   • Step 2: Connect to the source BigRock server

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

       

     • Identify the BigRock email product first, then use its documented secure IMAP endpoint: cPanel Hosting uses the account's mail.yourdomain-style host; Business Email uses us2.imap.mailhostbox.com; Titan uses imap.titan.email. Use secure IMAP port 993 and SSL/TLS.
     • Click the ‘Login’ button.

       

     • To connect multiple Bigrock mailboxes, select ‘Multiple (Bulk) Users/Accounts Migration’, choose ‘Connect to IMAP Server’, and click ‘Next’.
     • Then proceed by clicking ‘Next’.

       

     • 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 BigRock server mailboxes

     • Choose the specific mailboxes or individual folders you wish to migrate. Once your selection is complete, click ‘Next’ to continue.

       

   • Step 4: Connect to the target Office 365 server

     • Select the ‘Add New Connection’ option to establish a connection with your target Office 365 account.
     • If you have previously set up a connection, you can choose it from the available list and click ‘Connect to Existing’ to proceed.

       

     • Select the preferred connection settings and click ‘Next’ to continue with the migration process.

       

     • Choose any of the available options to create a secure connection through OAuth 2.0 modern authentication.
     • Select Auto Registration for a quick and hassle-free configuration. Simply log in with a Global Admin account and approve the required permissions to automatically register the application in Azure AD.
     • Or select Manual Registration if you want to provide the Azure AD application details manually. This option supports both Global Admin accounts and accounts with Full Access permissions.
     • Click the ‘Login’ button to continue.

       

     • Authenticate on Microsoft sign-in page.

       

     • Once authentication is completed successfully, select any one of the following methods to load the mailboxes:

       Load Mailboxes Automatically: Use the automatic option to retrieve available target mailboxes through the current EdbMails Microsoft 365 connection. If every required mailbox is not returned, use the supported CSV-loading option and verify the destination mailbox list before continuing.

       ii) Load Mailboxes using CSV file: If the automatic method does not retrieve all mailbox names, choose the ‘Load Mailboxes using .CSV file’ option to manually select and load the required mailboxes.

       iii) Load Mailboxes from previous list: You can directly access mailboxes from the list that was imported and saved during your previous session.

     • Select ‘Load Mailboxes Automatically’ and click ‘Next’ to proceed.

       

   • Step 5: BigRock to Office 365 mailboxes mapping

     • Choose one of the available options to map the source and target mailboxes

       

     • 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 Bigrock to Office 365 migration

     • Verify the mailbox mapping, then click the ‘Start Migration’ button to begin the migration process.

       

     • Click the ‘View Logs’ button to access the full migration report. The report provides detailed information, including the mailbox mapping, an overall summary of the migration, and the item count for each mailbox and folder that was migrated.

       

6. BigRock to Office 365 Post-migration Tasks

   • Verify the target

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

   • Update mail DNS when ready

     Change the required MX/DNS records only after target validation. BigRock domain registration or website hosting can remain unchanged.

   • Validate Outlook/client access

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

   • Retain the source during validation

     Keep the BigRock mailboxes available for the agreed transition period before decommissioning them.

7. Troubleshooting Guide for BigRock 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.

---

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