Tools Hub

Clean a messy data export before import

Repair a badly exported table in the browser: split ragged lines into columns, switch the delimiter and inspect the result before importing it anywhere.

Browser onlyYour data never leaves this device.

Every tool named on this page runs in your browser; nothing you paste or open is uploaded.

Details: Privacy policy

Draft job page — noindex and awaiting human review before publication.

Formats this job covers

  • csv

Tools used in this job

  • Text to CSV — Turn plain pasted lines into structured CSV rows and columns.
  • CSV Delimiter Converter — Switch CSV files between comma, semicolon, tab, and pipe delimiters.
  • CSV Viewer — Browse huge CSV files as a fast table with filter and export.

Exports from ticketing systems, time trackers and older finance packages rarely arrive in the shape an importer wants. Rows may be glued together with semicolons, a header may sit on the wrong line, or a column of reference codes may have lost its leading zeros somewhere along the way. This job is the repair routine: turn the raw block into columns, choose the separator the target system expects, then look at the first and last rows before anyone imports the file. Checking beats hoping, because a silent mis-split is far more expensive than a minute of inspection. Everything is parsed locally, so customer names, salaries and order references never leave the machine you are working on, and you can keep re-splitting until the table reads correctly. A quick suspicion test saves an import window. Count the rows in a spreadsheet, then count them again in the repaired preview; a mismatch usually means an embedded newline split one record in two or a stray quotation mark swallowed several lines. Look for a header that appears twice, which happens when an exporter concatenates several monthly files, and for a trailing total row that an importer will treat as data. Confirm the encoding before anything else, because a Latin-1 export read as modern text produces mangled names that look like corruption but are merely mislabelled. Keep the repair reproducible by writing down the delimiter, quote style and header row you settled on. Import a small sample before the whole set, so a mistake costs seconds rather than a rebuild. Dates and currencies are the quiet casualties of a careless repair. A column that mixes day-first and month-first formats will import without complaint and produce nonsense downstream, so standardise the order before handing the file on. Currency symbols embedded in a number field break arithmetic, and thousand separators vary by locale; decide the target convention and apply it deliberately. Record those decisions in a short note beside the file, and keep the untouched original so a disputed value can be checked against the raw export.

How to use Clean a messy data export before import

  1. Paste the raw block or open the file and look at how the fields are separated.
  2. Convert the text into a table and confirm the header line landed in row one.
  3. Switch the delimiter if the importing system expects tabs, semicolons or pipes.
  4. Compare the first and last rows with the source to prove nothing shifted.

What you get

  • Very large tables are browsed as a capped, virtualised view rather than loaded whole.
  • Cells that begin with a formula character are escaped so a spreadsheet cannot execute them.

When to use Clean a messy data export before import

  • Feed a semicolon export into a tool that only accepts commas.
  • Turn a pasted block of fixed columns into a table a spreadsheet can open.
  • Check a suspicious export for missing or duplicated rows before an import window.

Frequently asked questions about Clean a messy data export before import

Will my reference codes keep their leading zeros?

Yes. Values are treated as text, so codes such as 00417 survive the split rather than being retyped as numbers.

What if the wrong delimiter is chosen?

The preview shows the damage immediately: everything collapses into one wide column. Switch the separator and the rows separate again.

Is my exported data uploaded?

No. Splitting and previewing happen in your browser, and no row is stored or reused after the tab closes.

Can this repair a file with a broken header row?

Partly. A missing header must be written by hand, but misplaced or duplicated rows become visible the moment the table is previewed.

Feedback

Send feedback about this tool (placeholder — feedback collection is not wired up yet).