migrate-from-pinecone

Migrate Pinecone vector indexes and metadata to Elasticsearch with bulk indexing.

6|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/patrykkopycinski/elastic-cursor-plugin --skill migrate-from-pinecone
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: migrate-from-pinecone
Source: https://github.com/patrykkopycinski/elastic-cursor-plugin/tree/main/.cursor/skills/migrate-from-pinecone
Command: npx skills add https://github.com/patrykkopycinski/elastic-cursor-plugin --skill migrate-from-pinecone

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This workflow helps teams move vector indexes and associated metadata from Pinecone into Elasticsearch to consolidate search infrastructure, reduce vendor lock-in, and enable unified observability and kNN queries.

Core Features & Use Cases

  • Index provisioning: Create an Elasticsearch index with a dense_vector field that matches the Pinecone dimensions and any metadata fields used for filtering.
  • Bulk data migration: Export vectors and metadata from Pinecone, map them to Elasticsearch document shape, and perform efficient bulk indexing.
  • Integration & validation: Replace Pinecone query calls with Elasticsearch kNN searches, optionally use an ingest pipeline for server-side embedding, and validate results by comparing top-k outputs.
  • Use Case: Move a semantic search index from Pinecone to Elasticsearch for tighter integration with observability and existing data pipelines.

Quick Start

Use the migrate-from-pinecone skill to transfer vectors and metadata from my Pinecone index named 'docs' into a new Elasticsearch index with matching vector dimensions.

Frequently Asked Questions about migrate-from-pinecone

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

FAQPage Schema
How do I migrate vectors from Pinecone to Elasticsearch?

Migrate Pinecone vectors to Elasticsearch by creating a dense_vector mapping, exporting vectors and metadata, and bulk indexing them into the new index. This process replaces Pinecone kNN queries with Elasticsearch kNN searches for unified search infrastructure.

What is the best way to replace Pinecone kNN queries with Elasticsearch?

Replace Pinecone kNN queries by provisioning an Elasticsearch index with a dense_vector field matching Pinecone dimensions, then performing bulk indexing of exported vectors and validating top-k outputs against the original results.

Does Elasticsearch support dense_vector fields for Pinecone migrations?

Yes, Elasticsearch supports dense_vector fields. You must create an index mapping that matches your Pinecone vector dimensions and metadata fields to successfully migrate and perform kNN search on your vector data.

Can I use an ingest pipeline for server-side embeddings during a Pinecone migration?

Yes, you can optionally configure an Elasticsearch ingest pipeline for server-side embeddings during the bulk indexing process. This allows you to compute embeddings directly while migrating vectors and metadata from Pinecone.

How do I validate vector search results after moving from Pinecone to Elasticsearch?

Validate vector search results by comparing the top-k outputs from your new Elasticsearch kNN queries against the original Pinecone results. This ensures your dense_vector mapping and bulk data migration retained index accuracy.