- Esri Geometric Network retires March 2026 — all utilities must migrate or run unsupported
- Typical first-year cost: $500K–$1.5M+ (licensing + implementation + data migration + training)
- Annual licensing alone: $150K–$400K for mid-sized utility with 20–50 GIS users
- Alternatives exist: minimal migration, open-source (PostGIS), hybrid approaches, or workflow automation first
If you're a GIS manager at a utility company, you've probably heard: "Geometric Network is retiring. Migrate to Utility Network." But nobody's giving you straight answers about what it actually costs.
We've helped utilities evaluate this decision. Here's what we've learned about the real costs—licensing, implementation, and the hidden expenses that catch everyone off guard.
THE MARCH 2026 DEADLINE
Esri will retire the Geometric Network in March 2026. After this date:
- •No more patches, updates, or security fixes
- •Esri support for GN issues will end
- •New ArcGIS Pro versions won't support legacy networks
If you haven't started planning, you're already behind.
Why Esri Is Forcing This Migration
The Utility Network (UN) isn't just a renamed Geometric Network. It's a fundamentally different architecture:
| Capability | Geometric Network | Utility Network |
|---|---|---|
| Subnetwork management | ✗ | ✓ |
| Real-time tracing | Limited | Advanced |
| Data integrity rules | Basic | Built-in |
| Web editing | ✗ | ✓ |
| Cloud deployment | Desktop only | Enterprise/Cloud |
The UN is objectively better technology. But "better" doesn't mean "free" or "easy."
ArcGIS Utility Network Licensing Costs
Esri doesn't publish Utility Network pricing publicly. You need to contact their sales team. But based on industry conversations, here's what utilities typically face:
TYPICAL ANNUAL LICENSING COSTS
For a mid-sized utility with 20-50 GIS users
If you're already on ArcGIS Enterprise, some of this is sunk cost. But many utilities on Desktop-only deployments face a significant jump.
The Hidden Costs Nobody Mentions
Licensing is just the start. Implementation is where budgets blow up.
Data Migration: $100,000 - $500,000+
Your Geometric Network doesn't just "convert" to Utility Network. The data model is fundamentally different. Esri's new Migration Toolset helps, but expect schema redesign, data cleanup, and extensive QA.
Consulting/Implementation: $150,000 - $750,000
Unless you have deep UN expertise in-house, you'll need consultants. Esri partners charge $200-400/hour. A full implementation takes 6-18 months.
Data Quality Remediation: $50,000 - $200,000
The UN has strict data integrity rules. Your legacy data probably doesn't comply. Disconnected features, topology errors, and missing attributes all need fixing.
Training: $25,000 - $75,000
The UN works differently. Your GIS team needs training. Your field crews need training. Your customer service staff who use GIS need training.
Productivity Loss: 15-30% for 6-12 months
Even with training, expect a significant productivity dip. Staff who knew the old system inside out are now beginners again.
TOTAL FIRST-YEAR COST ESTIMATE
Licensing + implementation + data migration + training + productivity loss
Is the Utility Network Worth It?
Here's the honest answer: it depends on your situation.
UN MAKES SENSE IF...
- You need advanced tracing capabilities
- Web/mobile editing is a priority
- You're already on ArcGIS Enterprise
- Your data is already clean and well-structured
- You have budget and 12+ months to implement
RECONSIDER IF...
- Simple tracing meets your needs
- You're primarily Desktop-based
- Your data has significant quality issues
- Budget is constrained
- You have less than 6 months until deadline
Alternatives to Full UN Migration
Not every utility needs to go all-in on Utility Network. Here are other paths:
1. Minimal Migration
Migrate to UN with a simplified data model. Skip advanced features you don't need. Lower cost, faster implementation, but you may need to revisit later.
2. Open-Source Alternative
PostGIS + pgRouting can handle network analysis for many use cases. No licensing costs. But you lose Esri ecosystem integration and need strong technical skills in-house. See our ESRI migration guide.
3. Hybrid Approach
Keep UN for core network management. Move everything else to open-source or cloud-native tools. Reduce Esri footprint while maintaining critical functionality.
4. Workflow Automation First
Before migrating platforms, automate your existing workflows. Often the biggest ROI comes from eliminating manual processes, not changing platforms. Get a free workflow assessment.
Realistic Migration Timeline
If you're starting now (January 2026), here's what's realistic:
⚠️ TIMELINE WARNING
A typical UN migration takes 6-18 months according to industry analysis. The March 2026 deadline is 2 months away. If you haven't started, you cannot complete a full migration in time.
Options at this stage:
- • Request deadline extension from Esri (some utilities have negotiated this)
- • Implement minimal viable UN migration
- • Accept running on unsupported GN temporarily while migrating
- • Accelerate with fixed-fee migration packages from Esri partners
Discovery & Planning
4-8 weeksAssess current state, define requirements, plan data model
Data Preparation
8-16 weeksClean data, fix topology, prepare for migration
UN Configuration
4-8 weeksSet up UN schema, rules, subnetwork definitions
Data Migration
4-12 weeksMigrate data, validate, fix issues
Testing & Training
4-8 weeksUser acceptance testing, staff training
Go-Live & Support
4-8 weeksProduction deployment, hypercare support
Total: 28-60 weeks (7-15 months)
The Utility Network migration is expensive and complex. But running on unsupported software isn't an option either.
Our recommendation: don't just think about platform migration—think about workflow automation. Whether you stay on Esri or move to open source, the real ROI comes from eliminating manual processes.
Start with your workflows. The platform decision follows from there.
Workflow-Automatisierung Einblicke erhalten
Monatliche Tipps zur Automatisierung von GIS-Workflows, Open-Source-Tools und Erkenntnisse aus Enterprise-Deployments. Kein Spam.