Migrating a Live Logistics Platform from Azure to Google Cloud

Zero Rollbacks | All Tenants Migrated in One Cutover | 37× Faster Database Query | 38% Lower Storage Usage

Executive Overview

Logibee needed to migrate its live, multi-tenant logistics SaaS platform from Microsoft Azure to Google Cloud without disrupting daily operations. The migration covered applications, databases, virtual machines, media storage, and deployment pipelines, with all tenants and white-label brands required to move together.

Transcloud managed the migration, established the new Google Cloud environment, and coordinated the production cutover while maintaining data consistency. All tenants moved in a single cutover with zero rollbacks. Following migration, database optimization improved critical database queries, while storage cleanup reduced usage by 38%.

The Challenge

The client’s platform supported essential logistics operations, including order management, driver tracking, route optimization, and proof of delivery. Migrating the platform required careful coordination to maintain service continuity and preserve customer data.

The main challenges included:

• Maintaining service continuity: Migrating a live platform without disrupting daily logistics operations.
• Coordinating all tenants: Moving customers and white-label brands together while preserving their domains and routing configurations.
• Preserving application data: Migrating databases and media files without disrupting existing application functionality.
• Ensuring a reliable cutover: Keeping production data synchronized and validating critical workflows before switching platforms.
• Improving performance and security: Addressing database performance issues and strengthening access controls in the new environment.

What Transcloud Delivered

Google Cloud Foundations

Transcloud assessed the existing Azure environment, identified migration requirements, and established separate Google Cloud environments for staging, production, and shared services. The team configured network access and security controls to support the migrated workloads.

Application and Data Migration

Transcloud moved application workloads to Cloud Run, migrated PostgreSQL databases to Cloud SQL, and transferred media files to Google Cloud Storage. The existing application file structure was preserved, avoiding application-code changes for file access.

Database synchronization continued during preparation, allowing the team to validate the new environment while the Azure platform remained operational.

Production Cutover

Transcloud created a structured cutover plan covering final data synchronization, application validation, and the transition of supporting services. The team also moved deployment pipelines to Google Cloud Build, connected to GitLab.

All tenants and white-label brands transitioned in one coordinated cutover. Azure remained available as a fallback during the post-migration safety period, and no rollback was required.

Improved Security and Storage Efficiency

Transcloud removed obsolete files before completing the migration, reducing unnecessary data transfer and lowering storage usage. The team also strengthened security by centralizing application secrets, restricting database access, and protecting administrative interfaces.

Optimized Database Performance

Transcloud investigated the inefficient database queries and applied targeted optimizations.

The changes reduced execution time of a business critical queries to sub-second latency and one of the query’s performance is improved approximately 37 times faster.

Outcomes

• Zero Rollbacks: Completed the migration without reverting to Azure, which remained available as a fallback during the transition.
• Single Cutover Across All Tenants: Moved all tenants and white-label brands together while preserving critical platform functionality.
• 37× Faster Database Query: Reduced a critical database query from 6.5 seconds to 175 milliseconds through targeted optimization.
• 38% Lower Storage Usage: Removed obsolete files, reducing the storage footprint and unnecessary data transfer.
• Reliable Data Transition: Maintained database synchronization and validated critical workflows before switching the production platform.
• Improved Security: Strengthened secret management, database access restrictions, and administrative access controls in the new environment.
• Modernized Deployment Process: Moved deployment pipelines to Google Cloud Build, establishing a deployment workflow aligned with the new platform.

Technology Stack

Google Cloud: Cloud Run, Cloud SQL, Cloud Storage, Compute Engine, Cloud Build, Secret Manager, Identity-Aware Proxy, and Database Migration Service.

Source environment: Microsoft Azure, including Azure Container Apps, Azure Database for PostgreSQL, Azure File Share, and Azure DevOps.

Why Transcloud

Transcloud managed the migration from infrastructure assessment through production cutover and performance optimization. By coordinating application and database migration, validating critical workflows, and improving the migrated platform, the team helped Logibee transition its live logistics operations to Google Cloud without a rollback.

The result was a successful platform migration accompanied by measurable database performance improvements, lower storage usage, and stronger operational controls.