GIS Data Review & Migration Scoping for a National Property Consultancy

Snapshot

In early 2025, we worked with a national property consultancy to scope the migration of dispersed geospatial data and workflows into a central, Postgres-backed GIS environment. The goal was a practical path to a single source of truth: less duplication, and consistent spatial working practices across multiple rural teams. The engagement produced an organisation-wide workflow map, a Master Data Register (MDR), migration recommendations, and concise good-data-practice guidance to anchor the technical design and change plan.

Challenge

Over time, different rural teams had evolved different ways of working. Some primarily in QGIS, some leaning on external web mapping services, others maintaining their own local copies of datasets. While many layers overlapped in purpose, storage locations and update routines did not. This created uncertainty about authoritative sources, re-work when outputs conflicted, and a growing backlog of technical debt.

A one-size-fits-all migration would not have worked here. The scoping needed to respect how teams actually operated while bringing them onto shared standards.

A particular complication was the mix of legacy desktop tooling and region-specific processes. Rather than forcing a big-bang switch, we sequenced recommendations to reduce delivery risk: document how work is done, set pragmatic design conventions, pilot the target approach in a contained slice, then scale.

Our approach

Discover and map workflows: We interviewed key users across rural teams to capture how spatial data is sourced, created, checked, and delivered. We visualised the hand-offs and decision points where GIS touches approvals, reporting, and client deliverables, so any proposed change could be traced to an operational benefit.

Compile the Master Data Register: We consolidated commonly used datasets, both internal and third-party, noting their sources, owners, refresh cycles, and whether an authoritative copy already exists centrally. The MDR became the spine of the migration backlog: what to migrate, what to reference live, and what to retire.

Assess central platform fitness: We evaluated how the existing central database and governance model could serve rural teams. Schema patterns by theme and region, geometry and CRS standards, when to use views or materialised views, and permissioning that is simple enough to administer while protecting sensitive layers.

Codify good data practice: We produced naming conventions, field design patterns, geometry validation checks, indexing recommendations, and lightweight metadata guidance covering provenance, cadence, and owner. This enables consistent project templates and predictable query performance.

Plan training and change: We proposed a champion model, a light skills matrix, and short refreshers focused on the central platform and standardised QGIS project setup. Designed to raise awareness of what is already curated centrally and reduce ad-hoc support demand.

What we delivered

• Organisation-wide workflow map for rural teams, showing data entry points, checks, and deliverables
• Master Data Register aligning datasets to those workflows, with clear flags for “migrate”, “consume live”, or “deprecate”
• Migration roadmap with sequenced waves starting from quick wins, plus schema proposals and standardised QGIS project templates that bind to authoritative tables and views
• Good-practice guide covering naming, CRS and geometry conventions, indexing, views and materialised views usage, and permissioning patterns
• Training and communications plan to embed the standards and drive adoption

Scoping outcomes

• Clarity on the single source of truth: Rural teams can now see which layers are authoritative, which remain external live services, and where local duplicates should be removed.
• Standardised project setup: Templates for QGIS reduce per-project configuration, prevent accidental use of stale local files, and point analysts at the right tables and views.
• Risk-managed migration path: The roadmap starts with well-bounded slices. High-value internal datasets first, before expanding to broader themes and regions.
• Immediate housekeeping wins: Duplicated layers and outdated copies identified that can be archived or replaced with centrally referenced sources, cutting noise and re-work.
• Targeted upskilling: A champion network and concise refreshers address common gaps around permissions, editing in a central database, and working with views. Building confidence and reducing support load.

The client now has a realistic, low-risk path to consolidate geospatial data and standardise rural workflows without disrupting day-to-day delivery. The plan balances central governance with local usability. Rural teams retain the flexibility they need, while the organisation gains a clear, auditable system of record.