CSV import templates

Import your existing lists from a spreadsheet instead of typing them in.

Workspace admins import lists under Settings → Import, or in the Suppliers step of setting up a workspace. Choose a list, download its template, fill it in and upload it as a CSV file: one list per file, up to 1.9 MB and 5,000 rows. Mittral checks the whole file and shows what it will add and update before anything is saved. To add or change a few records, use Suppliers and lists or Entities instead: the same rules apply to each record.

How imports work

  • All or nothing. If any row has a problem, nothing is imported, and every problem is listed by its row number in the spreadsheet.
  • Matched by code. A new code adds a row; a code that’s already there updates it.
  • Only the columns in your file change. A column you leave out keeps its current values. A blank cell clears an optional value (a blank Approved or Active means yes).
  • Nothing is deleted. Rows that aren’t in the file are left alone, and a code that was removed earlier comes back.
  • Headings are matched without case, spaces or punctuation, and some common alternatives are accepted (listed below). Unknown headings are refused.

Suppliers

Template: mittral-suppliers.csv. Rows are matched on Code.

Suppliers template columns
Column Required What goes in it
Code Yes Your code for the supplier, e.g. BRI001. Also accepted: code, supplier code.
Name Yes The supplier’s name, as printed on POs. Also accepted: supplier, supplier name.
Email No Where purchase orders are emailed. Leave blank to send them yourself. Also accepted: email address, po email, orders email.
Contact person No Who you deal with there. Also accepted: contact.
Phone No Their phone number. Also accepted: telephone, phone number, tel.
Approved No Yes or No. Requests to unapproved suppliers ask why. Blank means Yes.
Credit limit No Optional, as a plain number, e.g. 5000.
Currency No Optional three-letter code the supplier invoices in, e.g. USD. New requests to them start in it when your workspace allows it. Also accepted: default currency, supplier currency.

Items

Template: mittral-items.csv. Rows are matched on Code.

Items template columns
Column Required What goes in it
Code Yes Your item or product code. Also accepted: code, item code, product code, sku.
Description Yes What it is, as it appears on request lines. Also accepted: name, item.
Group No Optional category. Also accepted: category, item group.
Unit cost No Optional latest price, as a plain number, e.g. 24.50. Also accepted: price, unit price, cost, latest unit cost.

GL accounts

Template: mittral-gl-accounts.csv. Rows are matched on Account.

GL accounts template columns
Column Required What goes in it
Account Yes The account number or code, e.g. 5100. Also accepted: account code, account number, gl account, code.
Description No What it’s for, e.g. Office supplies. Also accepted: name, account name.
Type No Optional, e.g. Expense. Also accepted: account type.

Projects

Template: mittral-projects.csv. Rows are matched on Code.

Projects template columns
Column Required What goes in it
Code Yes Your project code. Also accepted: code, project code, project.
Name No The project’s name. Also accepted: project name, description.
Branch code No Optional: the code of a branch already in Mittral. Also accepted: branch.
Active No Yes or No. Inactive projects aren’t offered on new requests. Blank means Yes.

Entities

Template: mittral-entities.csv. Rows are matched on Code.

Entities template columns
Column Required What goes in it
Code Yes Your short code for the company, e.g. ACME. Also accepted: code, entity code, company code.
Name Yes The company’s name, as people pick it on requests. Also accepted: entity, entity name, company, company name.
Legal name No The registered name printed on its POs, if it differs. Also accepted: registered name.
Address No Printed on its POs. Line breaks inside the cell are kept.
Tax number No Its VAT, GST or sales tax number, printed on its POs. Also accepted: vat number, gst number, tax id, tax no.
Phone No Printed on its POs. Also accepted: telephone, phone number, tel.
Email No The contact email printed on its POs. Also accepted: email address, contact email.

Branches

Template: mittral-branches.csv. Rows are matched on Code.

Branches template columns
Column Required What goes in it
Code Yes Your branch code. Also accepted: code, branch code.
Name Yes The branch’s name, used as the delivery location. Also accepted: branch, branch name.
Entity code No The code of the company it belongs to. Can be left blank when the workspace has one company. Also accepted: entity, company, company code.
Site code No Optional short site reference. Also accepted: site.