Spatial7 EAM Data & Migration SpecialistLesson 1 of 4 · 0% complete
Preparing asset data for Spatial7

Preparing a source register

Cleansing before import, and the traps that cause a migration to fail.

45 min

Clean before you load

An import will not fix a source file. It will faithfully load whatever it is given, warnings and all. Before uploading:

  • Remove subtotal, blank and note rows from the middle of the data
  • Make every asset ID unique — duplicates cannot be resolved inside the platform
  • Standardise dates into one recognisable format
  • Decide the unit for every dimension column and state it in the header
  • Replace placeholders (N/A, TBD, unknown) with empty cells; a placeholder is not a value

Geometry

Where a file carries geometry, it must be readable as WKT or GeoJSON, or as coordinate pairs with a stated CRS. Half-copied geometry containing an ellipsis will be rejected and flagged for review — as it should be.

Use the template

Start from the Spatial7 import template, keep its column names where you can, and add the organisation's own columns after them. Extra columns are preserved as attributes, not discarded.

Create an Academy account to track your progress and resume where you stop.

Skip to Mapping to the Spatial7 taxonomy