Getting Started
Import Assets and Facility Data
How to prepare imports, avoid messy records, and turn imported data into a usable workspace.
Updated April 19, 2026
Before you import
Imports are most successful when you clean the source data first.
Check for:
- duplicate assets
- blank facility names
- inconsistent locations
- mixed naming patterns
- status values that mean the same thing but use different labels
What to import first
Start with the records that matter operationally:
- 01facilities
- 02critical assets
- 03asset locations
- 04essential metadata that helps identify equipment
Recommended first import pass
- critical mechanical equipment
- electrical distribution equipment
- life-safety assets
- high-cost or high-risk assets
After the import finishes
Always validate the results.
Review:
- asset names
- facility assignments
- locations
- duplicate counts
- empty critical fields
Then open:
- assets
- work board
- preventive maintenance
- dashboard
to make sure the imported records actually support the workflows you expect.
Best practice
Treat import as the start of data stewardship, not the end of setup.
A good imported register is one your team keeps alive:
- new assets get added correctly
- old assets are retired intentionally
- names stay consistent
- work history remains attached to the right equipment
Still need help?
Reach out for broken behavior, account-specific help, or billing questions.