How to migrate data from my free account to enterprise account?

Support
1

Hey everyone, a few months ago, I signed up for a free account, and later on, I also registered for an Enterprise Plan account.

Now, I have a question: how can I migrate the data from my free account to the index of my Enterprise Plan account?

Thanks in advance!

2

Hi @chatofai

there is no quick or “easy” way to migrate the data from one project to another. If your free index isn’t too full I would just run the original embedding creation again. A similar issue is discussed here:

Also it is good practice to save the ids created (if you can) into a separate database or file just in case you need to do some operation on all of them at once.

eg. I once had to update one metadata field of all my vectors. If I didn’t have my ids there would be little I could do.

Hope this helps

3

I had this problem before as well. This was when the starter tier had namespaces available, so if you dont have that your milage may vary.

I made an Open-source tool called VectorAdmin that can handle this for you provided your free account has namespace support. No-namespace stuff is still tricky but its on the roadmap.

You can connect the free index, and sync the data to the tool. Then connect the new enterprise index and migrate all the data from free to enterprise in a single click. No issue and done in a few seconds. There are a bunch of other tools, but that one would be the most useful for you given the issue that I also suffered with.

No changes required to your data either - it’ll work with whatever is already in the index.

3 Likes
5

Hey Jasper, thanks for your reply!

We’ve already sorted out the data migration issue. Here’s what we did:
Using the vector_id(obtained from the response when calling the save function in the Pinecone API) stored in our system, we were able to “fetch” the data (including values, metadata, etc.) from the original Pinecone index and then “upsert” it into the new Pinecone index.

6

Hey Tim, thanks for your reply!

We’ve already sorted out the data migration issue. Here’s what we did:
Using the vector_id stored in our system, we were able to “fetch” the data (including values, metadata, etc.) from the original Pinecone index and then “upsert” it into the new Pinecone index.

1 Like
7

It’s not working, getting this error:

{
  "message": "Job failed with error",
  "error": "Cannot read properties of null (reading 'describeIndexStats1')",
  "details": {}
}