Bulk Importing Assets from CSV

AccuArk's bulk import tool lets you create many assets at once by uploading a CSV (comma-separated values) file. This is significantly faster than entering assets one at a time through the acquisition wizard, and is the recommended approach for initial system setup, batch acquisitions, and migrations from other systems.

When to Use Bulk Import

Bulk import is ideal for these scenarios:

• Initial system setup — When you first deploy AccuArk and need to load your existing asset inventory into the system.
• Acquiring a batch of assets — When your organization purchases multiple assets at once (e.g., 50 laptops for a new office) and you want to register them all simultaneously.
• Migrating from another system — When transitioning from a spreadsheet, another asset management tool, or an ERP system that can export to CSV.
• Periodic reconciliation — When you have an external list of assets (e.g., from a vendor shipment manifest) that need to be added to the register.

How to Access

Navigate to Assets > Import Assets from the main menu bar. This opens the the Import screen form.

Required Permission

You must have the Asset Admin permission to access the Import Assets screen. If you do not see the Import Assets option under the Assets menu, contact your administrator to verify your role includes this permission.

Preparing Your CSV File

Before importing, prepare your CSV file according to the following specifications.

File Format Requirements

• Encoding: UTF-8 (this ensures special characters like accented letters and currency symbols are preserved)
• Delimiter: Comma (standard CSV format)
• First row: Must contain column headers (the header names are used during column mapping)
• Text qualifier: Use double quotes around values that contain commas (e.g., "Conference Room A, Floor 2")

Required Columns

The following columns must be present in your CSV file. The import will fail validation if any of these are missing or empty for a given row.

Category and location names are matched against your existing records. If a CSV row contains a category or location name that does not exist in AccuArk, that row will fail validation.

Recommended Columns

These columns are not required but are strongly recommended for complete and accurate asset records:

If depreciation columns are omitted, the asset inherits depreciation settings from its category or the module defaults.

Optional Columns

Include any of these columns as needed:

Columns not listed above are ignored during import. You can include extra columns in your CSV for your own reference — the mapping step lets you skip them.

Loading the File

Click the Browse button on the import form to open a file selection dialog. Navigate to and select your CSV file. The system reads the file and displays the column headers found in the first row.

If the file cannot be read (wrong encoding, corrupted file, or not a valid CSV), an error message explains the issue.

Column Mapping

After loading the file, the Column Mapping screen appears. This screen shows each column header found in your CSV file alongside a dropdown where you select the corresponding AccuArk field.

How Mapping Works

For each CSV column, select the AccuArk field it corresponds to from the dropdown. If a CSV column does not map to any AccuArk field (e.g., an internal reference number you do not need in AccuArk), select Skip from the dropdown.

The system attempts to auto-map columns based on common header names. For example, a CSV column named "Asset Name" or "Name" is automatically mapped to the Asset Name field. Review the auto-mappings and correct any that are wrong.

Required Mapping

The three required fields (Asset Name, Category, Location) must each be mapped to a CSV column. The Validate button is disabled until all required mappings are complete.

Mapping Tips

• Use clear, descriptive column headers in your CSV to help the auto-mapper
• If your CSV has separate First Name and Last Name columns for employees, you may need to combine them into a single column before import
• Date columns must be in YYYY-MM-DD format (e.g., 2026-01-15). Other date formats will cause validation errors.
• Numeric columns (costs, useful life) should contain numbers only — no currency symbols, commas, or text

Validation

Click the Validate button to check all rows in the CSV against AccuArk's data rules. Validation runs through every row and reports issues in two categories:

Errors (Will Not Import)

Rows with errors are rejected and will not be imported. Common errors include:

• Missing required field — Asset Name, Category, or Location is blank for the row
• Invalid category name — The category in the CSV does not match any existing category in AccuArk (names are case-sensitive)
• Invalid location name — The location in the CSV does not match any existing location in AccuArk (names are case-sensitive)
• Duplicate asset number — If your CSV includes an Asset Number column and two rows have the same number, or the number already exists in the system
• Invalid date format — A date column contains a value that is not in YYYY-MM-DD format
• Invalid numeric value — A cost or numeric column contains non-numeric characters

