Skip to main content
  1. CloudM
  2. Migrate
  3. Errors & Troubleshooting
  4. Troubleshooting
  5. Performance

Google Workspace Rate Limiting: Proactive Prevention & Handling

Updated

During a migration to Google Workspace, you may encounter an error like "Rate Limit Exceeded" or other API quota-related messages. This indicates the migration is making more requests to a Google service (like Gmail or Drive) than is allowed within a specific timeframe. CloudM Migrate is designed to handle Google rate limiting that may occur during a migration.

This article explains the cause of these errors and provides actionable steps to help you manage Google's API quotas for a more efficient migration.

Understanding API Quotas

Google imposes API quotas to ensure service stability. These quotas limit the number of API calls an application, such as CloudM Migrate, can make to a Google service within a 24-hour period.

CloudM Migrate is designed to manage these limits automatically using exponential backoff, a process where the tool waits for progressively longer periods before retrying a failed request. However, with large data volumes or a high number of concurrent migrations, you may still exceed these quotas.

Resolving Quota Errors

To resolve these errors, you can adjust the migration speed within CloudM Migrate to stay within Google's API limits. Here are the recommended adjustments, which can be applied individually or in combination.

1. Reduce Concurrent User Migrations

Lowering the number of users migrated simultaneously is the most effective way to reduce API calls. This will increase the overall project duration but will significantly reduce the likelihood of hitting API limits.

  1. Open the CloudM Migrate Service Manager.

  2. Navigate to the Maximum User Migrations setting.

  3. Reduce the current number (e.g., from 20 to 10).

2. Reduce Drive Thread Count (for Google Drive)

If the errors are specific to Google Drive, reducing the number of threads used for Drive data can help.

  1. Go to Configuration > Advanced Settings.

  2. Navigate to the System section.

  3. Locate the Drive Thread Count setting and reduce the value. Lowering it from the default of 3 to 2 can make a substantial difference.

3. Implement an Item Export Delay

Introducing a small delay between items can also help manage the rate of API requests.

  1. Go to Configuration > Advanced Settings.

  2. Navigate to the System section.

  3. Find the Item Export Delay setting and enter a small value in milliseconds (e.g., 100 or 200).

Performance Tuning & Best Practices

To further optimize your migration performance on the Google platform, consider the following best practices:

  • Use GCP Servers: Hosting the CloudM Migrate application within Google Cloud Platform is highly recommended. Because the application resides within the same network as the Google Workspace tenant, this can significantly improve data transfer speeds by reducing latency and ensuring a high-throughput network connection.

  • Utilize Additional Service Accounts: By using multiple service accounts across different GCP projects, you can increase the overall API throughput. Each service account has its own API quotas, so distributing your workload across multiple accounts can help you avoid hitting a single project's daily limits.

Google Resources

API rate limiting is controlled entirely by Google and cannot be directly altered by the CloudM Migrate software. If you have adjusted the settings above and continue to experience persistent errors, we recommend contacting Google Support directly to discuss your options.

Related Information

Was this article helpful?
2 out of 4 found this helpful