Which file formats can I import today?

MapItRight currently supports KMZ, KML, GeoJSON, and VETRO FiberMap exports. ArcGIS geodatabase (.gdb), Shapefile (.shp), DXF, and GeoPackage (.gpkg) are on the roadmap.

How long does migration usually take?

It depends on how clean your source data is and how much connectivity you need to validate. Many regional operators start with a pilot service area and expand project by project rather than attempting a single big-bang cutover.

Will we lose strand connectivity?

MapItRight is built around strand-level modeling. During migration, we focus on validating connectivity as plant comes in especially for operators moving off connectivity models that lived partly in spreadsheets.

Can field crews use MapItRight after migration?

Yes. MapItRight works in any modern phone or tablet browser for map access, marker flags, photos, and plant updates. See Field Crew Collaboration (/features/field-crew-collaboration).

Use Case · Esri Migration

A fiber-native path off enterprise GIS

If Esri has been your map but fiber semantics never felt quite right, MapItRight offers a different path: strand-level plant on Google Maps, transparent pricing, and import workflows built for operators — not GIS integrators.

Book a demo See pricing

app.mapitright.com/use-cases/migrating-from-esri

The problem

Why Esri migrations feel stuck

Generic GIS was never fiber-first

ArcGIS maps geography well, but fiber teams need strand connectivity, splice context, and field workflows that match how outside plant actually runs. Customizing a general-purpose model takes time, budget, and a dedicated GIS team.

Utility Network is a major program, not a quick switch

For many mid-market operators, migrating to Utility Network means a long implementation, partner engagement, and ongoing schema maintenance — even when all you wanted was a trustworthy fiber map.

Operations still need something crews can use

Even with a strong back-office GIS, field teams often work from exports, PDFs, or side spreadsheets because the enterprise tool does not fit a phone in a bucket truck.

How it works

How Esri migration works in MapItRight

Import, validate, operate.

STEP 01

Bring in what you already have

Start from KMZ, KML, GeoJSON, or VETRO FiberMap exports today. Additional formats such as ArcGIS geodatabase (.gdb) and Shapefile (.shp) are on the roadmap. We help you understand what maps cleanly into MapItRight's fiber model.

STEP 02

Rebuild connectivity on a fiber-native map

Model strands, splices, splitters, and drops on Google Maps with Planned and Active states. Trace light paths and validate connectivity as you bring plant live in MapItRight.

STEP 03

Move day-to-day work to one project map

Office planners and field crews work from the same record. Export project data when you need backup or downstream processing, and keep plant current after go-live.

Capabilities

What Esri migrators get in MapItRight

Import from common formats

KMZ, KML, GeoJSON, and VETRO FiberMap today — with more formats on the roadmap.

Strand-level connectivity

Trace paths, model splices, and answer operational questions from the map.

Google Maps canvas

A map canvas field teams can open in a mobile browser without a desktop GIS seat.

Planned and Active lifecycle

Separate design plant from live inventory on the same project.

Published pricing

Transparent tiers online — no six-figure quote just to see if the platform fits.

Respectful coexistence

Need ArcGIS for non-telecom GIS? MapItRight can focus on fiber plant while other tools handle the rest.

“There is nothing out there as robust as MapItRight. Thanks a lot.”

Andy Q.

CFO · M33 Access

Explore more

Frequently asked.

For many operators, yes
for the fiber plant workflows they actually use daily: mapping, strand inventory, splice tracing, field updates, and exports. MapItRight does not try to replace every non-telecom GIS workflow. See MapItRight vs Esri Utility Network.