Get hands-on experience with 20+ free Google Cloud products and $300 in free credit for new customers.

Migrating from GCP (BQ) to another GCP

Hi everyone!
I'm looking for any info about switching connected BigQuery in GA4 to another BigQuery (in another GCP)
I got some specific things in the project, and not sure that everything will be fine.
So, the thing is that to current BQ connected not only data from GA4, but Firebase too.
As I understand (for now):

  • I need to change BQ in GA4 to a new one, and Firebase settings will switch automatically

Or also I need to do the same thing in Firebase?
In this case will I broke / loose something or not? May be some of you already faced the same issue and know how to do it more correctly.
Will be appreciated for any info, thx

Solved Solved
0 4 367
1 ACCEPTED SOLUTION

Hello,

Thank you for contacting the Google Cloud Community.

When you switch the connected BigQuery in GA4, the data flow from GA4 to the new BigQuery will be redirected. However, the connection between Firebase and BigQuery is a separate configuration.

  1. Disconnect GA4 from the Old BigQuery
  2. Connect GA4 to the New BigQuery
  3. Verify Firebase Connection

Regards,
Jai Ade

View solution in original post

4 REPLIES 4

Hello,

Thank you for contacting the Google Cloud Community.

When you switch the connected BigQuery in GA4, the data flow from GA4 to the new BigQuery will be redirected. However, the connection between Firebase and BigQuery is a separate configuration.

  1. Disconnect GA4 from the Old BigQuery
  2. Connect GA4 to the New BigQuery
  3. Verify Firebase Connection

Regards,
Jai Ade

Thx a lot, Jai!

Hello,

Thank you for your engagement regarding this issue. We haven’t heard back from you regarding this issue for sometime now. Hence, I'm going to close this issue which will no longer be monitored. However, if you have any new issues, Please don’t hesitate to create a new issue. We will be happy to assist you on the same.

Regards,
Jai Ade

Hi @Konstantine switching the connected BigQuery dataset in GA4 to another BigQuery project is definitely possible, but it requires careful planning to avoid any disruptions—especially if Firebase is also part of your setup. Here are some key points to keep in mind:

1. Updating the BigQuery Link in GA4

To connect GA4 to a new BigQuery project:

  • Go to Admin > BigQuery Linking in your GA4 account.
  • Remove the existing connection and set up a new one with the BigQuery project you want to use.
  • Note that this change will only affect new data; historical data will remain in the original BigQuery dataset.

2. Firebase Integration Considerations

Firebase’s BigQuery linking is independent of GA4, so if your Firebase project is connected to the same BigQuery dataset:

  • Open your Firebase console and update the BigQuery link under Project Settings > Integrations > BigQuery Export.
  • If you don’t update this, Firebase will continue sending its data to the old dataset.

3. What Happens to Historical Data?

Switching projects won’t move your historical data to the new dataset. To address this:

  • Export the historical data from the old dataset if you need it in the new one.
  • Alternatively, you can run queries across multiple projects to combine historical and new data when needed.

4. Testing and Transition Plan

Before making the switch, it’s a good idea to:

  • Test the new connection using a different GA4 property, if possible, to make sure everything works as expected.
  • Take note of any configurations in GA4 or Firebase that might be affected.

5. An Alternative for Unified Data Management

If you’re dealing with multiple platforms like GA4 and Firebase, you might consider a tool like Windsor.ai. It can centralize your data from BigQuery, Firebase, and other sources, making it easier to manage without worrying about separate integrations. This can also act as a backup plan in case the transition gets tricky.

Final Tips

Once you’ve made the switch, double-check that both GA4 and Firebase are exporting data to the new dataset correctly. If historical data is important, make sure you have a solid plan to either migrate or query across datasets.

Hope this helps!