BigQuery Export changes: Billing impact, action needed

In August, Google started consolidating Gmail log exports from BiqQuery into the same export used for all other Admin logs. see unified-experience-for-workspace-logs-in-bigquery

This change will require changes for customers that have set up GCP billing for their logs export project. Customers should turn off the separate Gmail log export to avoid double billing and additional costs. For those not previously exporting Gmail logs, understand that your Admin log export BigQuery project will begin billing higher now that Gmail logs are included. For those using Sandbox mode, note that your exports are stopping, and you will need to enable billing to continue exporting your logs.

DataStudio dashboards created for Gmail logs will need to be updated to point to the new data location. See Migrate Gmail logs in BigQuery to Workspace logs in BigQuery. This article explains the next steps to avoid double billing, how to consolidate old Gmail project exports prior to the change into the main export project, and other technical details.

If you require support in making these changes, please email for assistance in making these adjustments.

Example of email customer gets from Google:


To streamline BigQuery tasks, and to let you get all your BigQuery data in one place, we’re merging logs in BigQuery with Google Workspace logs in BigQuery.


Dear Administrator,

We are writing to let you know that we have merged the export of Gmail logs to BigQuery with other Google Workspace applications. Our records show that you have both Gmail and Google Workspace logs enabled for export to BigQuery.

If you have custom queries and views in your Gmail logs, transfer them to Google Workspace logs within six months after receiving this message so you don’t lose access to those custom queries and views.

What does this mean for my organization?

Merging Gmail logs with the rest of Google Workspace will provide the following benefits:

  • One place to store and manage BigQuery exports for all your Google Workspace services audit events.
  • More complete data about Gmail events in BigQuery
  • Partitioned data, so you can export smaller data sets and reduce BigQuery data storage costs.
  • Data recovery, so you can correct misconfigurations and permission changes.

It also means that six months after receiving this message, you will no longer be able to export Gmail logs to BigQuery from Gmail settings. Therefore, you will need to take the steps outlined below to ensure your custom queries and scripts run successfully.

What do I need to do?

To keep your Gmail BigQuery data available, migrate your views, queries, and scripts to Google Workspace logs and reports in BigQuery by performing the following steps:

  1. Backfill Gmail data to the new table (optional)
  2. Migrate Gmail BigQuery logs views, queries & scripts
  3. Turn off Gmail log exports to your Gmail-only BigQuery project

For additional information, refer to the full guide on migration of your Gmail Logs export projects into unified Google Workspace logs.

Note: Your Gmail data will be exported twice: to Gmail-only and to Google Workspace BigQuery projects. This dual write period will last until you turn off Gmail logs export to Gmail-only BigQuery project. Until then you will be charged according to On-demand analysis pricing.

We’re here to help

If you have questions, need assistance, or need to explore reimbursement opportunities and eligibility, please contact Google Workspace support. When you submit your support case, reference issue number {238969322}.

Thanks for choosing Google Workspace.

— The Google Workspace Team



Articles in this section