Rackspace to Gmail Migration

During a Rackspace to Gmail migration, users may encounter a few technical challenges. Here’s how to overcome them effectively:

• Login Failures: Authentication errors can occur when source settings or credentials are incorrect.

  Solution: For Rackspace Email, use the current secure IMAP settings (secure.emailsrvr.com, port 993, SSL/TLS) and verify the full mailbox address and password before bulk loading.

• Rate Limits: Gmail imposes connection and sending limits that can slow down large migrations

  Solution: Schedule migrations in batches to avoid throttling and ensure smooth data transfer.

• Folder Mapping Issues: Inconsistent folder names or structures between Rackspace and Gmail can cause confusion.

  Solution: EdbMails uses automatic folder mapping to correctly align and organize folders during the migration.

• Email Duplicates: Re-running migrations may lead to duplicate messages.

  Solution: Enable delta migration to transfer only new or changed emails, preventing duplicates.

• Google Workspace integration: Gmail works with Google Drive, Docs, Sheets, Calendar, Meet, and other Google Workspace services.
• Centralized administration: Google Workspace provides organization-level user, security, and service administration for business accounts.
• Cloud-based access: Users can access Gmail through supported web, mobile, and email-client workflows.
• Spam and phishing protection: Gmail includes Google’s mail filtering and security controls, with additional capabilities available in Google Workspace plans.
• Custom-domain support: Organizations using Google Workspace can continue using a business domain after the required domain verification and DNS changes.

EdbMails supports Rackspace-to-Gmail migration through the IMAP-to-IMAP workflow, with mailbox selection, mapping, filters, concurrent processing, follow-up runs, and migration logs. Throughput depends on source and target limits, bandwidth, mailbox volume, and migration-computer resources.

Before you begin Rackspace to Gmail migration, thorough planning is essential for a controlled transition. To help you with the process, here is a checklist of important points to consider:

• Remove any unused mailboxes, redundant mail items, and duplicate files from the source server to streamline the migration.
• Before proceeding with the migration, create an inventory of important items. Here are some key items to include:
• User accounts, email addresses, and login credentials.
• Source and target server details, including information about browsers and operating systems used.
• Network settings, DNS configurations, MX records, and firewall settings.
• Outlook settings and version utilized within your organization.
• Licensing plans associated with your current source server.
• List of data and permissions from Rackspace that need to be transferred.
• Determine the size of the data and the number of mailboxes that will be migrated to Gmail.
• Decide whether to opt for a cutover migration (migrating all data at once) or a staged migration (migrating data in phases) based on your requirements.
• Estimate the approximate time required for the migration, taking into account factors such as data size and network capabilities.
• Create or prepare the target Gmail / Google Workspace accounts.
• Verify that your network has sufficient capacity and bandwidth to handle the migration process effectively.
• Communicate the migration plan and upcoming changes to your end users and stakeholders to ensure a smooth transition.
• Perform a test migration to identify and address any potential issues before initiating the actual migration.
• Start the migration process, ensuring endpoints are correctly configured and MX records are updated as necessary.
• Develop a plan for decommissioning any unused apps and their associated settings after the migration is complete.

• Ensure that IMAP settings are enabled on both the source (Rackspace) and target (Gmail / G Suite) servers to facilitate migration.
• Keep a record of the email addresses and passwords for all users you plan to migrate from the Rackspace server.
• Confirm that you have the email addresses for all users on Gmail. If using Gmail, create an app password for the account.

 Click here for steps to create an app password for a Gmail account.

• Step 1: Update DNS records (MX record) to point to Gmail
  • Updating MX Records:
    To redirect incoming email traffic to Gmail instead of Rackspace, you need to make changes to the MX records in your DNS provider's portal. This step ensures that emails are properly directed to your Gmail account.
  • Setting up Rackspace Mail Forwarding:
    To prevent any email loss during the migration process, it is essential to set up mail forwarding in your Rackspace account. This ensures that any incoming messages are forwarded to your Gmail account until the transition is complete. By enabling mail forwarding, you can stay connected and receive all your emails during the migration period
• Step 2: Decommission or delete the user mailboxes on Rackspace server

  Once you have confirmed that you are successfully receiving emails on Gmail, you can proceed with decommissioning and disabling user mailboxes on the Rackspace source. Additionally, make sure to remove any licenses that have been assigned in Rackspace. Follow these steps to perform the necessary actions:

  • Log in to the Rackspace Cloud Control Panel.
  • Navigate to the ‘Email’ section and click on ‘Mailboxes.’
  • Select the desired mailbox(es), whether it's a single mailbox or multiple ones.
  • Click on ‘Manage’ next to the respective mailbox and then click on ‘Delete Mailbox’ in the upper-right corner.

 For troubleshooting, visit Knowledge Base.

 For more queries, check Frequently Asked Questions or contact support.