# Importing data — the magic importer

> Drop any file at /import/ — geoDB detects what it is and pre-maps the columns.

Source: https://geodb.io/guide/topic/import_magic/ · Category: Getting data in
Getting data into geoDB starts at one place: the **magic importer** at
`/import/`. Drop almost anything onto the upload zone — CSV, Excel, zipped
shapefiles, GeoPackage, KML/KMZ, even lab certificate PDFs — and geoDB works
out what kind of data it holds. You never have to say "these are drill
collars" first.

## What auto-detection does

When you click **Analyze & Import**, geoDB reads your file's headers and a
sample of rows, scores it against every data type it knows (drill collars,
samples, surveys, lithology, assay certificates, water data, land holdings
and more), and picks the best match with a confidence score. High confidence
goes straight to the right import wizard; medium confidence asks you to
confirm; low confidence lets you choose the type yourself.

## The import wizard

The wizard opens with your columns already mapped — geoDB matches your header
names against its own field names, common industry synonyms, and any custom
column names your project has configured. You review the mapping, fix
anything it wasn't sure about, and it validates every row before anything is
saved: type checks, coordinate checks, foreign-key lookups (does that hole ID
exist?), and duplicate detection. Nothing lands in your database until
validation passes and you confirm.

## Other ways in

- **Through Petra** — upload a file straight into a Petra chat and she'll
  read it, propose the import, and land it with your approval. Best when the
  file is messy or you want to talk through what it is.
- **Direct wizards** — if you know exactly what you have, each data type has
  its own import page; the magic importer is just the door that picks the
  right one for you.