HISTORICAL SERIES2 OF 3 PUBLISHED

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. Migration Engine is In development.

3 parts

48 min total

AVAILABLE14 min

The Business Case for Migration

Why a migration decision needs a current cost model, and when staying on ArcPy may still make sense.

→True cost of desktop GIS
→ROI calculation framework
→When NOT to migrate

AVAILABLE18 min

The Migration Playbook

A step-by-step migration method for ArcPy workflows, with inventory, pilot, validation, and stop decisions.

→4-phase migration framework
→Decision gates at each phase
→When to pause or stop

COMING SOON16 min

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

BEGIN THE SERIES

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.

Read Part 1 Discuss a workflow

RELATED SERIES

SERIESParts 1-2 Available

Spatial agent systems

Research notes on evaluating AI-assisted geospatial workflows, validation, and limits.

SERIES3 parts

Geospatial on Databricks

Practical guide for teams running geospatial on Databricks. Volumes traps, Jobs API patterns, and critical mistakes to avoid.