Importing Findings from Other Programs

If you're migrating from another inspection program, you can bulk-import your standard findings into Agile Inspections from a CSV file.

Before You Start

Agile Inspections imports a CSV file with a specific set of columns. Because each finding is filed under a trade and subtrade, the trades and subtrades referenced in your file must already exist in your account. Create them first under Settings → Trades and Standard Findings, then import.

Check that you have:

• Your findings in a CSV file (UTF-8 encoded)
• A header row with the required columns (see below)
• Trade and subtrade names that match your existing trades exactly

CSV Format

The first row must be a header row. Columns are matched by name (case-insensitive) and can appear in any order.

Example

Trade,Subtrade,Type,SortOrder,Finding
Structural Systems,Foundations,Deficiency,10,"Visible crack in basement wall"
Roof,Coverings,Comment,20,"Shingles in good condition"

Wrap any finding text that contains commas or line breaks in double quotes, as shown above.

How to Import

1. Go to Settings → Trades and Standard Findings.
2. Click Import Standard Findings.
3. Choose (or drag in) your .csv file and start the import.
4. Review the on-screen summary when it finishes.

The import is additive — it never changes or removes findings you already have. It runs immediately and shows the results inline; there's no email to wait for.

Understanding the Results

After importing, you'll see a summary:

• Added — new findings created.
• Already existed — rows skipped because an identical finding (same subtrade and text) was already in your library. Re-running the same file is safe; duplicates are skipped automatically.
• Skipped — rows that couldn't be imported. Each skipped row is listed with the reason so you can fix your file and re-import.

Troubleshooting

"CSV is missing required column(s)…" The header row is missing one of Trade, Subtrade, Type, or Finding. The whole file is rejected until the header is fixed. Check spelling and that the first row is the header.

A row was skipped: "no subtrade … under trade …" The Trade/Subtrade names in that row don't match an existing trade and subtrade. Names must match exactly (case doesn't matter). Create the missing trade or subtrade first, then re-import.

A row was skipped: Type must be 'Deficiency' or 'Comment' The Type cell contained something else. Set it to Deficiency or Comment.

A row was skipped: SortOrder is not a valid number The SortOrder cell wasn't a whole number. Leave it blank to auto-order, or enter a number.

Findings imported but text looks wrong Make sure finding text containing commas or line breaks is wrapped in double quotes, and that the file is saved as UTF-8.

Migration Tips

1. Set up trades first: import only matches findings to trades and subtrades that already exist.
2. Start small: try a handful of rows to confirm your format before importing everything.
3. Use Export as a template: export your current findings to see the exact column layout, then add to that file.
4. Re-import freely: duplicates are skipped, so it's safe to fix errors and run the file again.

Manual Entry Alternative

If you only have a few findings, you can add them manually instead of importing.

Next Steps

• How to Add Standard Findings
• How to Update Standard Findings
• How to Delete Standard Findings

Need Help?

If you're having issues importing findings, contact our support team — we're happy to help with the migration.