26 days until IMGIS 2026 in Palm Springs Schedule time with us
Integration · At cutover

Migrate the network. Keep every integration.

Outage management, customer systems, work management and field tools all speak to your GIS the way the Geometric Network taught them. Nutility stands up proxies in front of the Utility Network that answer in that same signature — so cutover breaks nothing downstream, and each integration moves to the Utility Network when you choose, not when the migration forces it.

Talk to us about integration → Need the migration first? →
How the proxies work

The Utility Network behind. The Geometric Network in front.

Each proxy takes the requests your integrations already make — feature queries, traces, edits — and serves them from the Utility Network in the shape they expect. The integration never learns the network changed.

Signature preserved
Endpoints, field names and trace semantics stay as the Geometric Network exposed them, so the calling system needs no change and no re-test on migration day.
No big-bang cutover
Every integration keeps running through go-live. The migration’s risk stops at the network; it never reaches the systems that depend on it.
Retire on your schedule
Move each integration to native Utility Network services when its own roadmap allows, then switch its proxy off. Nothing forces the order.
Every integration accounted for
We inventory what talks to your GIS before cutover, cover each with a proxy, and track the switch-off — so nothing is discovered broken after the fact.
How the engagement works

Scoped to your integrations, not to a clock.

Starts with an inventory

We catalogue every system that reads or writes your GIS and what each one asks of it. That inventory is the scope, and it is yours to keep.

Fixed price per integration

Each proxy is priced on what it has to preserve, agreed before cutover — no open-ended time-and-materials.

Engineer-governed changes

Every agent runs inside a scoped, monitored workflow — permissioned actions, engineer sign-off on changes, and a full activity trail. We never train on your data.

Your proxies, your pace

The proxies run in your environment and switch off one at a time as integrations move. Keep them for years, or retire the last one the week after go-live.

Common questions

Which integrations can be proxied?
Anything that talks to the Geometric Network through its published services — outage and distribution management, customer and billing systems, work and asset management, mobile and field tools, reporting. During the inventory we confirm each one and say plainly where a proxy is not the right answer.
Does a proxy slow the integration down?
The proxy is a translation, not a second database. Requests are served from the Utility Network directly, in the shape the integration expects, and we measure each one against its current behavior before cutover.
Can we keep the proxies indefinitely?
Yes. Some integrations will never justify a rewrite, and a proxy is a perfectly good permanent home for them. Others you will move when their own roadmap allows. The order and the timing are yours.
Do we have to take the migration with it?
No. If another team is doing the migration, we can still inventory your integrations and stand up the proxies against the network they deliver. Each engagement stands on its own.

Cut over without cutting anything off.

See what a proxied cutover looks like for the systems that depend on your GIS.

Talk to us about integration →