Strict validation or repair preview for CSV onboarding?

A product tradeoff around strict validation versus flexible repair preview for CSV imports.

For CSV onboarding, strict validation protects the database but may lose users at the first upload. A repair preview can accept messy files, explain guesses, and keep final commit strict. That seems like the useful middle path. Where should a small SaaS draw the line between helpful guessing and dangerous auto-fix?