A European company arriving in China brings the CRM it already runs at home, because that is the sensible thing to do: one tool, one database, one way of reporting. Within a season the Chinese part of it is a shell. The companies are there, the contacts are there, and nothing has been written since the first weeks. The usual explanation is that the local team does not like filling in forms, which is true of every sales team in the world and explains nothing. The real reason is structural: the exchange with the customer never passed through anything the tool could read.
Where the relationship actually lives
In China a commercial relationship lives inside a messaging thread. The first contact, the request for a quotation, the drawing, the counter-proposal, the question asked on a Sunday evening, the agreement — all of it in one thread, much of it in voice messages, on a telephone that belongs to a salesperson rather than to a company. Nobody is hiding anything. That is simply the channel a Chinese professional uses, in the same way a European one uses an inbox, and asking them to duplicate each exchange into a form afterwards is asking for an hour a day that nobody has.
The consequence is the one a CRM was invented to prevent. When that salesperson leaves, the customers leave with the telephone: the contact, the history, the understanding of why this buyer refused the first offer. What remains on your side is a company name and a stale note. This is not a reporting inconvenience, it is the asset walking out of the door, and it is the only reason worth spending money on a tool in the first place.
WeCom is the junction point
The professional version of the messaging app, run by the same company, exists for exactly this problem. An employee's professional account can hold conversations with ordinary users of the consumer app, which means the customer changes nothing: they write where they always write. On your side the account belongs to the company. The contact, the thread and the groups are attached to a seat rather than to a person, and when that person leaves, the seat is handed to someone else as a visible operation instead of an argument about a telephone.
That is the whole of what it changes, and it is a great deal. What it does not do is turn a messaging tool into a management system. It is worth being precise about the line, because the disappointment usually comes from expecting the second thing.
| What you need | What the professional account gives | What stays manual |
|---|---|---|
| A contact that belongs to the company | A customer added to a professional seat stays when the employee goes, and the handover is traceable | Deciding, at the start, that no customer is added on a personal account — afterwards is too late |
| The history of what was said | Threads held through the professional account remain on the company side and travel with the contact | Anything agreed in a voice message, which nobody will listen to twice — the decision has to be rewritten as text somewhere |
| Customer groups | A group created from the professional side can be transferred and survives a departure | The groups that already exist on someone's personal account: those are rebuilt, not moved |
| A record per company, with a stage | Tags, notes and a light pipeline inside the tool, which is enough for a small team | Anything resembling a forecast, a weighted pipeline or consolidated reporting — a connector or a spreadsheet |
| A link to the CRM you already run | A documented interface exists, and integrators sell connectors for the usual tools | Deciding what crosses the border: a name and a telephone number are personal data, and a synchronisation is a transfer |
| Not the channel. A Chinese professional contact answers in the messaging app, not in an inbox | Keeping an address for the contract, the invoice and the formal trace, which is what it is good for |
Where the data sits, and what the customer agreed to
A customer record is personal data, and Chinese law on personal information treats it as such: it rests on an informed consent given for a stated purpose, it gives the person rights over what you hold, and it treats sending that information out of the country as a separate operation with its own conditions. Synchronising Chinese contacts into a CRM hosted in Europe is exactly that operation. It is not forbidden, and it is not a formality either; the applicable route depends on what you transfer, how much of it and why, and the detail has been amended more than once, so the question goes to current text or to counsel rather than to an article.
The practical arrangement that avoids most of the difficulty is to stop trying to hold the same object in two places. Keep the Chinese customer records in China, in the tool the team actually uses, and send home what a head office genuinely needs: volumes, stages, won and lost, by company rather than by person. A consolidated figure is not personal data. A contact list is. The first crosses the border without a file to open; the second is a project of its own, and deciding whether you need it is cheaper than building it and discovering you did not.
The useful minimum for a team of two or three
- One list of accounts, and who owns each one. Which professional seat holds which customer. This single list is what makes a departure survivable, and it fits on one page.
- One record per company, not per person. People move inside Chinese companies more often than the companies move, and a record attached to an individual dies with their job change.
- The date of the last real exchange. Not the date of the last message: the date someone last said something that mattered. It is the only field that tells you which accounts are alive.
- Where the files live. Quotations, drawings, approved samples — in a shared folder on the company side, named so that the next person finds them, and not only in the thread they were sent in.
- A written handover rule. What is transferred when someone leaves, in which order, and who checks that the customer was told. Written before anyone leaves, because afterwards it is a negotiation.
A tool heavier than the business it serves
The other failure is the opposite one, and it is more expensive because it looks like progress. A platform is bought, fields are designed, stages are defined, automated sequences are written, and a dashboard appears that nobody uses to decide anything. The quantity of information a tool asks for has to be smaller than the quantity the activity produces, or the tool measures the discipline of the people filling it rather than the state of the market. A spreadsheet that is maintained is worth more than a platform that is abandoned, and the honest test is whether anyone would notice if it stopped working tomorrow.
Start from the departure, not from the reporting. Write down what you would need, tomorrow morning, if the person who holds your Chinese customers stopped answering: the account list, the current conversations, the files, the agreed prices. Whatever is needed for that is your CRM. Everything else can wait until the first version has been used for a season.