Warnings (Will Import, May Need Attention)

Rows with warnings can still be imported but may require follow-up:

• Missing optional fields — Recommended columns like Purchase Cost or Acquisition Date are blank
• Unusual values — A cost that is zero or negative, a useful life that is unusually short or long
• No depreciation settings — Neither the row nor the category specifies depreciation method or useful life (module defaults will be used)

Fixing Errors

If validation reports errors, you have two options:

1. Fix the CSV — Open the CSV in a spreadsheet application, correct the errors, save, and re-load the file in AccuArk.
2. Skip problematic rows — Proceed with the import and only the valid rows will be created. Error rows are skipped and listed in the import summary.

Preview

After validation, the Preview screen shows all rows that passed validation in a grid. Review this data carefully before importing:

• Verify that the correct columns were mapped to the correct fields
• Spot-check several rows to confirm names, categories, locations, and costs are correct
• Check the row count — does it match the number of assets you expect to import?

The preview is your last chance to catch issues before data is written to the database.

Executing the Import

Click the Import button to create all validated assets. The import process:

1. Creates each asset record in the database
2. Assigns an auto-generated asset number to each asset (based on the numbering format in Asset Settings)
3. Applies depreciation settings from the CSV, category defaults, or module defaults (in that priority order)
4. Calculates the total capitalized cost (purchase cost + shipping + installation + other costs)
5. Logs each asset creation to the activity log with the source marked as "CSV Import"
6. Associates each asset with the specified location

A progress bar shows the import progress. For large files (hundreds or thousands of rows), the import may take several minutes.

After the Import

When the import completes, the Import Summary screen displays:

If any rows were skipped, a downloadable error report lists each skipped row with the specific error that caused it to fail. This report can be used to fix the CSV and re-import the remaining rows.

Verification Steps

After importing, perform these verification steps:

1. Check the Asset Register — Navigate to Assets > Asset Register and verify that the imported assets appear with correct names, categories, locations, and costs.
2. Spot-check depreciation — Open a few imported assets and verify that depreciation method, useful life, and salvage value are set correctly.
3. Verify asset numbers — Confirm that auto-generated asset numbers follow the expected format.
4. Check totals — Compare the total purchase cost of imported assets against your source data to verify financial accuracy.

Tips and Recommendations

• Start with a small test batch. Import 5-10 rows first to verify that your column mapping, category names, and location names are correct. Once confirmed, import the full file.
• Ensure category and location names match exactly. Names are case-sensitive. "IT Equipment" and "it equipment" are treated as different categories. Copy names directly from AccuArk to avoid mismatches.
• Include acquisition dates for accurate depreciation. Without an acquisition date, the system uses the import date, which may produce incorrect depreciation calculations for assets acquired in the past.
• Export a sample asset to CSV first. If you are unsure about the expected format, create one asset manually through the acquisition wizard, then export it. Use that export as a template for your import file.
• Remove blank rows from your CSV. Spreadsheet applications sometimes add empty rows at the end of a file. These will cause validation errors for missing required fields.
• Back up before large imports. While the import does not modify existing data, creating a database backup before importing hundreds of assets is a prudent precaution.
• Use consistent naming conventions. Standardize how you name assets in the CSV (e.g., always "Dell Latitude 5540" not sometimes "Latitude 5540" and sometimes "Dell 5540 Laptop"). Consistent names make searching and reporting more effective.
• Do not include currency symbols in cost columns. Enter 1250.00, not $1,250.00. Currency symbols and thousand separators will cause validation errors.

Related Articles

• Adding a New Asset
• Asset Numbering Formats
• Asset Categories Setup
• Asset Settings & Configuration
• Asset Register & Search