How do I import from Excel?

Accessories

Accessory Checkouts

Assets

Asset Checkouts

Audits

Categories

Components

Component Checkouts

Consumables

Consumable Checkouts

Departments

Depreciations

Employees

Licenses

License Product Keys

License Checkouts

Locations

Maintenances

Manufacturers

Products

Suppliers

accessory_name (required)
The name of the accessory.
Accepts all values
​Example: Logitech MX Master

model_number (optional)
The model number.
Accepts all values
​Example: GD481A

order_number (optional)
The order number.
Accepts all values
​Example: XB8119

purchase_date (optional)
The date of purchase.
Format: YYYY-MM-DD
​Example: 2026-01-31

unit_cost (optional)
The unit cost.
Accepts all numerical values
​Example: 4810

currency (optional)
The currency of the purchase price. Only needed if it's different from the default account currency.
Accepts all ISO 4217 three-letter currency codes.
​Example: USD

quantity (required)
The number of items in stock.
Accepts all numerical values
​Example: 30

minimum_quantity (optional)
The minimum quantity of items available before an alert is triggered.
Accepts all numerical values
​Example: 15

category_name (required)
The category of the accessory.
Accepts category names
​Example: Keyboards

supplier_name (optional)
The supplier of the accessory.
Accepts supplier names
​Example: Newegg

manufacturer_name (optional)
The manufacturer of the accessory.
Accepts manufacturer names
​Example: Logitech

location_name (optional)
The location of the accessory.
Accepts location names
​Example: Manhattan Office

department_name (optional)
The department of the accessory.
Accepts department names
​Example: IT Department

notes (optional)
Notes.
Accepts all values
​Example: Remember to ...

remote_accessory_image_url (optional)
The accessory image.
Accepts an HTTPS URL to an image
​Example: https://www.website.com/image.png

Custom Field Name
‍*Custom Field Value*
Create columns named after each custom field you wish to add. Column names become custom field names, and row data becomes field values. By default, new custom fields are text fields. For other custom field types, first manually create the custom field within the app before importing.

checkout_accessory_name (required)
The name of the accessory you want to check out.
Accepts all values
​Example: Magic Keyboard

email_address (required for employee checkouts)
The email address of the employee you'd like to check out the accessory to.
Accepts email addresses of employees already added to the app.
​Example: [email protected]

location_name (required for location checkouts)
The name of the location you'd like to check out the accessory to.
Accepts names of locations already added to the app.
​Example: Sydney

checkout_date (required)
The date of the checkout.
Format: YYYY-MM-DD
​Example: 2026-01-31

expected_checkin_date (optional)
The expected check-in date.
Format: YYYY-MM-DD
​Example: 2026-01-31

checkout_notes (optional)
The notes of the checkout.
Accepts all values
​Example: Forgot his headset at home, short-term loan.

asset_id (required)
The ID tag of the asset.
Accepts all values
​Example: 10000

product_name (required)
The product of the asset.
Accepts product names
​Example: iPhone 13 Pro Max

category_name (required for new products)
The category of the product.
Accepts category names
​Example: Mobile Phones

manufacturer_name (optional for new products)
The manufacturer of the product.
Accepts manufacturer names
​Example: Apple

asset_name (optional)
The name of the asset.
Accepts all values
​Example: The new iPhone

asset_serial (optional)
The serial number of the asset.
Accepts all values
​Example: CBSKS1819181

purchase_date (optional)
The date of purchase.
Format: YYYY-MM-DD
​Example: 2026-01-31

purchase_cost (optional)
The purchase cost.
Accepts all numerical values
​Example: 4810

currency (optional)
The currency of the purchase price. Only needed if it's different from the default account currency.
Accepts all ISO 4217 three-letter currency codes.
​Example: USD

order_number (optional)
The order number.
Accepts all values
​Example: FJD8191

warranty_expiration_date (optional)
The date the warranty of the asset expires
Format: YYYY-MM-DD
​Example: 2026-01-31

end_of_life_date (optional)
The end-of-life date for the asset.
Format: YYYY-MM-DD
​Example: 2026-01-31

