SERIES2 OF 3 PUBLISHED

ArcPy to Cloud Migration

A practical guide to migrating from desktop GIS to cloud-native pipelines. When it makes sense, when it doesn't, and how to execute without burning the team out.

3 parts

48 min total

AVAILABLE14 min

The Business Case for Migration

Why now, what's the real ROI, and when staying on ArcPy actually makes more sense. An honest cost-benefit analysis.

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

AVAILABLE18 min

The Migration Playbook

The step-by-step playbook for migrating ArcPy workflows to open-source. Assessment, pilot, scale - with real timelines and decision gates.

→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 Get Workflow Assessment

RELATED SERIES

SERIESParts 1-2 Available

AI Agents for Geospatial Automation

How AI agents actually automate legacy GIS workflows. Not chatbots. Agents that do the work.

SERIES3 parts

Geospatial on Databricks

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