Move fiber inventory into one project map
Bring outside plant out of legacy GIS, sunsetting OSP platforms, or spreadsheets into MapItRight. Import supported formats, map geometry and attributes into a telecom-native model, and keep design and operations on the same Google Maps canvas.
Why fiber migrations stall or fail
Legacy platforms are aging out
Teams on Esri Geometric Network, OSPInsight, AutoCAD sheets, or spreadsheet inventory face platform sunsets, rising costs, or records that no longer scale. Staying put often means paying for tools that were never built for strand-level fiber work.
Generic imports flatten fiber semantics
Many migration paths import lines and points but lose splice connectivity, equipment relationships, and the plant context operations relies on. The map looks complete while the network record is still unusable for tracing and inventory.
Parallel systems create double entry
Running two inventory systems during cutover sounds safe, but teams rarely sustain duplicate updates. Without a clear import and validation plan, migration projects drag on while field and office teams keep working from different records.
How network migration works in MapItRight
Assess, import, validate.
Review source data and mapping
Start with the exports or files you have today: KMZ, KML, GeoJSON, VETRO FiberMap, or structured spreadsheets. Define how cables, locations, splices, and equipment should map into MapItRight's telecom plant model before bulk import.
Import and validate connectivity
Bring geometry and attributes into project maps on Google Maps, then validate strand paths, splice records, and equipment links against samples from your source system. Fix gaps while the legacy record is still available for reference.
Cut over to one operational map
Move day-to-day design, field updates, and reporting to MapItRight. Use Planned and Active states to separate future buildout from live plant, export GeoJSON or KML for backup, and connect downstream tools through the API when needed.
What migration teams can import today
KMZ and KML
Bring Google Earth and common GIS exports into MapItRight projects with geometry mapped to plant elements.
GeoJSON
Import structured spatial exports and align attributes to cables, locations, and equipment.
VETRO FiberMap
Move project exports from VETRO into MapItRight's telecom-native plant model.
Spreadsheet-assisted imports
Use structured tabular data alongside spatial files when attributes need cleanup or enrichment during migration.
Roadmap import formats
ArcGIS geodatabase (.gdb), Shapefile (.shp), DXF, and GeoPackage (.gpkg) are on the roadmap for direct import.
Export for backup and reuse
Export migrated projects to GeoJSON or KML so you keep a portable copy outside the source system.
“There is nothing out there as robust as MapItRight. Thanks a lot.”
Related solutions
Frequently asked.
MapItRight currently supports KMZ, KML, GeoJSON, and VETRO FiberMap exports. Additional formats such as ArcGIS geodatabase (.gdb), Shapefile (.shp), DXF, and GeoPackage (.gpkg) are on the roadmap. See Network Asset Management.
Ready to see network migration in action?
30-minute demo. No slideware. We'll walk through your network, not ours.