neo4j-migration-skill

Migrate Neo4j driver code and Cypher queries to Cypher 25 syntax.

101|35|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/neo4j-contrib/neo4j-skills --skill neo4j-migration-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neo4j-migration-skill
Source: https://github.com/neo4j-contrib/neo4j-skills/tree/main/neo4j-migration-skill
Command: npx skills add https://github.com/neo4j-contrib/neo4j-skills --skill neo4j-migration-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill solves the problem of broken applications and failing queries when migrating Neo4j driver versions and Cypher syntax across Neo4j releases by providing a structured, version-aware migration checklist.

Core Features & Use Cases

  • Driver API migration across languages: Updates Python, JavaScript/TypeScript, Java, .NET, and Go code for breaking changes in driver v5→v6, including session transaction APIs and package renames.
  • Cypher 25 migration guidance: Translates removed/deprecated Cypher patterns such as id() → elementId(), shortestPath()/allShortestPaths() to Cypher 25 equivalents, PERIODIC COMMIT → CALL {...} IN TRANSACTIONS, and other syntax/compatibility changes.
  • Codebase audit workflow: Scans for embedded queries, dependency manifests, and deprecated patterns, then applies fixes per language and per Neo4j/Cypher target version.

Quick Start

Use the neo4j-migration-skill to migrate a Python and JavaScript codebase from Neo4j 5.x to Neo4j 2026.x with Cypher 25 by asking the Skill to scan your repository for deprecated driver and Cypher usage and produce a diff-ready migration plan.

Frequently Asked Questions about neo4j-migration-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I migrate Cypher queries from Neo4j 5.x to Cypher 25 syntax?

To migrate Cypher queries to Cypher 25 syntax, replace deprecated patterns like id() with elementId(), convert shortestPath() functions, and change PERIODIC COMMIT to CALL {...} IN TRANSACTIONS using guided substitution tables.

What are the driver v6 breaking changes when upgrading Neo4j drivers from v5?

Upgrading Neo4j drivers from v5 to v6 involves navigating breaking changes to session transaction APIs, execute_read modifications, and package renames across supported languages like Python, JavaScript, Java, .NET, and Go.

How do I scan my codebase for deprecated Neo4j driver and Cypher patterns?

Scanning for deprecated Neo4j patterns involves auditing your repository for embedded Cypher strings, external .cypher files, and dependency manifests, then deterministically searching for outdated functions to produce a diff-ready migration plan.

Does the Neo4j migration process support both embedded Cypher strings and external files?

Yes, the Neo4j migration process supports both codebases that embed Cypher strings directly and projects using external .cypher files, applying version-branch rules and fixes per language and target Neo4j version.

Why does id() fail in Cypher 25 and what should I replace it with?

The id() function fails in Cypher 25 because it was removed, requiring you to replace it with elementId() to ensure your Neo4j queries remain compatible with Neo4j 2025.x and 2026.x versions.