status_label (required)
The current status of the asset.
Accepts status label names
​Example: Ready to Deploy

supplier_name (optional)
The supplier of the asset.
Accepts supplier names
​Example: Newegg

location_name (optional)
The location of the asset.
Accepts location names
​Example: Manhattan Office

department_name (optional)
The department of the asset.
Accepts department names
​Example: IT Department

notes (optional)
Notes.
Accepts all values
​Example: Remember to ...

checked_out_to_employee (optional)
The employee the asset should be checked out to.
Accepts the email address of the employee the asset is checked out to. The employee needs to exist in the app before the import.
​Example: [email protected]

checked_out_to_location (optional)
The location the asset should be checked out to.
Accepts the name of the location the asset is checked out to. The location needs to exist in the app before the import.
​Example: New York Office

checkout_date (optional)
Checkout date.
The date the asset was checked out to the employee. Defaults to today's date if empty.
Format: YYYY-MM-DD
​Example: 2026-01-31

expected_checkin_date (optional)
Expected Check-in date.
The date the asset is due back from the employee.
Format: YYYY-MM-DD
​Example: 2026-01-31

checkout_condition (optional)
The condition of the asset upon checkout.
A number from 1-10 describing the condition of the asset when it was checked out to the employee.
​Example: 10

checkout_notes (optional)
Checkout note.
A note related to the checkout of the asset to the employee.
​Example: Remember to ...

Custom Field Name
Custom Field Value
Create columns named after each custom field you wish to add. Column names become custom field names, and row data becomes field values. By default, new custom fields are text fields. For other custom field types, first manually create the custom field within the app before importing.

checkout_asset_id (required)
The ID tag of the asset you'd like to check out. The asset needs to have a Deployable status.
Accepts all values
​Example: 10000

email_address (required for employee checkouts)
The email address of the employee you'd like to check out the asset to.
Accepts email addresses of employees already added to the app.
​Example: [email protected]

location_name (required for location checkouts)
The name of the location you'd like to check out the asset to.
Accepts names of locations already added to the app.
​Example: Sydney

checkout_date (required)
The date of the checkout.
Format: YYYY-MM-DD
​Example: 2026-01-31

expected_checkin_date (optional)
The expected check-in date.
Format: YYYY-MM-DD
​Example: 2026-01-31

checkout_notes (optional)
The notes of the checkout.
Accepts all values
​Example: Forgot his laptop at home, short-term loan.

checkout_condition (optional)
The condition of the asset upon checkout.
Accepts all numerical values between 0 and 10.
‍Example: 8

audit_date (required)
The date of the audit.
Format: YYYY-MM-DD
​Example: 2026-01-31

asset_id (required)
The asset ID that was audited.
Accepts Asset ID's
​Example: 100000

location_name (optional)
The location of the audit.
Accepts location names
​Example: Manhattan Office

notes (optional)
Notes.
Accepts all values
​Example: Remember to ...

audit_completed (required)
If the audit has already been completed
Options: TRUE or FALSE
​Example: FALSE

audit_scheduled (required)
If the audit has been scheduled in the future.
Options: TRUE or FALSE
​Example: TRUE

audit_status (required)
If the audit is pending, failed, or passed. Defaults to PENDING.
Options: PENDING, PASSED, FAILED
​Example: PENDING

audit_failed_reason (optional)
If the audit status has been set to failed, you can add a reason for the audit failure here.
Accepts all values.
​Example: Failed because...

category_name (required)
The name of the category.
Accepts all values
​Example: Mobile Phones

category_type (required)
The category type.
Options: Accessory, Asset, Consumable, Component, or License
​Example: Asset

category_eula (optional)
The End User License Agreement for the category.
Accepts all values
​Example: When you receive this asset, you accept these terms...

skip_checkout_emails (optional)
If you have checkout confirmation emails enabled, you can choose to skip them for all items that belong to this category
Options: TRUE or FALSE
​Example: FALSE

minimum_quantity (optional)
The minimum amount of assets using products belonging to this category that should be in a deployable state before an alert is triggered. Only works for categories of the type Asset.
Accepts all numerical values
​Example: 15

