Migrate from Cloudflare R2 to Google Cloud Storage
Complete guide to migrating your data from Cloudflare R2 to Google Cloud Storage using Cloney.
Overview
Migrating from Cloudflare R2 to Google Cloud Storage (GCS) enables integration with GCP's powerful analytics, machine learning, and data processing services. This guide provides a comprehensive walkthrough of the migration process using Cloney.
GCS offers seamless integration with BigQuery, Cloud Functions, Vertex AI, and other GCP services for advanced data analytics and processing.
Prerequisites
- A Cloney account with an active subscription
- Cloudflare R2 bucket with data to migrate
- Google Cloud Storage bucket created (destination)
- Appropriate credentials for both services
Setup Access Credentials
Before proceeding, ensure you have configured least privilege access for both services:
Cloudflare R2: Least Privilege AccessGoogle Cloud: Least Privilege Access SetupStep 1: Add Your Cloudflare R2 Source
- Log in to your Cloney dashboard
- Navigate to Jobs → Create New Job
- Select Cloudflare R2 as your source provider
- Enter your R2 credentials:
- Account ID: Your Cloudflare account ID
- Access Key ID: Your R2 API token access key
- Secret Access Key: Your R2 API token secret key
- Bucket Name: The name of your source R2 bucket
- Click Validate Connection to verify access
Step 2: Configure Your GCS Destination
- Select Google Cloud Storage as your destination provider
- Upload your GCP service account JSON key file or enter credentials manually:
- Project ID: Your GCP project identifier
- Service Account Email: The service account email address
- Private Key: The service account private key
- Bucket Name: The name of your destination GCS bucket
- Click Validate Connection to verify access
Step 3: Configure Migration Options
Customize your migration with these options:
| Option | Description | Recommendation |
|---|---|---|
| Prefix/Path Filter | Migrate only objects matching a specific prefix | Use for partial migrations |
| Preserve Metadata | Copy object metadata along with data | Enable for full fidelity |
| Storage Class | Set the GCS storage class for migrated objects | Standard for frequent access |
| Overwrite Existing | Replace objects that already exist in destination | Enable for sync operations |
Step 4: Start the Migration
- Review your migration configuration
- Click Start Migration
- Monitor progress in the Jobs dashboard
- Cloney will provide real-time updates on transfer progress
Once finished, verify your data in the GCS console and update your applications.
GCS Storage Class Options
Choose the appropriate GCS storage class based on your access patterns:
| Access Pattern | GCS Class | Use Case |
|---|---|---|
| Frequent access | Standard | Hot data, frequently accessed |
| Monthly access | Nearline | Backups, data accessed monthly |
| Quarterly access | Coldline | Disaster recovery, quarterly access |
| Yearly access | Archive | Long-term archival, compliance |
Best Practices
- Enable Object Versioning: Turn on versioning in GCS for data protection.
- Use Autoclass: Let GCS automatically manage storage classes based on access patterns.
- Integrate with BigQuery: Use BigQuery external tables to query data directly in GCS.
- Set Up Cloud Functions: Trigger serverless functions on object uploads for processing.
Ready to Start Your Migration?
Create your Cloney account and begin migrating your data securely today.