Migration · The move to the Utility Network

The geometric network is retired. Your migration shouldn't take a year.

Nutility turns years of accumulated network data into a clean Utility Network. Senior engineers design the asset package around how your utility actually runs; an AI agent workforce does the heavy lifting — so you're live in weeks, for a price you can put in a budget.

Start with a readiness assessment → Estimate the cost ↓
The timeline

Live in four to six weeks, not twelve to eighteen months.

A manual migration drags on for quarters because people do the transformation by hand. We flip the ratio: engineers make the decisions up front, agents do the volume in parallel. Here's how a typical engagement runs.

  1. Week 0

    Readiness assessment

    We read your geometric network geodatabase and score it — schema, connectivity, data quality, crosswalk fit. You get a clear picture and a fixed not-to-exceed price before anything starts.

  2. Weeks 1–2

    Asset package design

    Senior engineers design your Utility Network asset package, domains, rules, and subnetworks around how your utility actually runs — not a generic template.

  3. Weeks 2–4

    Agent-run transformation

    Agents do 85%+ of the work — features, attributes, connectivity, and associations — transforming your estate onto the Utility Network at a pace no manual team can match.

  4. Weeks 4–5

    Validation & remediation

    Continuous validation against your model surfaces dirty areas and rule violations early. Agents remediate; engineers review every feature class.

  5. Weeks 5–6

    Engineer sign-off & go-live

    A senior engineer signs off on a connected, traceable network. We hand it over for you to run — or stay on for ongoing maintenance.

The approach

Engineer-led decisions. Agent-run volume.

The reason migrations fail or overrun is almost never the volume of data — it's the modeling decisions and the validation. We put senior engineers on the former and an AI workforce on the latter, with a human in the loop on every decision that matters. The agents move fast; the engineers stay accountable.

Get a readiness assessment →
Engineer-designed model
Senior GIS engineers design your asset package, rules, and subnetworks around your real network — the decisions that are expensive to get wrong are made by people who have done it before.
Agent-run migration
The AI agent workforce handles the heavy, repetitive transformation and validation in parallel — features, attributes, connectivity — compressing quarters of manual work into weeks.
Continuous validation
Connectivity and rules are checked continuously as the data moves, so issues surface in hours and never pile up into a go-live scramble.
Signed off, fixed price
Every feature class is validated and signed off by an engineer, for a fixed not-to-exceed price you know before you start. No open-ended time-and-materials.
The migration playbook

Every migration sharpens the playbook.

We keep a working field guide — the modeling patterns, the connectivity gotchas, the crosswalks that hold up under audit — and every engagement we run adds to it. It's the accumulated craft our engineers build from, so your migration starts on the far side of lessons other utilities paid to learn.

The Migration Handbook · our internal field guide, maintained by the engineering team

The Migration Handbook by Isaac King — front and back cover mockup
Cost calculator

What will a Utility Network migration cost us?

Five quick inputs, no login. You'll get a budgetary range you can take to your board. Tell us more and the range tightens — a short readiness assessment turns it into a fixed not-to-exceed number.

Which network are you migrating?

The questions and pricing levers differ by domain.

Budgetary range

$75K – $125K

Pick a network to start. Most standard migrations land in this band; complex systems and very large networks scope higher.

Book a readiness assessment

Budgetary estimate, not a quote. Final price depends on the levers above plus data quality and subnetwork complexity — confirmed during a readiness assessment, where we tighten this to a fixed not-to-exceed. The assessment is a flat $10K, credited toward your migration if you proceed.

Where every migration starts

It starts with a readiness assessment.

Before a single feature moves, we read your geometric network geodatabase and score it — schema alignment, connectivity integrity, data quality, and how cleanly it crosswalks to the real Esri asset packages. The output is a clear readiness picture and a fixed not-to-exceed migration price. It's a flat $10,000, credited in full toward your migration if you move forward.

  • A measured UN-readiness score across eight dimensions
  • A crosswalk to the genuine Esri Utility Network asset packages
  • Findings ranked by severity, with a fixed-price path to go-live
Explore the readiness assessment →
60/100
Sample readiness score
74,723
Features assessed
97%
Auto-mappable attributes
8 dims
Scored end to end
FAQ

How the migration works.

The common questions utilities ask before moving off the geometric network.

What are the steps in a migration?
It starts with a readiness assessment that scores your geometric network geodatabase and gives you a fixed not-to-exceed price. From there, senior engineers design the target Utility Network asset package, the AI agent workforce transforms and conditions the data — schema crosswalk, connectivity healing, associations, and subnetworks — and we validate with reference traces and reconcile against known field conditions before go-live.
How long does it take?
Most migrations reach go-live in roughly four to six weeks, versus the 12 to 18 months a manual effort typically takes. Engineers design the model up front while agents do 85%+ of the transformation and validation in parallel.
How disruptive is it to our operations?
Very little. We work from a copy of your geodatabase, so your system of record keeps running untouched while we build. Cutover is planned with your team around storm seasons and freeze periods, and is typically a single scheduled window.
What do you need from us to get started?
A copy of your geometric network File Geodatabase and a little time from the people who know your network — usually a lead GIS analyst and an operations contact for switching and normal status. That's enough to produce the readiness assessment and scope the work.
Do we need Esri licenses, ArcGIS, or Windows on our side?
Not for the assessment — it runs on open-source tooling with no arcpy, no Esri license, and no Windows. The migration itself targets the genuine Esri Utility Network and is executed in your ArcGIS Enterprise under your license; we build everything to drop cleanly into it.
What happens to our downstream systems — billing, OMS, AMI?
They're part of the plan, not an afterthought. The crosswalk preserves the identifiers those systems key on, and we flag every place a downstream integration references the old schema so it can be re-pointed deliberately. Nothing about your network's identity is changed silently.

Move off the geometric network in weeks.

Start with a readiness assessment — a clear score, a crosswalk, and a fixed not-to-exceed price, before you commit to anything.

Get a readiness assessment → Talk to an engineer →

Get the latest updates

Subscribe to our newsletter

Utility Network migration insights and field notes from the geometric-network exodus — a few times a quarter, no fluff.

An AI agent workforce for utility GIS — off the retired geometric network and onto the Esri ArcGIS Utility Network, backed by senior engineers.

hello@nutility.io
2650 W Belleview Ave, Suite D-100
Littleton, CO 80123
© 2026 Nutility, LLC. All rights reserved.