Run, review, and clean up imports
Use optional Import steps, interpret processing results, recover from failures, and remove history safely.
This guide helps you choose the optional Entity behavior, follow a run to completion, and separate Import history cleanup from changes already written to the destination.
Before you begin
You need:
- a mapped Import draft in the approved organization;
- the source CSV and the intended destination available for comparison;
- an approved conflict policy for rows that can match existing records;
- a safe validation sample for checking the destination after processing.
Do not use the workflow to probe another organization’s records or capabilities. Permission and destination-access rules remain under verification.
Configure optional Entity steps
- Complete Select database table, Upload CSV data, and Map columns.
- When Enrich data appears, select Enrich from column, choose the Value type, and select the Fields to enrich.
- Choose the approved enrichment behavior: Don’t use, Fill if empty, Overwrite, or Add to existing where available.
- On Conflict strategy, choose the approved outcome for matching records: Add only new records (skip existing), Fill in blank fields only, or Overwrite existing values.
- Continue to Review and import and verify the mapping and Import name before starting.
Enrich data and Conflict strategy are optional and only appear when the selected destination supports them. Do not expect those pages for every target.
Monitor and review a run
- Open the Import from the history page.
- Read the status as a lifecycle: a draft or queued run is Pending, the worker changes it to Processing when an attempt begins, and that attempt reports Completed or Failed.
- While it is Processing, leave the detail page open if you want the displayed state to refresh automatically.
- When it is Completed, review Total records, Processed records, Failed records, Updated records, Skipped records, and Error details.
- Interpret Success rate as processed rows that did not error. It can count inserts, updates, matched-but-unchanged rows, and skips; it is not an inserted-record percentage.
- Validate a representative sample in the destination, including created, changed, unchanged, and skipped cases that matter to your workflow.
A Completed status means the run finished; it can still include failed rows. A Failed status represents a run-level failure, but the background worker can make up to three total attempts. Do not treat Failed as permission to start a duplicate run until support confirms that no attempt remains. In either case, use the visible counts and errors rather than the status alone.
Remove Import history
- Open the Import detail page and preserve any error details or counts your audit process requires.
- Validate the destination rows and decide separately whether they need correction.
- Select Delete and read the confirmation.
- Confirm only when you intend to remove the Import record and its history.
Deleting history does not delete destination rows or entries already created by the import. It is not an undo action.
Success check
The reviewed run has a final status, reconciled counts, documented row errors, and a destination sample that matches the approved mapping and conflict behavior. If history was deleted, the Import no longer appears in the list while its previously created destination records remain.
Troubleshooting
- Completed includes failed records. Inspect Error details, correct the affected source rows, and use a new import for the corrected data.
- Failed has no Retry control. The product has no generic user-facing retry for a failed Import record. Preserve the visible error, have support confirm that no background attempt remains, and reconcile destination records and any other persisted changes across attempts before starting a replacement import.
- A matched record was not overwritten. Confirm the selected Conflict strategy and the destination’s matching fields before running a corrected import.
- Deleting history did not remove created rows. This is expected. Correct or remove destination data through the destination’s approved workflow, not by deleting Import history.