How to Import Fleet Data from Excel to HVI: Migration Guide

HVI accepts CSV (Comma-Separated Values) as the standard bulk import format, with UTF-8 encoding recommended to handle special characters like accented letters, symbols, and non-English text without corruption. Excel spreadsheets (.xlsx, .xls) should be saved as CSV UTF-8 before uploading — in Excel that's File → Save As → "CSV UTF-8 (Comma delimited)". Google Sheets and Apple Numbers can export CSV directly. The reason CSV is the standard: it's a flat, universally-parseable format that avoids the version-specific quirks Excel introduces (merged cells, formulas that evaluate differently across versions, hidden columns). If your data is in a different fleet system today, most platforms can export to CSV directly — you rarely need to touch Excel in between.

Industry standard practice is to cap CSV imports at approximately 500 rows per file to prevent timeout errors and to make validation manageable. Fleets larger than 500 assets should split into multiple files — a 1,200-truck fleet might do three imports of 400 assets each. This isn't a technical hard limit so much as a practical one: smaller files import faster, validate more clearly, and if something goes wrong the fix is easier to scope. HVI's saved column map feature means the second, third, and fourth imports from the same source file format take under a minute each — you don't re-map every time. For very large migrations (5,000+ assets), most HVI customers work with our onboarding team to script the import in phases rather than uploading a single massive file.

Vehicle records and maintenance history are two separate imports in HVI — and this is the right structure, not a limitation. Vehicles come in first (the required 6-field asset creation import). Maintenance history, work orders, and past PM records come in as a second import once the vehicles exist, because each historical record has to link to a vehicle by VIN. If your Excel sheet has "last oil change date" as a column on the vehicle row, that comes in with the vehicle. But a full year of work-order history — every service, every part, every labor hour — belongs in a separate work-order CSV that references the imported vehicles by VIN. Most fleets bring in current vehicle state on day one and layer historical maintenance data over the following 2–4 weeks; some skip historical import entirely and start fresh, which is a perfectly valid choice for fleets whose past records were unreliable anyway.

HVI's validator runs before any data is written to your account — not during. That means an error on row 47 doesn't leave rows 1–46 partially imported. The validator flags every issue inline (row number, column, what's wrong, suggested fix) and gives you the choice: fix in the browser preview and re-run, or bounce back to Excel, fix the source file, and re-upload. Common auto-caught errors include: VIN not 17 characters, VIN contains invalid characters (I, O, Q), duplicate VIN in the file, duplicate VIN vs existing HVI records, required field blank, date in unparseable format, asset type not in the allowed values list. Nothing writes to your live fleet until the file passes validation clean. This is the fundamental difference between a bulk-import tool and a raw database dump — the validation prevents the "we imported 400 records and now half are broken" scenario.

Yes — and this is how most fleets keep their HVI records in sync when they still maintain some data in Excel during transition. HVI uses VIN as the unique matching key on import. If an incoming row's VIN already exists in HVI, the row is treated as an update to the existing asset rather than a new record. Fields you include in the CSV get overwritten with the new values; fields not in the CSV stay as-is. This means you can push a monthly odometer update via CSV (just VIN + odometer_reading columns) without disturbing any other field on the asset. It's also how fleets migrate progressively — import minimum required fields on day one, add optional fields over the next few weeks through incremental updates. Just be careful: an update import overwrites, so make sure the incoming values are current before uploading.