Get a spreadsheet ready for import
Most import problems start with a shifted row, the wrong postcode level or a value formatted unexpectedly by a spreadsheet. A quick check before import saves a lot of tidying afterwards.
Choose the right importer
Import Excel colours postcode polygons into territories. Create Dots plots locations. Marker Boxes adds labelled locations. Radial Circles draws distance rings. A postcode in a legend note is just printed text. Choose by the result you want, not simply by the fact that your source is Excel.
Keep each record on one row
The postcode, name and settings on row 12 must all describe the same location or polygon. Sort the whole spreadsheet table together. Do not sort the postcode column separately. Check blank rows, merged cells and accidental heading rows.
Match the map and postcode level
A UK postcode area such as YO, a district such as YO18, a sector such as YO18 7 and a full postcode such as YO18 7TG describe different levels. Territory import needs codes compatible with the selected boundary map; location tools need full postcodes for precise positioning.
Keep names consistent
“North team” and a differently spelt version can become separate key entries. Use a single spelling for each territory. Give each territory one consistent colour throughout the sheet.
Preserve codes as text
Postal codes are identifiers, not quantities. Keep leading zeroes where relevant and avoid spreadsheet date conversion. In the advanced location importers, use plain numeric settings and the exact words listed in Column guide.
Read the import result
A loaded file is not always an applied import. Review the fields, choose Import to map, then check any errors or missing postcode results. Keep the original spreadsheet so you can correct and repeat the import without rebuilding it from the map.
Choose the correct import route
Use Import Excel for postcode-to-territory columns; Advanced import under Create Dots, Marker Boxes or Radial Circles for each item’s settings; Additional Data → My datasets for reusable numerical CSV data; or the assistant’s paperclip for a small reference to discuss. Attaching a spreadsheet to the assistant does not import it into My datasets. Each route has its own limits and replace/add behaviour.
Check the limits before preparing a large file
Dots and shapes support up to 2,500 locations per import. Marker boxes remain limited to 500 locations per import. On supported Eircode maps, no more than 200 of those locations can be full Eircodes. These are import limits, not a promised total number of objects per map. If you need more, choose Contact GBMaps and tell us the map, the type of import and approximately how many locations or rows you need, so we can discuss options. Advanced dots and markers CSVs must be smaller than 2 MB. My datasets has separate limits of 25,000 data rows and 8 MB. The assistant paperclip has its own reference-file limits. See Import limits for the full comparison.