Will reimporting a Housecall Pro price book create duplicates?

Why duplicate risk is a matching problem

A reimport is safe only if the destination can interpret the incoming rows the way you expect. If identifiers or source structure changed during editing, a row that looked like an update in Excel may not behave like one in the import workflow.

Preserve identifiers from the original export

Housecall Pro exports can include UUID fields and other source columns. Do not remove unfamiliar identifiers simply to make the spreadsheet look cleaner. Preserving the original data gives you more context for comparison and reconciliation.

Do not rely on one field as a guarantee

Import behavior can change and may depend on the current Housecall Pro workflow. Treat UUID and other identifiers as important source data, not as a promise that the system will always update instead of create.

Compare the edited file before upload

Check whether identifiers disappeared, rows were added, or source columns were removed. ImportFix can surface those differences in the browser local Change Audit.

Use a small test import

A limited test is the safest way to verify what Housecall Pro does with your specific file and account before you apply a large reimport.

FAQ

Does keeping UUID guarantee no duplicates?

No. Preserve identifiers, but verify the current import behavior and use a small test instead of relying on an unverified guarantee.

Should I delete old identifiers before reimporting?

Not by default. If the identifiers came from the original export, preserving them is the conservative choice unless current Housecall Pro guidance says otherwise for your workflow.

Can ImportFix remove duplicates automatically?

ImportFix surfaces duplicate and identifier related issues for review. It does not guess which business record should be deleted or merged.