Account for every removal
The sample session starts with 1,248 rows and removes 48, leaving 1,200. Blank-row cleanup, deduplication and comparison each contribute to that difference.
Keep your cleaning and transformation steps visible. Review changed values, removed rows and applied operations before downloading the final CSV prepared from your CSV or Excel data.
Review your working dataset before export. Illustrative session, not a live file.
| Source row | Column | Before | After | Operation |
|---|---|---|---|---|
| 12 | Company | " Acme Inc. " | Acme Inc. | Trim whitespace |
| 34 | Company | " Northwind " | Northwind | Trim whitespace |
| 12 | JORDAN@EXAMPLE.COM | jordan@example.com | Email casing | |
| 57 | SAM@EXAMPLE.COM | sam@example.com | Email casing | |
| 89 | LEE@EXAMPLE.COM | lee@example.com | Email casing |
5 changed values across 4 retained rows. Customer IDs remain unchanged.
Compare original and cleaned data at a glance. Original rows, current rows, removals, changed values and applied transformations describe different parts of the cleanup. A value change does not necessarily remove a row.
The sample session starts with 1,248 rows and removes 48, leaving 1,200. Blank-row cleanup, deduplication and comparison each contribute to that difference.
Five values changed across four retained rows in the example. One row can contain multiple changed cells. Renaming a column changes its header, not its cell values.
Six transformations describe how the example reached its current state. Review the operation summaries as well as the final totals before exporting.
Track data cleaning changes through readable session steps. Each applied transformation records the operation and its impact, so you can connect the current dataset to the choices that produced it.
This is a data cleaning audit trail for the active session, not a permanently stored cross-session history or a collaborative version-control system.
Review CSV changes in context: the source row, column, previous value, current value and operation responsible. Check the actual difference instead of assuming a successful operation produced the intended result.
Operation: Normalize email casing
Only the casing changed. This does not verify that the mailbox exists. The same row also has a separate Company whitespace change in the example above.
Review removed rows as well as the records left behind. The reason and originating operation help explain why a row is absent from the prepared output.
A record was excluded by the configured matching and keep rules. Check the retained record before accepting the removal.
Every field in the row was blank. This is different from a record with only one missing value.
The row from File A matched the reference file and was excluded by Keep only new records.
Where a row is explicitly excluded by your choice, distinguish that decision from a rule-based removal. This reason is not present in the illustrated session.
Preview Changes and Changes serve different moments. Preview important cleanup or removal operations before confirming them. After applying, use Changes to inspect the resulting values, removed rows and transformation summary.
Review affected-row counts, before-and-after examples and proposed removals. Nothing in that proposal is applied until you confirm it.
Verify the actual working dataset and the new session step. A preview is not a saved transformation; the applied operation is what appears in the history.
Keep control while the workspace session is active. Review, undo or start over without overwriting the file you loaded.
Undo and redo transformations during the active session. To reach an earlier state, undo later steps first. This is not a promise of recovery after closing the session.
Return the working dataset to the originally loaded data when you need to start again. Reset clears the applied session changes; review or export anything you need to retain beforehand.
Cleaning, filtering and resetting operate on the browser workspace. Your source CSV or XLSX file is never modified. A prepared export is a separate file.
Check the final row count, changed values and removed records before CRM or business-system import. Download the prepared dataset as CSV and use your destination system's own import workflow.
CSV and XLSX are supported inputs; the prepared output is CSV, not an edited Excel workbook. Separate changed-row, removed-row and audit-summary exports are Pro features. Reviewing the data helps you verify it, but does not guarantee acceptance by the destination.
Browser-local processing. In local-processing mode, raw dataset contents stay in your browser and are not uploaded to RowDesk servers.
About local processingReview the work between the original file and the final CSV.