remote_category_image_url (optional)
The category image
Accepts an HTTPS URL to an image
​Example: https://www.website.com/image.png

component_name (required)
The name of the component.
Accepts all values
​Example: Samsung 512GB SSD

serial_number (optional)
The serial number of the component.
Accepts all values
​Example: CBSKS1819181

order_number (optional)
The order number of the component.
Accepts all values
​Example: FDS1231

purchase_date (optional)
The date of purchase.
Format: YYYY-MM-DD
​Example: 2026-01-31

unit_cost (optional)
The unit cost.
Accepts all numerical values
​Example: 4810

currency (optional)
The currency of the purchase price. Only needed if it's different from the default account currency.
Accepts all ISO 4217 three-letter currency codes.
​Example: USD

quantity (required)
The number of items in stock.
Accepts all numerical values
​Example: 30

minimum_quantity (optional)
The minimum quantity of items available before an alert is triggered.
Accepts all numerical values
​Example: 15

category_name (required)
The category of the component.
Accepts category names
​Example: Phones

supplier_name (optional)
The supplier of the component.
Accepts supplier names
​Example: Newegg

manufacturer_name (optional)
The manufacturer of the component.
Accepts manufacturer names
​Example: Samsung

location_name (optional)
The location of the component.
Accepts location names
​Example: Manhattan Office

department_name (optional)
The department of the component.
Accepts department names
​Example: IT Department

notes (optional)
Notes.
Accepts all values
​Example: Remember to ...

remote_component_image_url (optional)
The component image.
Accepts an HTTPS URL to an image
​Example: https://www.website.com/image.png

Custom Field Name
Custom Field Value
Create columns named after each custom field you wish to add. Column names become custom field names, and row data becomes field values. By default, new custom fields are text fields. For other custom field types, first manually create the custom field within the app before importing.

checkout_component_name (required)
The name of the component you want to check out.
Accepts all values
​Example: 1TB SSD

asset_id (required)
The ID of the asset you'd like to check out the component to.
Accepts Asset IDs.
​Example: 100001

checkout_date (required)
The date of the checkout.
Format: YYYY-MM-DD
​Example: 2026-01-31

checkout_notes (optional)
The notes of the checkout.
Accepts all values
​Example: Needs upgraded storage space.

consumable_name (required)
The name of the consumable.
Accepts all values
​Example: Canon GS42 Ink

model_number (optional)
The model number of the consumable.
Accepts all values
​Example: GD231S

order_number (optional)
The order number of the consumable.
Accepts all values
​Example: FDS1231

purchase_date (optional)
The date of purchase.
Format: YYYY-MM-DD
​Example: 2026-01-31

unit_cost (optional)
The unit cost.
Accepts all numerical values
​Example: 4810

currency (optional)
The currency of the purchase price. Only needed if it's different from the default account currency.
Accepts all ISO 4217 three-letter currency codes.
​Example: USD

quantity (required)
The number of items in stock.
Accepts all numerical values
​Example: 30

minimum_quantity (optional)
The minimum quantity of items available before an alert is triggered.
Accepts all numerical values
​Example: 15

category_name (required)
The category of the consumable.
Accepts category names
​Example: Printer Ink

manufacturer_name (optional)
The manufacturer of the consumable.
Accepts manufacturer names
​Example: Canon

supplier_name (optional)
The supplier of the consumable.
Accepts supplier names
​Example: Newegg

location_name (optional)
The location of the consumable.
Accepts location names
​Example: Manhattan Office

department_name (optional)
The department of the consumable.
Accepts department names
​Example: IT Department

notes (optional)
Notes.
Accepts all values
​Example: Remember to ...

remote_consumable_image_url (optional)
The consumable image.
Accepts an HTTPS URL to an image
​Example: https://www.website.com/image.png

Custom Field Name
‍Custom Field Value
Create columns named after each custom field you wish to add. Column names become custom field names, and row data becomes field values. By default, new custom fields are text fields. For other custom field types, first manually create the custom field within the app before importing.

checkout_consumable_name (required)
The name of the consumable you want to check out.
Accepts all values
​Example: Canon 5610 Printer Ink

