A Sales Contact Changes Employer: Update the Relationship Without Rewriting History
A contact tells you they have joined another company. Changing the company name on their CRM record may look like a quick update. It can also leave a colleague reading old proposals as if they belonged to the new employer.
Treat the change as a relationship transition. Preserve the context of past work, check who now owns the current discussion at the former employer and establish what you actually know about the contact's new role.
Confirm the change before using it
A direct message from the contact and an observed public profile update provide different kinds of information. Record the source and when you learned it. If the exact transition date is unknown, leave it unknown rather than treating your observation date as the employment start date.
Check whether the person is still involved in an existing assignment during the transition. Their departure does not establish who replaces them, whether the project continues or whether another colleague has already taken over the relationship.
This article proposes an operational worksheet. It does not set a legal retention period or decide which personal information your organisation should keep.
Split the transition into three questions
In this fictional example, Morgan tells a consultancy that they have moved from Eastbank to River House. Morgan had participated in a process-review discussion at Eastbank.
| Question | What is known | What remains to do |
|---|---|---|
| What happened at Eastbank? | Morgan took part in the original review discussion | Keep that history attached to its original context |
| Who handles Eastbank's current decision? | Morgan says a colleague will take over | Confirm the agreed handover route |
| Is there a River House opportunity? | Morgan has a new role there | No business need or new opportunity established |
The third row is easy to skip. A familiar person at another company is a relationship fact. A new opportunity needs a relevant task or decision of its own.
Keep old work readable
Before editing a live record, inspect how your system connects people, companies, opportunities and conversations. A company change may affect what appears in different views. Test with fictional data if the behaviour is unclear.
The intended result is simple: an old Eastbank proposal remains recognisably an Eastbank proposal, and Morgan's current affiliation does not change who took part at the time. Your CRM might represent this through dated relationships, separate records or another method. Confirm the actual options before choosing one.
Avoid creating a second record without an explicit reason and a way to recognise the relationship between the records. Equally, avoid merging them merely to reduce the contact count. The decision depends on preserving useful context in the system you use.
Review the work that still points to the contact
Look at open tasks, meeting plans and any scheduled communication related to the old role. Decide which remain appropriate and who should handle them. Check for a message that would refer to Morgan as if they still worked at Eastbank.
For the fictional consultancy, the next action is to confirm the handover Morgan offered. It is not to guess a replacement and start a parallel approach. If another colleague already manages Eastbank, coordinate with them first.
Keep the old employer's confidential discussions within their appropriate context. Familiarity with Morgan does not make those details relevant material for a conversation at River House.
Open a new business discussion only when there is one
If Morgan later asks about a River House project, record that request separately: the task, the company concerned, what Morgan is asking for and the agreed next action. Do not copy the old employer's budget, needs or stage into the new discussion.
A brief transition note can close the administrative work: source checked, current affiliation recorded, old history inspected, open actions reviewed and account handover assigned. List any unresolved point with its owner.
When considering Konekt CRM, try this fictional employer-change scenario before updating a live relationship. Check that a colleague can understand both the earlier work and the current affiliation. Confirm how your chosen setup preserves those contexts.