GCP Project Migration

Migrate GCP projects by provisioning APIs, moving data, and updating configurations.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ksrae/tag-diary-app --skill gcp-project-migration-ksrae
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: GCP Project Migration
Source: https://github.com/ksrae/tag-diary-app/tree/main/.agents/skills/gcp-migration
Command: npx skills add https://github.com/ksrae/tag-diary-app --skill gcp-project-migration-ksrae

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gcloud, docker, terraform, and includes scripts (resource) and references (resource) components.

What problem does it solve?

Migrating cloud resources, permissions, and configurations between GCP projects is error-prone and time-consuming; this skill provides a repeatable, script-driven process to move databases, storage, APIs, and infrastructure definitions with minimal downtime.

Core Features & Use Cases

  • Automates API enabling across the target project for required services.
  • Migrates Cloud SQL databases, GCS buckets, and container images.
  • Applies Terraform configuration and updates deployment secrets to align with the new project.

Quick Start

Execute the migration script with the required flags to begin the full GCP project migration.

Frequently Asked Questions about GCP Project Migration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate GCP projects between environments safely?

To migrate GCP projects safely, you can automate provisioning APIs, moving Cloud SQL and GCS data, and updating Terraform state in a single repeatable workflow. This validates inputs before execution to minimize downtime.

What is the best way to move Cloud SQL databases and GCS buckets to a new GCP project?

The best way to move Cloud SQL and GCS data is using an automated workflow that provisions required APIs and migrates resources alongside container images and Terraform configurations to align the new project.

Do I need gcloud CLI, Docker, and Terraform to migrate GCP project configurations?

Yes, you need gcloud CLI, Docker, and Terraform installed as prerequisites. The migration process enforces these dependencies to apply configurations and move infrastructure definitions successfully.

Can I automate API enabling and IAM updates when moving GCP projects?

Yes, you can automate API enabling across the target project and update related IAM and network settings. The workflow aligns deployment secrets and configurations with the new GCP project automatically.

How does Terraform state migration work when switching GCP projects?

Terraform state migration works by applying existing Terraform configurations to the new project and updating deployment secrets. This ensures infrastructure definitions match the target environment without manual errors.

What are the limitations of automating GCP project migration with scripts?

The limitations include strict dependencies on gcloud CLI, Docker, and Terraform. The script validates inputs before performing the migration, requiring proper environment setup to avoid execution failures.