Single service comparison

Storage class boundaries differ. GCS bundles four tiers (Standard, Nearline, Coldline, Archive) under one service with per-object lifecycle transitions and retrieval SLAs expressed per class. Huawei OBS exposes Standard, Infrequent Access (30-day minimum), and Archive (90-day minimum) on the public OBS service, with Archive requiring an explicit restore before read and expedited restore taking 1-5 minutes. GCS Coldline/Archive are immediately readable (with retrieval fees) while OBS Archive is not directly readable until restored, so lifecycle and access-pattern modeling must change rather than be mapped one-to-one.

Access control and API surface differ. GCS uses IAM plus bucket/object ACLs with uniform-bucket-level access and signed URLs over JSON or XML APIs compatible with S3-style tooling. Huawei OBS uses account/bucket/object IAM, bucket policies, ACLs, and OBS-signed URLs with its own API plus an S3-compatible endpoint on dedicated gateways; SDK coverage and feature naming differ. Dedicated OBS (DOS) is a separate, dedicated-deployment variant for tenants needing isolated capacity or compliance, not a drop-in replacement for shared OBS, and is not offered in all regions.

Durability, replication, and operating responsibility differ. GCS provides 11 nines durability with dual-region high availability and transparent multi-region placement, while OBS achieves 11 nines single-AZ or 12 nines multi-AZ durability with region and AZ selection made by the operator at bucket creation time. Cross-region replication in OBS is configured via OBS Replication, whereas GCS uses object versioning plus dual/multi-region or CRR. Network egress and inter-region traffic are billed analogously but on different price lists, so TCO must be recomputed with request volume, retrieval frequency, and cross-region patterns.

Assess first and choose the right target. Inventory bucket counts, object sizes, class distribution, retrieval frequency, lifecycle rules, retention/holds, encryption keys, and signed-URL or public-read usage. Default to shared OBS for most workloads; reserve Dedicated OBS (DOS) only where contractually required isolation or dedicated capacity is needed, and confirm DOS regional availability. Map GCS Standard to OBS Standard, Nearline to Infrequent Access, and Coldline/Archive to OBS Archive, noting OBS Archive's restore-before-read model and minimum durations (30/90 days).

Migrate data with an appropriate Huawei tool. For cloud-to-cloud object moves use Object Storage Migration Service (OMS), which is designed to migrate data from other clouds into OBS; for one-off bulk transfers use obsutil, OBS Browser+, or CDM batch jobs, and for very large offline datasets use DES (disk or Teleport) or Direct Connect. Recreate bucket structure, object metadata, tagging, lifecycle rules, and KMS encryption settings manually since these do not translate automatically. Re-issue IAM to Huawei IAM, replace signed-URL code with OBS signing, and update applications pointing at JSON/XML endpoints.

Validate integrity and access before cutover. Verify object counts, sizes, ETag/checksums, and metadata between source and target using obsutil or a custom parallel verifier; test restore of Archive objects and measure restore latency; confirm lifecycle rules trigger as expected and that replication or versioning behavior matches requirements. Re-run permission checks for IAM users, bucket policies, and public-read configurations, and validate VPC endpoint and CDN integration paths end to end before switching DNS or application configuration.

Mind the gaps and cost-model shift. GCS charges storage GB-month plus class-specific retrieval and operations, while OBS charges storage, requests, retrieval/replication, and data transfer with separate DES/Direct Connect transfer costs; recompute TCO with peak request rate, retrieval frequency, and inter-region traffic. Watch for features without direct parity, such as GSC object holds and retention policies versus OBS WORM (OBS Object Lock where available), CMEK handling differences, and S3-compatible endpoint availability by region, and plan phased cutovers rather than assuming feature equivalence.