CSV File Keeps Breaking My Import? The Tide Table

2026-11-01

The import tool says it again, in the same polite red text: "Import failed. Row 1,482 could not be read."

It is 8:20 on a Monday morning. You are sitting in your car on the seafront, because the Wi-Fi in the holiday flat you rented for a long weekend is, to put it kindly, decorative. Your laptop is balanced on the steering wheel. A thermos of tea is wedged between the seats. Outside, the tide is out and the beach looks like it has been left unfinished.

The client's shop opens its new booking system at noon. The customer list has to be inside it by then. Three hundred names, emails, phone numbers, last visit dates. Simple. You said "simple" on the call on Friday.

The fourth try

You open the file. Row 1,482 looks fine. You stare at it anyway, the way you stare at a fridge you already checked.

So you fix something. A stray quote, maybe. You save, upload, wait. The progress bar creeps along, and then the red text again, only now it says row 1,611.

This is the part nobody warns you about. The file is not broken in one place. It is broken a little bit everywhere, and each fix only shows you the next problem. Like walking along the shore and finding that every rock you step over has another rock behind it.

Your tea goes cold. You do the maths you always do in these moments: If I find it by ten, I'm fine. If I find it by eleven, I'm tight. If I'm still at it at half past eleven, I will have to write a message I really don't want to write.

What it quietly costs

It is not only the time. It is the small hot feeling in your chest that says you should be better at this. That a proper professional would have a clean file by now. That the client trusted you with their customers' details and you are sitting in a parked car squinting at commas.

You notice you are not even enjoying the view. You booked this weekend to breathe, and instead you spent Saturday half-listening to your phone and Sunday night wondering if the export would behave.

It did not behave. The names have odd little symbols where the accents should be. Some dates read day-month, others month-day, and a few say nothing at all. A phone number starts with a plus in one row and a bracket in the next. Someone, at some point, typed an email address with a space in the middle.

None of it is dramatic. That is exactly why it eats a morning.

The other way to stand at this problem

A text arrives from a friend who works in operations for a ferry company. She has no idea what you are doing. She just sends a photo of the harbour tide table with the words "Low tide at 11:40. Do not be late."

You look at the photo for a while.

A tide table is not exciting. It is a page where somebody decided, once, that the sea should be predictable, so nobody has to stand on the pier guessing. Nobody argues with it. Nobody refreshes it hoping it will change its mind.

And you think: why am I treating this file like weather?

You have cleaned files like this before. Each time, you did it by hand and by mood, and each time you promised yourself you would never do it that way again. Then the next export arrived and the promise got lost somewhere between a deadline and a cup of tea.

What if cleaning a file was boring in the same way a tide table is boring? Something you run, glance at, and trust. Something that shows you what it would change before it changes anything, and leaves you a plain list of what it did, so you are never wondering what happened to row 1,482.

That thought alone loosens your shoulders a little.

Noon, but calmer

Imagine the same Monday with that in place.

You open the export at 8:20. You run it. You read a short report: dates sorted out, duplicates flagged, phone numbers in one shape, the odd symbols repaired, three rows that genuinely need a human look. You look at those three rows. One is a typo you can fix in ten seconds. One you ask the client about. One you leave out and note down.

The import goes through on the first try. You watch the bar fill, and it feels almost rude how uneventful it is.

Then you get out of the car. You walk to the end of the pier with the thermos, and the tea is still warm because you actually drank it. The client's shop opens at noon and you are not refreshing anything. Your phone stays in your pocket. The sea, as promised, is going out.

That is the whole difference. Not a miracle. Just a Monday where the file is a task, not a verdict on you.

If you recognise yourself in the car

If you have ever lost a morning (or a holiday) to a file that would not behave, you are not careless and you are not behind. Messy exports are simply how data tends to arrive. The only real question is whether you want to meet every one of them from scratch.

We built the Clean Data in Minutes – CSV & Excel Cleaning Toolkit (Python) for exactly that. It cleans messy CSV and Excel exports: duplicates, dates, phone numbers, encoding, splitting and merging, and validation. It starts with a dry run and gives you a change report, so you always see what happened. It comes with our 30-day money-back promise: if it doesn't help, you get a full refund, no questions.

No rush. The tide comes back whether you click or not.

An illustrative story, written with AI assistance.