Bring your customer, site and asset records into one service directory.

Moving asset data should not begin with hidden assumptions.

A clear template and visible validation step help the team identify missing customer, site or asset information before it enters the working service directory.

Prepare, review and import a standard data set.

The import follows one maintained structure for customer, site and asset records rather than accepting an undefined spreadsheet layout.

• Use the standard CSV template. Place customer, site and asset details into the documented columns and stable external references.
• Preview and validate the rows. Check row-level issues and relationships before committing records to the service directory.
• Create the accepted records. Import validated customers, sites and assets while keeping their hierarchy intact.

A three-row import preview with linked records.

This controlled CSV sample uses fictional onboarding data. It demonstrates the standard import structure and does not represent a completed customer migration.

• Template: ilarvo standard customer-site-asset CSV
• Record types: Customer, site and asset
• Review step: Preview and row validation
• Import scope: Accepted standard records
• Atlas Property: External reference CUST-ATLAS.
• Atlas House: Linked to CUST-ATLAS.
• Air Handler 04: Linked to Atlas House with serial AHU-04018.

Prepare a focused first import for one service workflow.

The service manager selects a representative customer, its sites and maintained assets, checks the preview and corrects validation issues before import.

• Stable external references keep related rows clear.
• The preview shows issues before records enter the directory.
• Accepted records preserve the customer, site and asset hierarchy.

A standard import with explicit limits.

The current import is designed for the documented customer, site and asset template.

• The source file must follow the standard columns and relationships.
• Validation identifies issues but does not reinterpret an unrelated source schema.
• Operational history is created through completed work, not invented during import.

Frequently asked questions

Answers about this ilarvo workflow and its current product boundary.

• What records can the standard CSV import create? The current template supports customer, site and asset records and preserves the relationships between them.
• Can I review errors before importing? Yes. The preview and validation step identifies row issues before accepted records are committed.
• Can any spreadsheet layout be imported as it is? No. Source data must be prepared in the documented standard template before the current import workflow can validate it.