What problem does it solve? Moving structured data into Neo4j involves many failure-prone decisions: choosing between online Cypher loads and offline bulk import, handling nulls and type coercion, ordering constraints before indexes, and recovering from mid-import errors. This Skill guides agents through the correct method and syntax for each scenario so imports complete without duplicates, silent data loss, or memory failures. ## Core Features & Use Cases - Method selection: Decision table mapping dataset size, database state, and source format to LOAD CSV, CALL IN TRANSACTIONS, apoc.periodic.iterate, driver batching, or neo4j-admin database import. - Safe Cypher import patterns: Ready-to-use LOAD CSV templates with toIntegerOrNull/toFloatOrNull coercion, nullIf empty-string handling, ON ERROR modes, CONCURRENT TRANSACTIONS, and REPORT STATUS tracking. - Offline bulk load: neo4j-admin import full and incremental workflows with header file formats, ID groups, typed columns, --bad-tolerance, --high-parallel-io, and --schema file support. - Validation workflow: Pre-import checklist (constraints, APOC check, PRIMARY role, UTF-8 encoding) and post-import verification (row counts, index population polling, null-key spot checks). - Use Case: Migrating a relational database to a graph — export tables to CSV, create uniqueness constraints, bulk-load 30M nodes offline with neo4j-admin, then validate counts and bring indexes online. ## Quick Start Ask the agent to import a CSV file of customers into Neo4j with batched transactions and proper null handling, then verify the loaded row counts.