email_address (required for employee checkouts)
The email address of the employee you'd like to check out the consumable to.
Accepts email addresses of employees already added to the app.
​Example: [email protected]

location_name (required for location checkouts)
The name of the location you'd like to check out the consumable to.
Accepts names of locations already added to the app.
​Example: Sydney

checkout_date (required)
The date of the checkout.
Format: YYYY-MM-DD
​Example: 2026-01-31

checkout_notes (optional)
The notes of the checkout.
Accepts all values
​Example: Needed more printer ink.

department_name (required)
The name of the department.
Accepts all values
​Example: HR Department

department_email (optional)
Department Email.
Accepts all emails
​Example: [email protected]

department_phone (optional)
Department Phone.
Accepts all values
​Example: +12123412123

depreciation_name (required)
The name of the depreciation.
Accepts all values
​Example: Mobile Phone Depreciation

depreciation_number_of_months (required)
The duration of the depreciation in months.
Accepts numerical values
​Example: 36

depreciation_minimum_value_after_depreciation (optional)
The minimum value of the asset after depreciation.
Accepts numerical values
​Example: 1500

employee_name (required)
The name of the employee.
Accepts all values
​Example: John Wilson

employee_title (optional)
The job title of the employee.
Accepts all values
​Example: HR Manager

employee_email (required)
The email of the employee.
Accepts all emails
​Example: [email protected]

location_name (optional)
The location of the employee.
Accepts location names
​Example: Manhattan Office

department_name (optional)
The department of the employee.
Accepts department names
​Example: HR Department

manager_email (optional)
The email address of the employee's manager.
Accepts email addresses of employee entries already added to the system
​Example: [email protected]

notes (optional)
Notes.
Accepts all values
​Example: Remember to ...

Custom Field Name
Custom Field Value
Create columns named after each custom field you wish to add. Column names become custom field names, and row data becomes field values. By default, new custom fields are text fields. For other custom field types, first manually create the custom field within the app before importing.

software_name (required)
The name of the software.
Accepts all values
​Example: Adobe Photoshop

license_type (required)
If it is a Dynamic or Product Key license. Dynamic is for modern SaaS licenses where you have a number of seats that you can allocate to any user (like Microsoft 365), and Product Key is for legacy software where you have individual product keys for every user.
Accepts 'Dynamic' or 'Product Key'.
​Example: Dynamic

licensed_to_name (optional)
The name the software is licensed to.
Accepts all values
​Example: John Peterson

licensed_to_email (optional)
The email the software is licensed to.
Accepts all email
​Example: [email protected]

number_of_seats (optional)
The total number of seats you have for the license. This is for licenses of the type 'Dynamic'. Leave blank for unlimited seats. For 'Product Key'-type licenses, you need to use the License Product Key Template to set the number of seats.
Accepts all numerical values
​Example: 30

minimum_seats (optional)
The minimum quantity of seats available before an alert is triggered.
Accepts all numerical values
​Example: 15

expiration_date (optional)
The expiration date of the license.
Format: YYYY-MM-DD
​Example: 2026-01-31

termination_date (optional)
The termination date of the license.
Format: YYYY-MM-DD
​Example: 2026-01-31

order_number (optional)
The order number of the license.
Accepts all values
​Example: FDS1231

unit_cost (optional)
The unit cost.
Accepts all numerical values
​Example: 4810

billing_interval (optional)

The billing interval of the license.

Accepts 'monthly', 'quarterly', 'annually', or 'one-time'

Example: monthly

renewal_date (optional)

The renewal date of the license.

Format: YYYY-MM-DD

Example: 2026-09-01

auto_renew (optional)

Whether the license auto-renews.

Accepts 'yes' or 'no'. Leave blank for Not Set

Example: yes

renewal_notice_days (optional)

How many days before the renewal date.

Accepts all numerical values

Example: 30

purchase_date (optional)
The date of purchase.
Format: YYYY-MM-DD
​Example: 2026-01-31

currency (optional)
The currency of the purchase price. Only needed if it's different from the default account currency.
Accepts all ISO 4217 three-letter currency codes.
​Example: USD

