ArcPy to Cloud Migration
Retained historical material on migrating from desktop GIS to cloud-native pipelines. It covers decision models, alternatives, and validation without treating old costs or timings as current evidence.
Evidence status: this series preserves search context and planning methods. Current scope, cost, ownership, delivery, and validation must be established for each workflow. Workflow migration is scoped as Applied Work with the organisation that owns it.
Choosing Your Platform
Databricks vs AWS vs Azure vs GCP for geospatial. Decision criteria based on your existing infrastructure, team skills, and workload patterns.
- →Platform comparison matrix
- →Migration path by starting point
- →Cost modelling by scale
Start with Part 1:
The Business Case
Before diving into technical migration, understand the real costs and benefits. Sometimes staying on ArcPy is the right answer. This post helps you figure out which situation you're in.