Esri retires the Geometric Network in March 2026. Here's what to do.

If your fiber network is running on legacy ArcMap with the Geometric Network, you have one decision to make in 2026, and it's irreversible: stay on Esri and migrate to the Utility Network, or switch vendors. Esri's published end-of-life for Geometric Network is March 2026. After that, the support ends; the platform doesn't.

We've spent the last 18 months helping operators evaluate both paths. This article is what we wish someone had handed us at the start.

The forced choice, in two paragraphs

Path A is migrating to ArcGIS Utility Network. That's the Esri-native forward path. Typical first-year deployments include Esri enterprise licensing, partner SI fees, and dedicated GIS staffing — a substantial investment, with timeline of 6–18 months. You'll need either a dedicated GIS team or a partner SI charging $150–$250/hr. After all that, you're back to where you were — same data model, slightly newer architecture, but no new business value.

Path B is switching vendors. The candidate set is small: IQGeo (Tier-1 carrier-grade, no public pricing), VETRO FiberMap (ISP-focused, also no public pricing), 3-GIS (Esri-anchored partner — defeats the purpose), and MapItRight (yes, that's us). The economics on this path are dramatically different: weeks instead of months, sub-$50K instead of mid-six-figures, no SI required.

Why Path A costs what it does

Three components compound the cost.

• ·Esri licensing — the Utility Network requires ArcGIS Enterprise (not Online), which is a multi-tier licensing stack. Mid-market deployments quote at $50K–$200K/year before extensions.
• ·Partner SI fees — Esri's recommended deployment path uses a system integrator (1Spatial, Schneider, Epoch, TRC, etc.). SI fees on a typical mid-market deployment land at $200K–$800K.
• ·Internal team — to actually run the migration, you need a dedicated GIS specialist (or two) for 6–18 months. That's $150K–$400K in fully-loaded labor.

Add it up: a significant six-figure investment, year one. And you're not done at year one — Utility Network has ongoing licensing, ongoing partner-SI engagement, and ongoing internal staffing.

Why Path B is so much cheaper

The structural difference is who runs the migration. Path A puts a partner SI in the middle. Path B doesn't.

Modern fiber GIS vendors (us included) have built importers that consume your existing GDB exports and translate them to a telecom-native data model in days, not months. Strand connectivity is preserved. Splice geometry is preserved. Attribute history is preserved. Your fiber engineers can run the import themselves; they don't need ArcGIS Pro expertise.

We've done this for 8 customers in the last 12 months. Median timeline: 6 weeks for clean data, 60–90 days when there's data cleanup involved. Cost range: $5,099.90 (our Pro tier annual) to $50K (Enterprise + migration services). That's not a typo.

What's actually changing in March 2026

To be precise: Esri is ending support for the Geometric Network as of March 2026. ArcMap itself was deprecated in 2020 and will be retired around the same time. After March 2026, you can technically keep running ArcMap, but Esri won't issue patches, and the Utility Network is the only forward path within the Esri ecosystem.

How to actually decide

The honest decision tree:

• ·If you're a Tier-1 carrier or national fiber wholesaler, Path A (Utility Network) is probably the right call. You have the budget, the GIS team, and the procurement cycle that makes it work.
• ·If you have specific regulatory requirements requiring on-prem GIS, Path A is also probably right. Most modern SaaS fiber GIS vendors are SaaS-only.
• ·Otherwise — if you're a regional ISP, electric coop, municipal broadband program, or engineering firm — Path B is almost always right. The math doesn't work for sub-Tier-1 operators on Path A.

What's next

If you're on Path A, your priority right now is scoping the SI engagement and locking the project before everyone else does. If you're on Path B, the priority is selecting a vendor and running a parallel-import to validate before cutover.

We've published a longer comparison at /vs/esri-utility-network with a 60-day migration playbook. We've also published our pricing — see /pricing. Neither requires a sales call to read.