- The March 2026 deadline framing is historical and requires current vendor confirmation
- Cost depends on licensing, implementation, data migration, training, scope, and region
- A current decision needs an organisation-specific cost model rather than a typical range
- Alternatives include minimal migration, open-source, hybrid approaches, or workflow automation first
Quick Answer
There is no universal ArcGIS Utility Network migration cost. The figures in this retained article are historical illustrations. A current estimate must separate licensing, implementation, data migration, training, productivity impact, scope, region, and contract assumptions.
If you are a GIS manager at a utility company, you may be comparing Geometric Network and Utility Network. The decision depends on current vendor status, network requirements, data condition, delivery model, and available evidence.
This retained note groups the cost categories that a planning review should test: licensing, implementation, data work, training, validation, and operational change. It is not a current quote, benchmark, or client result.
HISTORICAL DEADLINE CONTEXT
The source linked in this retained note framed Geometric Network retirement around March 2026. Treat that as historical context and confirm the current Esri support and migration position before acting.
- •The original note recorded an expected end to patches, updates, and security fixes
- •The original note recorded an expected change to Esri support for Geometric Network issues
- •Compatibility with future ArcGIS Pro versions must be checked against current documentation
Do not use this dated block as a live deadline notice.
What the Historical Note Compared
The Utility Network (UN) is not simply a renamed Geometric Network. The original comparison describes a different architecture and capability model:
| 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 |
A capability comparison is not a recommendation. Confirm the required workflows, current product documentation, and operational constraints before selecting a target architecture.
ArcGIS Utility Network Licensing Costs
Current Esri pricing is not established by this article. The following table is a historical composite illustration from the original note. Verify current pricing with the vendor and the organisation's contract.
HISTORICAL LICENSING ILLUSTRATION — NOT CURRENT PRICES
Original scenario: mid-sized utility with 20–50 GIS users; currency, date, region, and contract must be revalidated.
If you are already on ArcGIS Enterprise, the current baseline differs from a Desktop-only deployment. Before committing to Utility Network, audit your current licence usage and record the capability, contract, region, and support assumptions.
The Hidden Costs Nobody Mentions
Licensing is only one category. Implementation can add material scope through data preparation, configuration, training, validation, and operational change.
Historical data-migration illustration: $100,000–$500,000+
Your Geometric Network does not simply "convert" to Utility Network. The data model is different. The original note linked Esri's Migration Toolset; confirm current tooling, schema work, data cleanup, and QA requirements for the target project.
Historical implementation illustration: $150,000–$750,000
The original note allowed for external implementation support and used a $200–$400/hour partner-rate illustration with a 6–18 month range. Treat both as historical assumptions, not current rates or a delivery promise.
Historical data-quality illustration: $50,000–$200,000
Utility Network data rules can make data condition material to scope. Check disconnected features, topology errors, missing attributes, and other validation requirements rather than assuming that legacy data will pass.
Historical training illustration: $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.
Historical productivity-loss illustration: 15–30% for 6–12 months
The original note treated transition productivity as a planning risk. Measure the effect for the target team; do not assume a fixed productivity percentage or duration.
HISTORICAL COMPOSITE ILLUSTRATION — NOT A CURRENT ESTIMATE
Original composite: licensing + implementation + data migration + training + productivity loss. Rebuild with current, scoped evidence.
Is the Utility Network Worth It?
The short 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. For teams considering open-source alternatives, our ArcPy to GeoPandas migration guide covers the practical translation. See also 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, map the existing workflows and their evidence requirements. In some cases, workflow improvement is a better first question than platform change. Discuss a workflow.
Realistic Migration Timeline
The original note used January 2026 as its reference point. The timeline below is a historical illustration, not a current delivery promise.
⚠️ TIMELINE WARNING
The original note used a 6–18 month migration range, based on the linked industry analysis. Treat the range and the March 2026 deadline framing as historical. Current timing depends on scope, data condition, staffing, vendor support, and validation.
Questions for a current review:
- • Confirm current support and migration options with Esri
- • Define the minimum required capability and migration scope
- • Record the risks of retaining the current system during transition
- • Compare delivery approaches, validation needs, and partner assumptions
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.
A useful next step is to map the workflow before choosing a platform. Whether you stay on Esri or consider another option, the decision should be supported by current evidence, validation, and operational ownership.
Start with your workflows. The platform decision follows from there.
Get Workflow Automation Insights
Monthly tips on automating GIS workflows, open-source tools, and lessons from enterprise deployments. No spam.