Back to all articlesContact identity

Keep a Person's History Intact When They Change Employers

Alactic Editorial10 min read

Prepared with AI assistance by Alactic Editorial. Examples identified as hypothetical are illustrative, not customer results.

A contact tells you they have joined a new employer. Someone edits the company field, replaces the email address, and saves. The record now looks current—but an old meeting may appear to belong to the new company. Creating a second person avoids that overwrite, yet splits the same person's history across two records.

When you update a CRM contact after they change companies, keep the same person identity, close or qualify the former organisational relationship, and add the new affiliation with dated evidence. Preserve past interactions against the organisation involved at the time. Treat current contact details as another change to verify, not as a reason to recreate the person.

The worksheet below provides a practical way to make that update, including when your CRM cannot store a full relationship timeline. The goal is simple: a reader should be able to tell who this person is, where they work now, and which employer each past interaction concerned.

1. Separate the person from their employment

A person record answers who someone is. An affiliation answers how that person relates to an organisation during a particular period. An activity records what happened, when, and in which business context. Those are related facts, but they should not be interchangeable.

Use this distinction when deciding what to change:

  • Person identity: retain the stable record identifier and the history that establishes continuity.
  • Former affiliation: retain the organisation, role, supporting evidence, and known or estimated end date.
  • Current affiliation: record the new organisation and role, with a start date or an explicit statement that the date is unknown.
  • Contact methods: identify which email addresses and telephone numbers are current, historical, or unverified.
  • Past activity: retain the original date, participants, and organisational context.

A current-employer field can be useful for scanning a contact list. It should not be the only surviving record of the person's employment history. Nor should changing it silently redefine the company associated with earlier meetings, messages, or documents.

Some people also hold concurrent roles. A new affiliation does not necessarily mean the previous one ended. Confirm whether the change is a replacement, an additional role, or still uncertain before marking the former relationship as closed.

2. Confirm continuity before making the update

A familiar name and a new company domain are clues, not sufficient evidence by themselves. Before editing, look for a reliable connection between the existing person and the new details. A direct message from the known contact confirming the move is stronger than a matching name on an unfamiliar address.

Record both the evidence and its limits. A message received on a particular date proves when you learned something; it does not necessarily establish the first day of employment. Keep these dates separate:

  • Effective date: when the relationship began or ended, if known.
  • Evidence date: when the supporting statement or interaction occurred.
  • Recorded date: when your team entered the change.

If the person says they started earlier in the month without giving a day, record that uncertainty. Do not turn an approximate statement into an exact date just because a field requires one. Use a supported date-precision field, a clearly labelled note, or a review state rather than presenting an invented date as fact.

If continuity remains uncertain, leave the established history intact and hold the proposed change for review. The safe intermediate state is an unresolved affiliation update—not a confident overwrite or an automatic merge.

3. Use a filled affiliation-change worksheet

Fictional worked example: All names, organisations, identifiers, dates, addresses, and events below are hypothetical. Maya Chen, already recorded as a contact at Cedar Instruments, confirms that she has joined Lumen Systems. The team uses this worksheet before updating her record.

Affiliation-change worksheet — hypothetical completed example

PERSON CONTINUITY
Person: Maya Chen
Existing person reference: PERSON-042
Decision: Retain PERSON-042; do not create another person.
Evidence: Maya replied in an existing conversation and confirmed
her move and new work email.
Evidence date: 18 May 2026
Recorded date: 19 May 2026
Identity review: Continuity supported by the existing conversation.

FORMER ORGANISATIONAL RELATIONSHIP
Organisation: Cedar Instruments
Role: Operations Manager
Relationship start: Unknown; do not infer from first CRM activity.
Relationship end: 30 April 2026, as stated by Maya.
Status: Former employee
Evidence: Direct confirmation received 18 May 2026.

CURRENT ORGANISATIONAL RELATIONSHIP
Organisation: Lumen Systems
Role: Director of Operations
Relationship start: 11 May 2026, as stated by Maya.
Relationship end: Not applicable; current as of confirmation.
Status: Current employee
Evidence: Direct confirmation received 18 May 2026.

PAST INTERACTIONS — RETAIN ORIGINAL CONTEXT
12 February 2026: Requirements meeting with Maya and Cedar team.
Context: Cedar Instruments; Maya participated in her Cedar role.
26 March 2026: Follow-up on Cedar's implementation questions.
Context: Cedar Instruments; do not relink to Lumen Systems.
18 May 2026: Maya's job-change confirmation.
Context: Person-level affiliation update; references both employers.

CURRENT AND HISTORICAL CONTACT DETAILS
Current work email: maya.chen@lumen.example
Evidence: Supplied by Maya in the 18 May confirmation.
Status: Current work address; association confirmed by Maya.
Former work email: maya.chen@cedar.example
Status: Historical; not for new correspondence to Maya.
Mobile: No current number confirmed; leave unverified.
Contact preferences: Retain existing restrictions; do not broaden
permission or assume it transfers to a new address or number.

UPDATE AND CHECK
Keep: Person reference and original activity records.
Change: Current affiliation and preferred current work address.
Preserve: Former affiliation, former address, original context.
Check: Both past interactions still identify Cedar Instruments.
Check: Current summary identifies Lumen Systems.
Unresolved: Former affiliation start date remains unknown.

