Ideas2IT Led the .NET Migration Behind a Retail Platform's Full Exit From Azure and AWS to GCP

Discovery and dependency mapping:

Phase I comprised four sequential workstreams: discovery, rehosting, dependency decoupling, and serverless migration. Phase I's mandate was safe relocation, which meant knowing exactly what existed before moving it. Two engineers spent three weeks assessing architecture, runtime versions, and hosting requirements across 70+ .NET applications and 275+ .NET projects across 7 repositories, including 250+ WebForms applications, Classic ASP projects, and a VB-based legacy project needing manual conversion.

The team scanned the codebase for every Azure and AWS service occurrence, mapped triggers and bindings for the 20+ Azure Functions and AWS Lambdas, and traced integrations, endpoints, and authentication flows end to end, closing the phase with complete visibility into migration complexity.

This Phase Produced

• Architecture and dependency assessment across 275+ .NET projects
• Azure and AWS service dependency inventory
• Trigger, binding, and runtime compatibility review
• Service occurrence mapping across the codebase
• Integration, endpoint, and authentication flow map
• Environment configuration inventory

Lift-and-shift rehosting: moving VM and AppServices workloads to GCP

VM to VM migration and AppServices migration both followed the same rule: rehost without a rebuild. The team provisioned GCP Compute Engine VMs with networking, security, and IIS prerequisites, then moved applications directly off Azure VMs and Azure AppServices onto that infrastructure.

Configurations, service URLs, connection strings, certificates, and secrets were updated in place rather than rewritten, keeping application logic untouched while the hosting layer changed underneath it. Smoke testing and performance validation closed each rehost before the next bucket started.

This Phase Produced

• GCP Compute Engine VM provisioning with networking, security, and IIS prerequisites
• Azure VM to GCP Compute Engine rehost
• Azure AppServices to GCP Compute Engine VM rehost
• Updated service URLs, connection strings, certificates, and secrets
• Smoke and performance test validation for each rehosted workload

Removing cloud lock-in: a wrapper layer standing between 30+ Azure/AWS services and GCP

The largest bucket in Phase I targeted the 30+ Azure and AWS services wired directly into the application layer. Rather than replace each integration in place, the team built an abstraction and wrapper layer that isolated cloud-specific logic from the applications calling it, then mapped every dependency to its GCP-native equivalent behind that interface.

Existing integrations were replaced service by service, infrastructure was stood up and deployed in GCP, and unit and regression tests confirmed each dependency was fully removed before the next one was tackled.

This Phase Produced

• Full inventory of 30+ Azure and AWS service dependencies
• Cloud-agnostic abstraction layer for storage, messaging, secrets, data, and monitoring
• GCP-native service implementations with shim adapters for phased cutover
• Replaced integrations across the application codebase
• GCP infrastructure provisioning for IAM, networking, and service accounts
• Unit and regression test suite confirming dependency removal

Serverless migration: realigning 20+ Azure Functions and AWS Lambdas to GCP Cloud Functions

Every serverless workload moved one function at a time, validated against its dependent services before the next one started. Triggers were realigned to their GCP equivalents: HTTP stayed HTTP, Timer became Cloud Scheduler with Pub/Sub, Blob and S3 storage triggers moved to Cloud Storage, Service Bus, SNS, and SQS consolidated into Pub/Sub, and Event Grid became Eventarc.

Cloud-specific SDK bindings were stripped out in favor of explicit GCP SDK calls and structured logging, IAM service accounts with Workload Identity replaced legacy credentials, and handlers were rebuilt idempotent and retry-safe to prevent cascading failures across the platform.

This Phase Produced

• Trigger realignment map (HTTP, Timer, Blob/S3, Service Bus/SNS/SQS, Event Grid to GCP equivalents)
• 20+ Azure Functions and AWS Lambdas migrated to GCP Cloud Functions
• IAM service accounts with Workload Identity
• Idempotent, retry-safe function handlers
• Minimum-instance configuration for latency-sensitive endpoints
• Unit, integration, and trigger-based test suite