Import

Bringing customers, leads, items or expenses in from a CSV file, with a dry run before anything is written and an undo afterwards.

When you would use this: moving your existing customer list, catalogue or expense history in from wherever it lives today, rather than typing it all in by hand.

The steps: choose what the file holds (customer, lead, item or expense — leads only offered if your firm has that module), download the sample so your columns match what the product expects, upload your file, then map your columns to the product's fields. Nothing is written to the database yet at this point.

Dry run: simulates the whole import and tells you what it would create, update or skip, and any row it would refuse, before you commit to anything real.

Running it: once you are satisfied with the dry run, running for real writes the rows, and the job's own row shows counts of what was created, updated, skipped and errored.

Undo: available after a completed run, for as long as nothing that import touched has since been changed by something else — it reverses exactly what that one import did, nothing more.

A narrower view: none — importing at all needs its own capability, held the same way for every entity type; there is no split between viewing past imports and starting a new one.

When it refuses: "Import is not available to your role" means you lack the import permission, by default an Admin-and-above capability — ask one of them. A row a dry run flags as an error is telling you the source data itself needs fixing, not the product.