category_name (required)
The category of the license.
Accepts category names
​Example: Photo Editing Software

manufacturer_name (optional)
The manufacturer of the license.
Accepts manufacturer names
​Example: Adobe

supplier_name (optional)
The supplier of the license.
Accepts supplier names
​Example: Newegg

depreciation_name (optional)
The depreciation of the license.
Accepts depreciation names
​Example: Photo Editing Software Depreciation

location_name (optional)
The location of the license.
Accepts location names
​Example: Manhattan Office

department_name (optional)
The department of the license.
Accepts department names
​Example: Creative Department

notes (optional)
Notes.
Accepts all values
​Example: Remember to ...

remote_license_image_url (optional)
The software license logo.
Accepts an HTTPS URL to an image
​Example: https://www.website.com/image.png

Custom Field Name
‍Custom Field Value
Create columns named after each custom field you wish to add. Column names become custom field names, and row data becomes field values. By default, new custom fields are text fields. For other custom field types, first manually create the custom field within the app before importing.

license_software_name (required)
The name of the software license.
Accepts software license names, as long as it has the Product Key license type.
​Example: Adobe Photoshop

depreciation_minimum_value_after_depreciation (optional)
The minimum value of the asset after depreciation.
Accepts numerical values
​Example: 1500

checkout_license_name (required)
The name of the license you'd like to check out.
Accepts all values
​Example: Adobe Photoshop

product_key (required for 'Product Key'-type licenses)
The product key of the specific license seat you'd like to check out.
Accepts all values
​Example: 1

email_address (required for employee checkouts)
The email address of the employee you'd like to check out the license seat to.
Accepts email addresses of employees already added to the app.
​Example: [email protected]

asset_id (required for asset checkouts)
The ID of the asset you'd like to check out the license seat to.
Accepts Asset IDs.
​Example: 100001

checkout_date (required)
The date of the checkout.
Format: YYYY-MM-DD
​Example: 2026-01-31

expected_checkin_date (optional)
The expected check-in date.
Format: YYYY-MM-DD
​Example: 2026-01-31

checkout_notes (optional)
The notes for the checkout.
Accepts all values
​Example: Short-term checkout

location_name (required)
The name of the location.
Accepts all values
​Example: Manhattan Office

location_address_1 (optional)
Address Line 1.
Accepts all values
​Example: 706 Pacific Street

location_address_2 (optional)
Address Line 2.
Accepts all values
​Example: Cooper Avenue

location_city (optional)
Location City.
Accepts all values
​Example: New York

location_zip (optional)
Location ZIP code.
Accepts all values
​Example: 10011

location_state (optional)
Location State.
Accepts all values
​Example: New York

location_country (optional)
Location Country.
Accepts all countries
​Example: United States

remote_location_image_url (optional)
The location image.
Accepts an HTTPS URL to an image
​Example: https://www.website.com/image.png

location_email (optional)
Location Email.
Accepts all emails
​Example: [email protected]

location_phone (optional)
Location Phone.
Accepts all values
​Example: +12123412123

currency (optional)
The currency used at the location. All items that belong to this location will use this currency.
Accepts all ISO 4217 three-letter currency codes.
​Example: USD

Custom Field Name
‍Custom Field Value
Create columns named after each custom field you wish to add. Column names become custom field names, and row data becomes field values. By default, new custom fields are text fields. For other custom field types, first manually create the custom field within the app before importing.

maintenance_name (required)
The name of the maintenance.
Accepts all values
​Example: Fixed broken screen

maintenance_type (required)
The type of maintenance.
Options: Maintenance, Repair, Upgrade, Test, Calibration, Hardware Support, Software Support
​Example: Repair

asset_id (required)
The asset ID that was audited.
Accepts Asset ID's
​Example: 100000

start_date (required)
The start date of the maintenance.
Format: YYYY-MM-DD
​Example: 2026-01-31

end_date (optional)
The end date of the maintenance.
Format: YYYY-MM-DD
​Example: 2026-01-31

cost (optional)
The cost of the maintenance.
Accepts all numerical values
​Example: 350

