Don’t Migrate your Problems

All Blog Articles

.

Moving to a new home has a way of revealing just how much has accumulated over the years. You open a closet and find things you haven’t used in a decade. Boxes nobody remembers packing, or things you’ve kept because they might be useful someday.

That same accumulation happens in enterprise systems. Most utilities I talk to plan their move to ArcGIS Utility Network as a lift-and-shift. Move the data, recreate the applications, reproduce the workflows, and get everyone working again as quickly as possible.

That approach gets people working again quickly. It also carries twenty years of accumulated decisions into a brand new platform. The more valuable question is: What should we bring with us?

Migration is an Opportunity to Reset

Most established utility GIS environments carry a history. Data models have evolved over years or decades. Applications have been added to solve specific needs. Workflows have grown around organizational structures, technology limitations, and business requirements that may have changed long ago.

None of this means the existing environment was poorly designed. In many cases, those processes and applications did exactly what they were supposed to do. But migrating them 1:1 into a new Utility Network environment preserves complexity that no longer serves the business. That’s why one of the most useful things a utility can do before and during migration is examine the current environment with fresh eyes.

Which applications are still actively used? Which workflows could be simplified? Where are users maintaining duplicate information? Which customizations still deliver genuine business value? And which exist primarily because, at some point in the past, there wasn’t a better way? There’s no need to discard everything, but it’s the opportunity to make deliberate choices about what deserves to move forward. In my experience, when utilities inventory their environment before migrating, they find that a meaningful share of the applications they planned to carry forward haven’t been touched in years.

Rethink the workflow, not just the technology

This becomes particularly important when considering business processes. A new technology platform creates an opportunity to reconsider how work gets done rather than simply rebuilding familiar screens and functions in a new environment.

For example, a process that once required several applications, manual handoffs, or specialized GIS expertise becomes a simpler digital workflow. Purpose-built applications can make information that historically lived inside the GIS department accessible to planners, operations teams, managers, or field personnel.

So the question changes from “How do we reproduce what users have today?” to “What are users actually trying to accomplish?” That distinction uncovers opportunities that a straightforward migration might miss.

Clean up what sits underneath

The same principle applies to data. Utility Network (UN) depends on well-structured, connected, trustworthy network information. Migration creates a natural point to identify data-quality issues, inconsistent attribution, duplicate information, and legacy structures that have accumulated over time.

Trying to resolve every historical data issue before moving forward can create a never-ending project. But carrying known data gaps and legacy constraints into the new environment simply postpones the work and can make it harder to use the capabilities that motivated the migration in the first place.

A practical approach is to prioritize:

• Identify the issues that affect network integrity, important workflows, analysis, or future applications
• Establish governance around how information will be maintained
• Continue improving the environment iteratively rather than treating migration as a one-time cleanup exercise

Build for what comes next

The biggest reason not to recreate the old environment is that Utility Network isn’t simply a new home for yesterday’s GIS. It can become the foundation for broader access to network intelligence, more sophisticated analysis, improved digital workflows, and closer integration between GIS and the rest of the utility.

That potential is much harder to realize if the new environment begins life carrying every constraint of the old one. Simplify where possible, preserve what works, retire what doesn’t, and establish processes and governance that can evolve as the utility’s needs change. Moving is always work. But there isn’t much value in carefully packing every box if half of them belong in the recycling.

If you are within a year of a Utility Network migration, the conversation about what deserves to carry forward should happen now, not after go live. See how VertiGIS Networks can help you turn your Utility Network investment into intuitive, accessible applications for the people who rely on network information every day.

All Blog Articles