Use one row per Location

Keep identifiers, name, address components, coordinates and other fields consistently separated by columns.

Coordinates

Provide valid latitude and longitude wherever possible. Bulk imports are easier to verify when coordinates are already authoritative.

Stable External IDs

If you expect to update the same Locations later, include stable External IDs from the source system. Do not recycle IDs for different real-world places.

Types and Groups

Use stable Type slugs and hierarchical Group slug paths rather than display labels that may change over time.

Pre-import checks

Remove accidental duplicate rows, confirm character encoding, standardize country/city values and test with a small representative file before importing thousands of records.