From Shapefile to Cloud: Migrating Your GIS Data the Right Way

Moving from local or legacy GIS data to the cloud doesn’t have to mean a full re-architecture. With a few format and workflow choices, you can keep using the same tools while gaining scalability and shareability.

Audit and prioritize

List what you have: shapefiles, GeoTIFFs, file geodatabases, PostGIS exports. Identify which layers are used in production or by key users. Migrate those first. One-off or archival data can follow. That way you get value quickly without boiling the ocean.

Choose cloud-friendly formats

Convert rasters to Cloud Optimized GeoTIFF (COG) so they can be streamed by extent. For large vector datasets, consider vector tiles for web and desktop clients; keep GeoJSON or GeoPackage for smaller layers and APIs. Standardizing on a few formats simplifies both storage and tooling.

Upload and organize

Upload to object storage (or a service built on it) with a clear structure: e.g. by project, theme, or resolution. Use consistent naming so URLs are predictable. If you’re using a platform like Sarkoa, follow its conventions for tiles and raw files so you get direct links and tile endpoints without extra config.

Update workflows

Point QGIS, ArcGIS, and web apps at the new URLs instead of local paths. Document the new locations and any credentials or CORS settings. Train users on “add layer from URL” or equivalent. With zero-egress or predictable pricing, you can encourage sharing and embedding without worrying about surprise bandwidth costs.