Why it matters
The first useful result may depend on bringing data from a spreadsheet or another product. A self-service importer must make errors understandable before it changes production records.
Import is an asynchronous, repeatable workflow: upload, map columns, preview validation, apply and reconcile. Customers need a way to correct only the failed rows.
Decisions to make
- Choose supported source formats and maximum import size.
- Define matching and duplicate rules for existing records.
- Decide whether an import can be rolled back or replayed.
- Set how references between records are mapped.
- Plan where sensitive import files are stored and when they expire.
Build checklist
- Provide a dry-run preview with field mapping and sample rows.
- Validate each row and produce an actionable error report.
- Run large imports in resumable background batches.
- Make retries idempotent to prevent duplicate records.
- Show progress, totals and a post-import reconciliation summary.
Common mistakes
- Accepting a file and returning only a generic failed status.
- Inserting half the rows without telling the customer which ones succeeded.
- Using filename or row order as the only duplicate key.
Tools & references
3 starting points to compare or study. Check fit, maintenance, terms and current capabilities before choosing one.