AWRA OpsHub Search

AWRA Help Center

Copy link
Help Workflow Support
01 Custom Fields Platform Tools 02 Workspace Onboarding Getting Started

Importing Your Data

Load your existing items, customers, vendors, assets, warehouses, locations, accounts and employees from a spreadsheet — using the template for that module so the columns match on the first try.

Every module that supports importing carries a template button on its list screen. Download the template, fill it in, upload it back. Do not build your own spreadsheet from scratch: the template already has the right headings in the right order, which is where most failed imports come from.

What Can Be Imported

ModuleWhere the button is
ItemsInventory → Items
Warehouses and LocationsInventory → Warehouses / Locations
Assets and Asset custodiansInventory → Assets / Custodians
CustomersSales → Customers
VendorsProcurement → Suppliers
Chart of accountsAccounting → Accounts
EmployeesHR → Employees, which has its own import with a preview step

How An Import Runs

Small files are processed straight away and you see the result immediately. Larger files are handed to the background so your browser is not left waiting — the import continues whether or not you stay on the page. Either way, every import is applied as a single unit: if the file cannot be processed, you are not left with half of it loaded.

The result reports three numbers: created, updated and skipped. Read all three. An import reporting mostly "updated" when you expected "created" means your file matched existing records — usually the right outcome on a re-run, and a warning sign on a first load.

Check The File Before You Import

Items, customers, vendors, assets, asset custodians, warehouses, locations and the chart of accounts have a Check File button beside Import File in the import window. It is a dry run: the real import runs on every row and is then undone, so nothing is saved and what you see is exactly what the import would do.

  • The verdict. The Import Dry Run page says either “This file is ready to import” or “This file would not import”, with counts of new, updated, already up to date, skipped, warning and error rows.
  • Every bad row, not just the first. Each row is checked on its own, so all the errors are listed together, problems first. An update lists the fields it would change; a blank cell on an existing record leaves that field as it is.
  • Warnings point out things the import accepts but you may not mean, such as a warehouse, location or custodian code that matches nothing, or the same record twice in one file. Rows with warnings import as they are.
  • Import from the same page. When there are no errors, Import N rows saves the exact file you checked, without uploading it again. While any row has an error the button stays off, because one bad row stops the whole import.
  • A dry run checks up to 2,000 rows; split a bigger file, or import it directly. A checked file can be imported once, and a dry run you never import expires after a day.

Getting It Right First Time

  1. Import in dependency order. Warehouses and locations before items with stock; accounts before anything posting to them; departments and positions before employees.
  2. Do not rename or reorder the template headings. Extra columns are fine to leave; renamed ones are not recognised.
  3. Test with ten rows. Load a small slice, check the records look right, then load the rest. Fixing ten wrong rows is a minute's work; fixing two thousand is a project.
  4. Watch your spreadsheet's helpfulness. Leading zeros stripped from codes, dates reformatted to the local convention, and long numbers turned into scientific notation are spreadsheet behaviours, not import faults. Format those columns as text before you type in them.
  5. Custom fields can be imported too where the module has them — see Custom Fields.

Employees Are Different — In A Good Way

The employee import has an explicit preview step: you upload, see exactly what would be created or changed, and only then commit. Where you have the choice, that is the pattern to prefer. See Employee Management.

Import History

Every import that goes through is recorded under Import history (/import-history, also reachable from each template’s import button). Each entry records who ran it, which file, when it started and finished, and how many rows were created, updated, unchanged, skipped or failed, together with the error and the row it stopped on if it failed. Open an entry to see each row’s outcome and the fields it changed. You see the history only for the templates you are allowed to import yourself.

If An Import Goes Wrong

Records created in error can be deleted and recovered from Trash, but an import that updated the wrong records is far harder to unwind — which is the real reason to test with ten rows. Stock balances are not loaded by import: bring stock in through a check-in or an opening adjustment, so the movement has a record behind it.

Need help with this topic?

Capture the module, record number, branch or warehouse, user, visible message, and what you expected to happen before contacting support.

Open support guide