The worksheet deliberately preserves an unknown start date. The first recorded meeting shows that Maya was acting for Cedar on that date; it does not prove when her employment began. It also treats confirmation of an email's association with Maya separately from technical deliverability or permission to use it for a particular communication.

4. Apply the change without rewriting past activity

Before saving, inspect how the workspace represents organisations on activities. A meeting may have its own company association, or its company label may be drawn from the contact's current employer. Those designs produce different risks when the employer changes.

  1. Capture the starting state. Note the person identifier, former employer, relevant addresses, and the activity references needed for review. Use an authorised record history or a controlled worksheet rather than scattering copies of contact data.
  2. Record the former relationship. Preserve its organisation, role, and dated evidence before replacing any summary field.
  3. Add the current relationship. Enter only confirmed details, leaving unknown dates and roles visibly unresolved.
  4. Update current contact details. Retain the old work address as historical where supported, while removing it from current-use selections.
  5. Inspect past activity. Confirm that the old employer remains explicit wherever it matters.
  6. Record the change itself. Leave a concise explanation of what changed, why, and which evidence supported it.

Do not move an old meeting to the new company simply because the participant now works there. If later work revisits an earlier discussion, create a new activity describing that reference rather than rewriting the earlier event.

A mixed-context interaction needs a clear description. In the hypothetical worksheet, the job-change confirmation concerns the person and both affiliations. Forcing it into a single company context could obscure its purpose. Where the system requires one association, add a concise explanation of the relationship update without duplicating the event as if it happened twice.

5. Adapt the method to your CRM's limits

The strongest structure separates a person record from multiple dated organisational relationships and preserves activity context independently. That is a recommended data design, not an assumption about any particular product.

If your workspace supports only one employer field, use that field for the current affiliation and preserve the former relationship in a consistently labelled history note or other supported structure. Include the former organisation, role, effective dates, evidence dates, and relevant activity references.

This fallback has a cost: notes are harder to filter, compare, and report on than structured relationship records. A note also may not fix a screen that dynamically labels every old activity with the current employer. Test the actual historical view after the update. If it becomes misleading, use supported annotations and raise the limitation with the workspace administrator.

Do not create a second person merely to compensate for a missing history field. That can fragment interactions and contact restrictions. If a system requires separate contact instances for each organisation, document that constraint and use a supported connection between those instances, if available; do not claim that they are independent people.

Check the workspace and current plan for the relevant history, relationship, and review capabilities before adopting a procedure that depends on them.

6. Handle ambiguous moves and contact details explicitly

Not every apparent job move should trigger the same update. Use the evidence to choose the next state:

  • New email, no confirmed move: record the proposed address as unverified. A new domain alone does not establish a new employer.
  • Departure confirmed, destination unknown: close the former relationship if the evidence supports it. Leave the current employer unknown rather than guessing.
  • Two active roles: retain both affiliations. If one must appear in a summary, label the selection rule rather than implying the other ended.
  • Consultant working with a client: distinguish employment from a client relationship. Participation in a client's meeting does not establish employment there.
  • Company name change: investigate whether the organisation itself changed name before treating the event as a person's job move.

Contact details deserve their own review. A telephone number may remain with the person, belong to their former employer, or have an unknown status. Do not classify it as current based solely on its presence in the old record.

Likewise, preserve opt-outs and other contact restrictions during the update. A changed employer or email address is not evidence of fresh permission. This identity-maintenance task should not silently alter communication preferences.

7. Recover carefully from an overwrite or duplicate

If someone has already overwritten the employer, stop further edits long enough to establish what changed. Use available record history and original interactions to reconstruct the former affiliation. Keep confirmed facts separate from reconstruction assumptions.

Restore the former context first: which organisation did the person represent in each affected interaction? Then add the current affiliation. Do not bulk-relabel every old activity from memory. Where context cannot be recovered, mark it as unresolved instead of replacing one unsupported conclusion with another.

If a duplicate person was created, compare the records before any merge. Confirm identity, map each affiliation, review contact methods and restrictions, and identify activity associated with each organisation. A merge can preserve the activities yet still produce a misleading employer history if those distinctions are lost.

Check merge behaviour and recovery options before proceeding. If it is unclear how conflicts or associations will be handled, keep the records flagged for review rather than making an irreversible change. Recovery is complete only when both person continuity and historical context are readable again.

8. Verify the result from three views

Use the completed worksheet as a test, not just as an input form. After an authorised update, inspect three views:

  • Person view: the continuing identity is clear, the current employer is correct, and former employment remains discoverable.
  • Historical activity view: earlier interactions still identify the organisation involved at the time, regardless of the current employer label.
  • Contact-detail view: current details are distinguishable from historical or unverified ones, and existing restrictions remain intact.

For a measurable next action, select one confirmed job change and complete the worksheet before editing. Record how many duplicate person records you found, how many past interactions needed context repair, and how many facts remain unresolved. Repeat those same checks after saving.

The acceptance test is concrete: another staff member should be able to identify the person's current affiliation and explain a past interaction's former-employer context without asking the person who made the update. If they cannot, the record still needs clarification.

Contact identityCRM data qualityAffiliation historyContact maintenance

Put the next conversation to work.

Explore Alactic Communications for WhatsApp conversations, campaigns and AI-assisted workflows. Choose the product and plan that fit your team.

Explore Communications