Bring your existing records in.

Supported formats

• CSV. Tabular records like sites, contacts, and structures with latitude and longitude.
• GeoJSON. Spatial layers like outfalls, BMPs, and drainage assets.
• Shapefile. Standard shapefile bundles for spatial layers; attribute fidelity is preserved on import.

WGS84 is the standard coordinate system. Layers store WGS84 so they move cleanly between NPDESTracker, ArcGIS Online, ArcGIS Enterprise, and QGIS.

Recommended import order

1. Sites (parcels, facilities, properties).
2. Contacts (owners, operators, responsible parties, reporters).
3. Spatial assets (outfalls, BMPs, structures, drainage features).
4. Inspection history (prior inspections tied to sites and assets).

This order keeps foreign references resolvable. Sites and contacts come first, then spatial features that reference them, then the inspection history that points at both.

CSV column expectations

• Sites. External ID, name, address, parcel, classification, status, optional latitude, optional longitude.
• Contacts. External ID, name, role, organization, email, phone, mailing address, related site ID.
• Structures with lat/lon. External ID, type, status, related site ID, latitude, longitude.
• Inspection history. External ID, related site ID, inspection date, type, finding summary, deficient flag, inspector reference.

Column mapping is guided inside the workspace. The exact field list is shown during the import step so you can match your spreadsheet to the workspace fields.

GeoJSON and shapefile expectations

Attribute fidelity is preserved on import. The original file is retained separately from the optimized display layer used in the workspace map, so you keep a copy of what you provided. Geometries should be valid (no self-intersections), and coordinates should be in WGS84 (EPSG:4326).

Self-service versus guided import

Self-service import is included on every annual plan. The workspace walks you through column mapping, a preview, and a confirmation step before records are written. Bulk migration (large legacy datasets, mixed-source records, custom field reshaping) is scoped separately on Inspection Team and Full MS4 Platform, as noted on /pricing.

Next step

With records in, you can build out the map. Continue to GIS and assets.