Skip to main content
Try for free

Data Import: Understanding the Basics

Before you load customers, vendors or parts, set up the code tables they point at, and import in an order where everything a file refers to already exists.

Updated Nov 9 2026

Data Import: Understanding the Basics

Allow external media cookies to watch this video.

Before you start

  • Data Import is under Admin > APIs & More, shown to users with the Can View API & Import Submenu function (API Access role by default; Admin always).
  • Code tables can also be typed in by hand under Admin > Maintenance > Data Maintenance (see the Data Maintenance guide). That screen lists them by table name, for example 9TERMS (Credit Terms), FOBCode, UOM and LNAME (Locations).
  1. Plan the import order

    Cetec's suggested order for imports, by group, is below. The Get Started link on the Import Documentation page shows the same order.

    1. Data Maintenance – code tables such as Terms, Shipping Methods, FOB Codes, Business Types, Credit Codes, Unit of Measure, UOM Conversion, Warehouse Locations and Work Centers.
    2. Accounting – Chart Of Accounts (and Expenses).
    3. Customers – Customers, then Customer Contacts, Customer Addresses, Customer Shipvias.
    4. Vendors – Vendors, then Vendor Contacts.
    5. Parts – PRCs, Parts, BOMs, Part Warehouses, Bins and the other part imports.
    6. Then pricing, invoices, purchase orders, sales orders, vouchers, labor plans, notes, tools and documents.

    The rule behind the order: a file can only refer to records that already exist. Validation stops a row that points at a missing code (for example Terms was not found).

  2. Know what each import needs first

    ImportMust exist first
    CustomersThe Terms code named in the Terms column (matched on the terms code's External Key).
    Customer ShipviasThe customer (Customer External Key) and the Shipping Methods entry named in Shipvia Method Of Shipment.
    VendorsThe Terms, FOB Codes and Shipping Methods entries named in the file.
    PartsAn active PRC for the first three characters of every Part Number; any Unit Of Measure / Purchase Uom named in the file.
    BOMsBoth the assembly and the component parts.
    Bins (stock)The part, the Warehouse Location and the part's record at that location.

    Columns that are blank are not looked up, so an optional code column can be left empty.

  3. Check the columns for an import

    1. Go to Admin > APIs & More > Data Import and pick the import in Import Type.
    2. Available Import Columns lists Required Columns, Suggested Columns and Optional Columns; click a section's arrow to expand it. Click Download Template for a file with those headings.
    3. For what each column means, click Import Documentation at the top of the page (or Admin > APIs & More > Data Import Documentation). Each column is a card; click a card to turn it over. The back shows Pre-Req, the table a value must exist in.

Related

How-tos
Blog Posts
Docs