WordPress to Google Cloud Migration

Google Cloud Platform (GCP) brings unique advantages to WordPress hosting — access to Google's global fibre network, integration with BigQuery for analytics, Cloud CDN for low-latency content delivery, and the simplicity of Cloud Run for serverless WordPress. For businesses that rely on Google Workspace, analytics, or machine learning, hosting WordPress on GCP provides a unified ecosystem and consistent operational practices. At SoniNow, we manage the full migration lifecycle — from a detailed assessment of your current WordPress environment to a fully optimised, secure deployment on Google Cloud.

Assessment and Planning

Understanding your current WordPress installation in depth is the foundation of every migration we undertake.

Comprehensive Audit

We audit your existing hosting environment to capture: the web server (Apache, Nginx, or IIS), PHP version and extensions, database system and version (MySQL 5.7, 8.0, or MariaDB), total database size and largest tables, file storage consumption (wp-content/uploads, plugins, themes, languages), active plugins with version information and known security advisories, and any performance bottlenecks (slow plugins, excessive HTTP requests, unoptimised images). We also measure your current resource utilisation — peak CPU, memory, disk I/O, and bandwidth — so we can right-size your GCP infrastructure from day one.

Goal Setting

Before migration begins, we establish clear success criteria. For example:

• Page load time under 1.5 seconds (vs. current baseline)
• 99.9% uptime SLA for the Compute Engine or Cloud Run instance
• Ability to handle 5× current peak traffic without degradation
• Monthly hosting cost reduction of at least 30%

Architecture Selection

Based on the audit and goals, we select the optimal GCP deployment model:

• Compute Engine VM — Full control over OS, web server, and PHP configuration. Best for complex, customised WordPress sites.
• Cloud Run — Serverless containerised WordPress. Scales to zero when idle (cost savings) and handles traffic spikes instantly. Best for variable-traffic sites.
• Google Kubernetes Engine (GKE) — Container orchestration at scale. Best for multi-site or WooCommerce deployments requiring horizontal scaling.

Migration Process

Database Transfer

We export the WordPress database using mysqldump with optimal flags and compress it with gzip. The file is transferred over an encrypted tunnel to Cloud SQL for MySQL or Cloud SQL for PostgreSQL. Cloud SQL provides automated backups, point-in-time recovery, high availability with regional replicas, and a 99.95% SLA. For databases exceeding 5 GB, we use Database Migration Service (DMS) for continuous replication, enabling a cutover measured in seconds.

Media Migration to Cloud Storage

All WordPress media files are migrated to Cloud Storage using gsutil rsync to perform efficient, incremental syncs. We configure a Cloud Storage bucket with:

• Fine-grained access control (not public by default)
• Object versioning enabled
• Lifecycle rules to archive old media versions to Nearline or Coldline
• A Cloud CDN origin for global edge distribution

The Media from Google Cloud Storage plugin or a custom wp-config.php constant (UPLOADS) is configured to route uploads directly to the bucket, and we implement signed URLs or IAM-based access for private content.

Application Deployment

For compute-based deployments, we provision a Compute Engine VM from the WordPress-optimised Marketplace image or build a custom image with a LEMP stack (Nginx, PHP-FPM, MariaDB or MySQL). Cloud-init scripts automate configuration. For serverless deployments, we build a Docker image of WordPress with the necessary plugins, push it to Artifact Registry, and deploy to Cloud Run with memory and concurrency settings tuned for PHP.

DNS and Migration Cutover

After the staging environment passes every validation test, we switch DNS. GCP's Cloud DNS provides low-latency, globally anycasted DNS resolution. We use Cloud Load Balancing (global external HTTP(S) load balancer) as the single front-end endpoint, providing SSL termination, health checks, and traffic distribution across backends.

Performance Optimisation

Content Delivery with Cloud CDN

Cloud CDN leverages Google's global edge cache to serve WordPress static assets and, optionally, full cached pages from 100+ edge locations worldwide. Combined with Cloud Storage for media and Compute Engine origin, this reduces TTFB to under 100 ms for most global users.

Caching Strategy

• Page cache — Nginx FastCGI Cache or a WordPress caching plugin fronted by Cloud CDN for anonymous traffic
• Object cache — Memorystore for Redis for database query caching, reducing load on Cloud SQL
• Fragment cache — Transients and widget output cached in Redis for dynamic content

Database Optimisation

Cloud SQL is tuned for WordPress with optimised buffer pool sizes, query caching, and automated index recommendations. For high-traffic e-commerce sites, we enable Cloud SQL read replicas and ProxySQL connection pooling. Cloud Monitoring dashboards track query performance and identify slow queries.

Security Hardening

GCP-Native Security

Cloud Armor with built-in WAF rules protects against OWASP Top 10 threats, SQL injection, XSS, and DDoS attacks. VPC Service Controls prevent data exfiltration from Cloud Storage and Cloud SQL. Cloud IAM enforces least-privilege access — the WordPress VM gets a service account with minimal permissions, and human access requires IAM roles with conditions.

WordPress Security

In addition to GCP security, we harden WordPress itself: disable XML-RPC (unless needed), restrict REST API access where appropriate, enforce HTTPS with automatic redirect, configure Content Security Policy (CSP) headers, limit login attempts, and enable audit logging for admin actions.

Backup and DR

Cloud SQL backups are automated with 7–30 day retention. Compute Engine VM images are captured weekly using snapshot schedules. For critical sites, we configure Cloud Storage transfer to copy backups to a secondary region, ensuring data survives a regional outage.

Cost Optimisation

GCP pricing with sustained-use discounts (automatic 20–50% for running a VM for a full month) and committed-use discounts (up to 57% for 1-year commitments) makes WordPress hosting cost-effective. A typical Compute Engine VM with Cloud SQL and Cloud CDN costs $30–$80/month for a medium-traffic site. Cloud Run deployments can be even more cost-effective since you pay only for request processing time.

Migrating your WordPress site to Google Cloud with SoniNow means faster page loads, simpler operations, and the full power of Google's infrastructure behind your content.