---
title: REMOVE
url: https://nexyron.tech/docs/cypher/clauses/writing/remove
description: Remove labels or properties while keeping the entity.
---

# REMOVE

## Generic Description

Remove labels or properties while keeping the entity.

Simple example:

```cypher
MATCH (p:Person) REMOVE p.legacy_field
```

## Consumer-Level Explanation

Use `REMOVE` when the query must remove labels or properties while keeping the entity and the planner needs to see that operation as part of the Cypher row pipeline. Keep the clause explicit because it controls row grain, variable scope, and what later clauses are allowed to reference.

## More Detailed Explanation

REMOVE is the clean-up companion to SET. It is useful when the entity should survive but obsolete or incorrect annotations should not.

What this clause is really for:

-   it defines one concrete stage in the Cypher row pipeline, so variables available before and after `REMOVE` must be clear
-   it should make graph structure, temporal filters, document payload shaping, or procedure output explicit instead of relying on client-side interpretation
-   planner tooling depends on this clause boundary to know row grain, variable scope, and whether later expressions are reads, writes, schema operations, or projections

## Advanced Example

This example keeps `REMOVE` inside a complete query pipeline so the clause boundary, visible variables, and returned row shape are clear to planner tooling.

```cypher
UNWIND [{user_id: 'u-1', doc_id: 'd-1', ts: '2025-01-02T10:00:00Z', payload: {kind: 'view'}, doc_metadata: {kind: 'report'}, embedding: [0.22, 0.18, 0.44]}] AS evt
MERGE (u:User {user_id: evt.user_id})
MERGE (d:Document {doc_id: evt.doc_id})
CREATE (u)-[e:VIEWED]->(d)
SET e.ts = toDateTime(evt.ts),
    e.payload = evt.payload,
    d.metadata = evt.doc_metadata,
    d.embedding = vector(evt.embedding)
WITH u, d, e, date_trunc('day', e.ts) AS day_bucket
RETURN u.user_id, d.doc_id, day_bucket, keys(properties(d)) AS doc_keys
```

## Real Use Cases

-   schema cleanup
-   removing transient processing markers
-   migrating off legacy fields

## Real Limitations And Tradeoffs

-   removing a field can affect downstream assumptions immediately
-   mass REMOVE operations still require careful scoping
-   label removal can change query reachability in surprising ways