Legacy system replacement for geodata: When the switch pays off

Replacing a legacy system is first and foremost a matter of timing. When an aging geographic information system is replaced is a much bigger factor in the cost than simply establishing that it needs to be replaced, because a system hides its weaknesses in growing maintenance efforts before they manifest externally as outages, media disruptions, or failed data transfers. Those who actively choose the timing work with orderly data and a predictable budget; those who let it pass by end up migrating under pressure.

How to recognize a system ready for replacement

Readiness for replacement announces itself early. It rarely shows up as a single defect, but rather as multiple signals that appear together and make ongoing operation more expensive than an orderly migration ever would be:

• Manufacturer support has expired or is restricted. Security updates are missing, every adjustment becomes a special service, and dependence on a single provider grows with each year.
• The data model no longer meets current standards. ÖNORM, INSPIRE & OGC are increasingly prerequisites in tenders, and an inventory that does not support them can neither be exchanged cleanly nor audited.
• There are media disruptions between the field and the GIS. Data is typed in manually, sent by email, or maintained in intermediate tables, and every transfer creates errors that no one can trace back.
• There is no versioning. An overwritten state is lost, previous edits are not reconstructible, and the question of “what did that look like two years ago” remains unanswered.
• Knowledge is tied to individuals. Only a few know the peculiarities of the system, and with their departure, operational capability goes with them.

Why the timing determines the costs

The public sector plans in fiscal years, not in sprints. A call for tenders for the replacement of a core system requires lead time for requirements definition, procurement procedures, and transition operations, meaning that there are realistically several quarters between the decision and the productive new system during which the legacy system must continue to run. From our perspective, the replacement therefore does not begin with the migration, but with requirements management — months before the first data transfer, while the old system is still stable enough to be read out cleanly.

How a migration without data loss succeeds

A migration is only successful when nothing is lost and every step remains traceable. This is exactly where four principles come into play that support every data transfer at MovingLayers:

• Nothing is overwritten. Every state remains reconstructible, the depth of the history is contractually agreed upon, and a state once recorded is not lost during the migration.
• Validated before it counts. There is no path into the new inventory that bypasses validation; invalid legacy data is stored and marked rather than trickling in unnoticed.
• Readable even after a model change. The conversion from the old to the new data model is recorded as a versioned artifact and not just applied once and discarded, so that every assignment can be proven later.
• One state, no second path. After the replacement, all applications access the same validated inventory so that two systems cannot have different opinions about the same object.

What we take over during the replacement

MovingLayers supports the replacement throughout the entire cycle. We handle requirements management and migration, provide legally compliant support for tenders and procurement, and maintain the inventory thereafter in operation and data maintenance — existing tools are integrated, and we provide any that are missing. The solution runs on-premise or in an environment controlled by you, with local EU-AI, GDPR-compliant and with a view to the EU AI Act (as of September 2026), so that the replacement also meets the requirements of critical infrastructure (KRITIS) operators and authorities.

The procedures behind this have grown in project practice, not on the drawing board: MovingLayers has been working on geodata infrastructure since 2019, in projects with network operators and in FFG research projects.

Whether a switch is worthwhile for you now can be clarified in a free initial consultation. We will examine your inventory, your standards, and your procurement schedule and identify the point in time when a replacement costs the least.

Geodata from the field to decision – standardized, versioned & KRITIS-compliant.
Uniform layers & symbolization · Complete history · Locally operated & verifiable