Importing Findings from Other Programs

If you're migrating from another inspection software, learn how to import your existing findings into Agile Inspections.

Before You Start

Check that you have:

• Your findings exported from the previous software
• Findings in a supported format (CSV, Excel, or other)
• Administrator access in Agile Inspections
• All necessary information about your findings

Supported Import Formats

Agile Inspections typically supports:

• CSV (Comma-Separated Values)
• Excel (.xlsx, .xls)
• JSON
• XML

Step 1: Export Findings from Previous Software

Export your findings from your current software following their process:

1. Access findings library or database
2. Select "Export" option
3. Choose supported format
4. Save file to your computer

Required Finding Fields:

• Title/Name
• Description
• Recommendation
• Category
• Severity (if available)

Step 2: Prepare Import File

Ensure your file contains:

• Consistent formatting
• No duplicate entries (optional cleanup)
• All data in correct columns
• Proper encoding (UTF-8 recommended)

CSV Format Example:

Title,Description,Category,Severity,Recommendation
Cracked Foundation,"Visible crack in basement wall",Foundation,Major,"Hire structural engineer"
Roof Damage,"Multiple missing shingles",Roof,Major,"Complete roof inspection needed"

Step 3: Access Import Function

In Agile Inspections:

1. Navigate to Settings → Standard Findings
2. Look for "Import" or "Import Findings" button
3. Or go to Admin → Findings Management → Import

Step 4: Select File

Click "Choose File" or "Browse":

• Locate your exported findings file
• Verify filename and format
• Click to select

Step 5: Map Fields

Match fields from your file to Agile Inspections fields:

• Your file's "Title" → Agile Inspections "Finding Title"
• Your file's "Issue" → Agile Inspections "Description"
• Etc.

This ensures data imports to correct locations.

Step 6: Review Import Preview

Most systems show a preview:

• Review sample findings from your import
• Verify data looks correct
• Confirm field mapping is accurate
• Check for any warnings or errors

Step 7: Complete Import

Click "Import" or "Complete":

• System processes your findings
• Creates new findings in your library
• Reports any import errors
• Shows import summary

Step 8: Verify and Cleanup

After import:

1. Review findings for accuracy
2. Check for any formatting issues
3. Test using findings in an inspection
4. Delete duplicates if any were created
5. Organize into categories as needed

Troubleshooting Import Issues

Import shows errors:

• Check file format is correct
• Verify required fields are present
• Look for special characters causing issues
• Try with smaller sample file first

Fields didn't map correctly:

• Re-run import with correct field mapping
• Consider manual correction of wrong entries
• Delete incorrectly imported findings if needed

Some findings didn't import:

• Review error report for specific findings
• Check if those findings have missing required data
• Manually add any findings that failed

Duplicate findings created:

• Review imported vs. existing findings
• Delete obvious duplicates
• Check if system has "merge" functionality

Migration Tips

1. Start small: Test with subset of findings first
2. Verify accuracy: Check imported findings carefully
3. Update as needed: Refine during import process
4. Organize: Establish clear categorization
5. Document changes: Note any modifications made
6. Train team: Ensure everyone knows new locations
7. Keep backup: Maintain copy of original export

Manual Entry Alternative

If import isn't working:

• Create findings manually through the interface
• Use batch creation if available
• Take time to properly categorize while entering

Next Steps

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

Need Help?

If you're having issues with importing findings, contact our support team - we can assist with the migration process.