Support Needed for Migrating Google reCAPTCHA Keys to Google Cloud Project

Hi ​@Eservicetracker - 

Could you please confirm if there are any changes in the billing model or pricing once the keys are migrated to Google Cloud?

Yes, there are changes. The migration shifts all customers to reCAPTCHA’s pricing model on Google Cloud. This includes a free tier of 10,000 assessments per month. For more information, see Billing Information.

What kind of production or service impact can be anticipated during or immediately after the migration process?

Is there any downtime expected or a recommended maintenance window for performing the migration?

There are no expected service interruptions. Your existing keys and API endpoints will continue to work, and no code changes are required immediately after migration.

Will the existing API endpoints, site keys, or secret keys continue to work post-migration, or do we need to update configurations on our applications?

Your existing site keys, secret keys, and the siteverify API endpoint will function as before. You do not need to update existing configurations immediately. Configuration updates are only required if you choose to adopt advanced reCAPTCHA features (which use a new JavaScript library and backend endpoint), see Use reCAPTCHA features after migration.

Are there any new permissions or IAM roles required on the associated Google Cloud project to manage reCAPTCHA?

Yes. If you are manually migrating to an existing GCP project you should have Project Owner, Project Editor, or reCAPTCHA Admin (roles/recaptchaenterprise.admin) IAM role on that project. If you are using our migration tool the GCP project that is created will automatically assign the appropriate role to the destination project.

Will there be any changes to logging or data retention policies once migrated?

Yes. Logging and analytics will move to the Google Cloud console, providing enhanced monitoring and reporting capabilities.

All reCAPTCHA customers are now also bound by Google Cloud’s Terms of Service and data retention policies. Also refer to our FAQ on Data Processing. 

Finally, could you please share any migration checklist or best practices documentation to ensure a seamless transition?

Please see the Migrate from reCAPTCHA Classic docs to see view all migration paths. If you do not self-migrate, your keys will be automatically migrated.

Please let me know if you have any more questions!

Emily

Hi emilymb,

Thank you for your support. We prefer to proceed with the automated process. Could you please let us know what impact this approach may have and any considerations we should be aware of?

Hi ​@Eservicetracker  –

In general, the migration will not impact your existing integration.

However, if you are using more than 10,000 assessments per month across all your keys, you will need to add a billing account to ensure continued protection. Without a billing account, requests over the limit will fail-open, which could leave your site unprotected (see Billing and enforcement).

Let me know if there is anything else you need!

Emily

Hi emilymb,

Thanks for your active response.  we prefer to migrate re-captcha keys automatically (  keys to automatically be associated with a Google Cloud project). Requesting you please mark us for your action to auto migration.