---
id: KB-ET-019
url: https://app.codecontract.io/help/your-workspace/when-the-company-changes-its-name
idioma: en
categoria: espacio-de-trabajo
subcategoria: cuenta
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-ET-009, KB-ET-018]
citadoPor: [KB-ET-001]
---

# When the company changes its name

_Changing the name takes a minute. What matters is what must not change: everything already issued under the old one._

**Responde a:** we have changed the company name · change of legal name what to update · we were acquired and rebranded · the old logo still shows up

It happens more often than you would think: a change of legal name, a merger, a rebrand, or simply the trading name drifting from the registered one. The visible part is fixed in an afternoon. The part that causes trouble months later is the one nobody looks at.

## What gets updated and what stays as it was

| Element | Does it change? | Why |
| --- | --- | --- |
| The name your team sees | Yes | It is today's name |
| The branding on what goes out from now on | Yes | Anything leaving from now should carry the new one |
| What was already sent and signed | No | It went out that way, and that is the proof of how it went |
| Documents with the old name inside | Not rewritten | Replaced by a new version when the issuer issues one |
| The name on live contracts | It depends | That is a legal question, not a settings one |

> [!IMPORTANT]
> The third row is where the temptation must be resisted: **what was sent under the old name must keep saying the old name**. If a document signed two years ago suddenly showed your current legal name, it would stop matching the copy the other party holds — and evidence that does not match the other side's is not evidence. The history is not a snapshot of what you are called today: it is of what you were called then.

## What is worth reviewing the same day

1. **The sender of outgoing messages** — And the domain, if that changes too: it confuses third parties most.
2. **Templates and whatever the recipient sees** — Texts, signatures and anywhere the name was typed by hand.
3. **Automatic notices** — They usually carry the name inside the text and nobody rereads them.
4. **And whatever appears on your public pages** — It is the first thing someone checking you from outside sees.

> [!WARNING]
> And something worth saying beyond the platform: **your suppliers will keep issuing under the old name for months**. Invoices, certificates and policies will arrive with the old designation until each of them updates their records. It is neither their error nor a gap in your cover, but tell them early — and keep evidence of the change, because it is what explains two correct documents carrying different names.

## If the tax number or the company itself changes

**En corto**

- That is no longer a name change: it is another entity, and usually deserves its own space.
- The previous one's material is kept as it is, because it answers for what it did then.
- And what transfers, and how, is a legal decision rather than a configuration task.

> [!NOTE]
> What a change of name or of company means for live contracts, licences and obligations is for your adviser to determine. **This is only the practical part**: that the new goes out properly and the old stays as it was.

**Can I just change the name and be done?**

For what goes out today, yes. For what is signed, it is not touched.

**What about links I already sent?**

They keep working: what changes is the branding on new material.

**Should I tell my contacts?**

Yes, and early: it saves months of documents in the old name.

## Ejemplos

**A company merges and wants everything to show the new name.**

- Changes branding on outgoing material and leaves what was sent and signed untouched

→ New material goes out right and each old document still matches the other side's copy.

**The company changes name and documents keep the old one.**

- Updates the name on the organisation

→ What goes out carries the right name.

**Old documents carry the previous name.**

- Keeps the old ones as they were

→ The history reflects what it was then.

**A client asks whether it is the same company.**

- Checks the record of the change with its date

→ The continuity is explained.

**Notices go out with the old name.**

- Reviews the templates after the change

→ What a third party receives is coherent.

**The name changes and so does the email domain.**

- Updates the contacts and the allowed domain

→ The team keeps getting in without incidents.