Migration guide
Bring your inspection template, then verify the result
Hometrace accepts Spectora template exports in .xls or .xlsx format, Home Inspector Pro template bundles in .tpz format, and templates arranged in the documented Hometrace CSV format. Every import should be previewed, saved, and reviewed before it is used for client work.
Who it is for
For inspectors moving an established reporting workflow
Template imports reduce rebuilding for inspectors who already have sections, specs, comments, and standard findings. They are a migration starting point, not a guarantee that tool-specific behavior will map exactly.
Spectora exports
Upload an .xls or .xlsx template export to bring over the supported section and spec hierarchy and comment options.
Home Inspector Pro bundles
Upload a .tpz template bundle to bring over supported section structure, the comment library, and inspection logic.
Documented CSV format
For other tools, arrange the template in Hometrace CSV format using the sample available on the import screen.
How it works
Import, inspect, test, then adopt
A deliberate validation pass protects the reporting language and structure that an inspection business already depends on.
Export or prepare the file
Create the supported file from Spectora or Home Inspector Pro, or prepare a CSV using the Hometrace template format.
Upload and preview
Choose the import source on the Templates page, upload the file, and inspect the preview before saving.
Review the saved template
Check sections, specs, comment options, default findings, and any logic or calculations that mattered in the previous tool.
Complete a test inspection
Use the imported template through field capture, report review, and delivery before switching the daily workflow.
What to know
Tool-specific behavior may need manual work
The importers map supported template content into Hometrace. They do not promise that every proprietary automation, calculation, media annotation, or custom behavior from another product will transfer.
- Spectora custom calculations may need to be re-entered after import.
- Home Inspector Pro photo annotations and tool-specific automations require a manual review.
- Files from other tools must use the documented CSV layout unless Hometrace support handles the migration.
- The inspector should verify the rendered report, not only the template editor.
Product evidence
Use the import and first-report checklists
The current documentation names supported formats, explains the preview, records known translation limits, and shows how the template enters an inspection.
Keep evaluating