supplier_name (optional)
The supplier of the maintenance.
Accepts supplier names
​Example: Newegg

notes (optional)
Notes.
Accepts all values
​Example: Remember to ...

manufacturer_name (required)
The name of the manufacturer.
Accepts all values
​Example: Dell

manufacturer_url (optional)
The link to the manufacturer's website.
Accepts all URLs.
​Example: https://www.dell.com

manufacturer_support_url (optional)
The link to the manufacturer's support page.
Accepts all URLs.
​Example: https://www.dell.com/support

manufacturer_support_phone (optional)
The manufacturer's support phone number.
Accepts all values
​Example: 1-877-DELLTTY

manufacturer_support_email (optional)
The manufacturer's support email.
Accepts all email addresses
​Example: [email protected]

notes (optional)
Notes.
Accepts all values
​Example: Remember to always...

remote_manufacturer_image_url (optional)
The manufacturer logo.
Accepts an HTTPS URL to an image
​Example: https://www.website.com/image.png

product_name (required)
The name of the product.
Accepts all values
​Example: iPhone 13 Pro Max

product_number (optional)
The model number of the product.
Accepts all values
​Example: A1381

end_of_life_type (required)
The end-of-life type.
Options: Fixed Date, Months from Asset Purchase Date, Months from Asset Warranty Expiration Date, Individual Per Asset.
​Example: Fixed Date

end_of_life_date (optional)
The end-of-life date for the product (if end_of_life_type is Fixed Date).
Format: YYYY-MM-DD
​Example: 2026-01-31

end_of_life_months (optional)
Number of months from asset purchase date/warranty expiration date to end of life (if end_of_life_type is Months from Asset Purchase Date or Months from Asset Warranty Expiration Date).
Accepts all numerical values
​Example: 24

default_purchase_cost (optional)
The default purchase cost for all assets using this product.
Accepts all numerical values
​Example: 5000

manufacturer_name (optional)
The manufacturer of the product.
Accepts manufacturer names
​Example: Apple

category_name (required)
The category of the product.
Accepts category names
​Example: Mobile Phones

depreciation_name (optional)
The depreciation of the product.
Accepts depreciation names
​Example: Mobile Phone Depreciation

minimum_quantity (optional)
The minimum number of assets using this product that should be in a deployable state before an alert is triggered.
Accepts all numerical values
​Example: 15

notes (optional)
Notes.
Accepts all values
​Example: Remember to ...

remote_product_image_url (optional)
The product image.
Accepts an HTTPS URL to an image
​Example: https://www.website.com/image.png

Custom Field Name
Custom Field Value
Create columns named after each custom field you wish to add. Column names become custom field names, and row data becomes field values. By default, new custom fields are text fields. For other custom field types, first manually create the custom field within the app before importing.

supplier_name (required)
The name of the supplier.
Accepts all values
​Example: Newegg

supplier_address_1 (optional)
Address Line 1.
Accepts all values
​Example: 706 Pacific Street

supplier_address_2 (optional)
Address Line 2.
Accepts all values
​Example: Cooper Avenue

supplier_city (optional)
Supplier City.
Accepts all values
​Example: New York

supplier_zip (optional)
Supplier ZIP Code.
Accepts all values
​Example: 10011

supplier_state (optional)
Supplier State.
Accepts all values
​Example: New York

supplier_country (optional)
Supplier Country.
Accepts all countries
​Example: United States

supplier_contact_name (optional)
Supplier Contact Name.
Accepts all values
​Example: James Peterson

supplier_contact_phone (optional)
Supplier Contact Phone.
Accepts all values
​Example: +184818191

supplier_contact_fax (optional)
Supplier Contact Fax.
Accepts all values
​Example: +1448653685

supplier_contact_email (optional)
Supplier Contact Email.
Accepts all email addresses
​Example: [email protected]

supplier_url (optional)
Supplier URL.
Accepts all URLs
​Example: https://www.newegg.com

notes (optional)
Notes.
Accepts all values
​Example: Remember to always...

remote_supplier_image_url (optional)
The supplier logo.
Accepts an HTTPS URL to an image
​Example: https://www.website.com/image.png