Migration and data import
Bring your existing drawings, tables and geographic records into a shared project record for your fiber network. Define data preparation, import checks and responsibilities together.
Start by assessing your existing information.
The migration scope depends on how source files are organised, their coordinate information and your organisation’s record requirements. As well as being importable, the resulting records need to represent the infrastructure in the field correctly.
Source records
Identify the drawings and tables in use, how current they are and who is responsible for them. Assess records of the same infrastructure across different files alongside their source names.
Target record structure
Clarify which fields will hold cable, node, device and connection information. Treat locations shown on drawings and fiber and port connections as distinct information.
From preparation to a current project record.
Discovery
Create an inventory of existing drawing, table and GIS records. Identify current source files, records to assess together and the people responsible for completing missing information. Assess the schedule and data conversion requirements during scoping.
Preparation
Check file formats, layers and the coordinate system. Review names, types, statuses and fiber counts when mapping source columns to target fields. Choose a stable record key for sources that will be updated regularly.
Import checks with selected data
Preview the selected sources and assess groups, target record types and field mappings. Cable endpoints can be linked to suitable node records. Review ambiguous endpoints and import warnings, and check fiber and port connections separately.
Acceptance
Review the resulting records on the map and in selected record details. Assess reasons for features that could not be imported, empty fields and unsuitable geometries. Your designated team compares locations and record contents with its own sources.
Daily use and importing updates
Define data owners and team access. When a source is updated, compare the new file with project records through the source difference report. Assess field corrections and source changes separately to decide which information to retain.
Assess drawings and geographic records together.
Import map data from KML, KMZ, GeoJSON, Shapefile, CSV, DXF, GeoPackage and FileGDB. Prepare each file for its format and verify its layers and coordinate reference in the preview.
For tabular records, identify the columns containing geometry or location information. Drawing layer names and attributes are used to map target records. The guide explains preparation requirements and import steps for each file type.
Importing a file does not mean that every line has become an operational connection model. Review cable endpoints, fiber connections and device ports through their own records. This helps teams use drawing information correctly in operations and field work.
Drawings used only for reference can be kept as reference layers. Map network data to the appropriate network feature type when it needs to be edited. This makes clear which parts of the source become organisational records and which remain visual references.
After reviewing import results, compare locations, names and numeric fields in selected records. Retain the key field and source name within your record structure if the same source will be used again.
Agree who will provide each piece of information.
The following division of work helps define the data conversion service scope. Deliverables and responsibilities are confirmed in the agreement.
| Work | Your organisation | SoSo Labs |
|---|---|---|
| Identifying sources | Provides current files, data owners and intended use. | Assesses import and preparation requirements during scoping. |
| Data preparation | Confirms missing source information and the coordinate reference. | Carries out the agreed data conversion service. |
| Mapping and import | Confirms field meanings and target record requirements. | Supports import preparation and checks within the agreed scope. |
| Acceptance and use | Assesses imported information and identifies data owners and users. | Supports the transition to use through deployment and training. |
Data conversion is an additional service. Pricing and the service description are on the plans page; the schedule depends on the condition of source data and the agreed scope.
Explore the data conversion service → · Explore support and training →
Define a migration scope for your existing data.
Let us assess file formats, record structure and data conversion requirements.
