Excel Turned My CSV Dates and Zip Codes Into Garbage

2026-10-14

The Call Starts in Ten Minutes

It is Monday, 9:50 am. You are standing at the kitchen counter with a lukewarm coffee and the laptop open on top of the bread bin, because the desk is still covered in last week.

At ten you have a call with a client. Maya runs a small online shop. She sent you a customer export last Friday and asked you to tidy it before her newsletter goes out.

You open the file. Your stomach drops a little.

The zip codes that started with a zero are now four digits long. 01067 has become 1067. The dates, which were all one tidy format in the original, are a mix now. Some say 03/04/2026. Some say 2026-04-03. One just says 46115, which means nothing to a human being.

You did not do anything special. You double-clicked the file. That is all.

The Small Shame of It

You know, somewhere in the back of your head, that this is a known thing. Spreadsheet programs guess. They look at a column, decide what it "must" be, and quietly rewrite it.

Knowing that does not help at 9:52.

What you feel is something smaller and more awkward. You are the person who is supposed to be good with data. And here you are, about to tell a client that her customers' postcodes look broken, and that you are not entirely sure whether it was her export or your opening of it.

Nobody talks about this part. It is not the hours. It is the little wobble in how professional you feel.

What It Quietly Costs

You start fixing things by hand. You format the column as text, but the zeros are already gone, so you retype a few. You try to work out which dates are day-month and which are month-day. Is 03/04 the third of April or the fourth of March? You have no way to be sure without going back to the source.

The call starts. You say, "I'm just finishing a cleanup, give me a minute," in the calm voice you have practised.

Maya is kind about it. She says it is fine, there is no rush. But you can hear a tiny change in her tone. She is now wondering whether the list is safe to send to.

And you are wondering the same thing.

This is how it usually costs you. Not one disaster, but a slow tax on your confidence. An hour here. A second look at every file. A habit of opening exports with a small flinch, the way you check a pan you think might still be hot.

The Moment It Turned

A few days later, you are in the supermarket queue with a basket of tomatoes and a loaf, half-reading a message on your phone. Someone in a developer group you follow has written one flat sentence: the file was never the problem, the way it got opened was.

That is all. Nothing clever.

But it lands. You had been treating every messy export as a personal failing. A thing you should have caught. Standing there with the tomatoes, you see it differently. The file arrived fine. A program made a guess. And the guess can be avoided, or undone, or checked, in a way that does not depend on you being alert at 9:50 on a Monday.

It does not have to be a ritual of dread.

The queue moves. You pay. You walk home a little lighter than you left.

A Different Monday

Picture the same Monday, a few weeks on.

The export arrives. You do not double-click it. You run one small step you set up once, and it reads the file as it is. Zip codes stay as written, zeros included. Dates come out in a single format. Duplicates are flagged rather than silently swallowed, and before anything is changed you can see what would change.

Then you get a short report. It says what was fixed and what was left alone, in plain words. You skim it with your coffee, still hot this time.

At ten, when Maya joins the call, you say, "The list is clean, and I can show you exactly what I changed." You mean it. Your voice does not need practising.

The call is about her autumn campaign instead of about your apologies. Afterwards you close the laptop and the morning still belongs to you.

What Changes, Quietly

Nothing dramatic. You still get messy files. Clients still export things in odd ways, and old systems still produce strange encodings and phone numbers in six styles.

What changes is that a messy file stops being an event. It becomes a small, ordinary job with a visible before and after. The flinch fades. You trust your own work again, and so do the people you do it for.

That is worth more than the hour you save, though you do get the hour back too.

If You Recognised Yourself

If you have ever stared at a column of numbers that used to be dates, or watched a leading zero vanish, you are in good company. It happens to careful people constantly.

We made a small Python toolkit for exactly this kind of morning. It cleans messy CSV and Excel exports: duplicates, dates, phone numbers, encoding, splitting and merging, validation. It does a dry run first and gives you a change report, so you see before you commit. Like every Blixwerk product, it comes with a 30-day money-back promise: if it does not help, you get a full refund, no questions.

If that sounds like the Monday you want, you can have a look here: Clean Data in Minutes – CSV & Excel Cleaning Toolkit (Python)

An illustrative story, written with AI assistance.