Don't import five years of WhatsApp into HubSpot on day one

There is a question I get in almost every first conversation with a new customer, usually within the first ten minutes. “Can it bring in all my old chats?” The person asking has normally been selling on WhatsApp for years, and they have just realised that none of it is in HubSpot. It feels like a debt, and they want to pay it off in one go.

I understand that feeling completely. But my honest answer has become a gentle no, or at least a “not like that”. The day you start to sync WhatsApp to HubSpot is not the day to dump your entire phone into your CRM. It is the day to start keeping a good record from here on, with just enough of the past to make the present make sense.

A scene from a tyre supplier

The people here are made up, but I have had versions of this call more than once.

Johan supplies tyres to small fleet operators in East London. Taxi owners, a couple of delivery companies, a farmer with more bakkies than sense. Almost all of it runs on WhatsApp. He has chats going back to 2019, hundreds of them, full of price lists, photos of worn treads, “can you do Thursday”, and the occasional message that just says “thanks boss”.

When he installed a WhatsApp HubSpot Chrome extension, his first instinct was to pull every one of those chats into HubSpot. We talked about it for a while, and then I asked him a simpler question. Which customers are you actually talking to this month?

It was about forty. Forty chats where something was still in motion: a quote waiting on approval, a fleet due for a rotation, a new depot that might become an account. Those forty were where the money was. The other few hundred were history in the true sense of the word.

Why bulk importing old chats goes wrong

The first problem is matching. A chat from 2020 belongs to a number, and that number may have changed hands, or belonged to a driver who has since left, or never been a HubSpot contact at all. I have written before about how a WhatsApp chat on the wrong contact is worse than no chat. A bulk import multiplies that risk by a few hundred and hides the mistakes in places nobody will look until they cause trouble.

The second problem is noise. If you log WhatsApp messages in HubSpot for every old conversation at once, the timeline on each contact fills up with things that do not matter anymore. A rep opening a record should see the story of the relationship, and five-year-old “thanks boss” messages are not the story. The useful bits get buried under the volume.

The third problem is quieter, and it is about trust. People share a lot on WhatsApp that was never meant for a company system. A personal chat with a customer who became a friend. A voice note about a family situation. When you bring things in chat by chat, someone makes a decision each time. When you bring everything in with one button, nobody decides anything, and that is how a CRM ends up holding things it should not.

What I think the first week should look like

My suggestion to Johan, and to most people, is fairly plain.

Start with the live deals. Pick the chats where something is happening now, and bring those into HubSpot first. For each of them, include enough HubSpot WhatsApp conversation history to understand where things stand, which usually means the recent stretch of the chat, not the whole thing. The last quote, the last objection, the last promise somebody made.

Then let the sync carry on from there. Every new message lands on the right contact with its original time, and within a few weeks the CRM reflects how you actually sell today. Older customers come back into the picture naturally when they message again, and that is the right moment to decide whether their history is worth bringing across.

And leave the rest where it is. Your old chats are not going anywhere. They are still in WhatsApp if you ever need to scroll back.

A small market note

Some tools sell the big import as a headline feature, and I can see why. It makes a great demo. You install something, press a button, and suddenly HubSpot looks full. But a full CRM and a useful CRM are different things, and I have yet to meet a sales manager who wished their contact timelines were longer and messier. I would rather a HubSpot WhatsApp sync was judged on whether the record is right in three months than on how much it swallowed in the first hour.

The opinion

The guilt about all those unlogged years is understandable, but it is not a good reason to make a mess. Treat the day you connect WhatsApp to HubSpot as a starting line, not a clean-up job. Bring in the deals that are alive, give them enough context to be understood, and let the past stay in WhatsApp until it earns its way back in.