Public information system modernization

You first need to map shared objects, real workflows, decision screens, and the redundancies that cost the most. You do not start with the oldest technology, but with the area where overlapping tools create the most errors, delays, or opacity.

You need to document roles, workflows, business rules, reference data, interfaces, technical dependencies, access profiles, and takeover conditions in operations. Without that base, the migration may move forward, but it remains hard to steer and even harder to hand over.

You need a clear decision on where each data point is authoritative, which flows remain temporary, and which screens progressively become unnecessary. Coexistence works when it is run as an explicit transition phase, not when it settles in by default until it recreates two competing systems.

Because they determine identities, cases, permissions, inter-application exchanges, and reporting quality. If several components do not use the same definition of a citizen, an agent, an establishment, or a status, any modernization remains superficial until that foundation is clarified.

The choice depends on three things: how readable the existing stack still is, the cost of keeping its debt, and the risk of service disruption. An overlay can make sense to restore coherence quickly, but it must not become a way to postpone a foundation that has become too opaque to maintain.

You need to distinguish the data to take over as is, the data to requalify, and the data that is better left archived outside the live workflow. A successful migration does not blindly copy the past: it chooses what must keep creating operational value and what only needs to stay consultable.

You need to plan export modalities, data structure, interface documentation, environment visibility, access rights, and third-party dependencies. Reversibility is only credible if another team can take over the foundation without relying on tacit knowledge or hidden tools.

Those topics must be carried from the first choices around journeys, components, roles, logging, and documentation. In public-sector work, accessibility, security, and auditability are not separate finishing touches: they are design constraints that shape service quality and takeover readiness.

A trajectory remains steerable when the active scope is clear, dependencies are known, trade-offs are documented, and service continuity is measured step by step. As soon as the roadmap fills up with fuzzy migrations that lack decision rules and risk visibility, the effort becomes hard to control again.