Recommended migration path for tools and integrations following the langchain-community sunset?

Talking Shop
1

Hi everyone,

With the recent official announcement sunsetting the langchain-community package and archiving the repository, I am evaluating how to safely migrate my current production workflows and agent toolsets.

Previously, I relied on langchain-community to manage third-party integrations (such as document loaders, vector stores, and utility tools like DuckDuckGoSearchRun).

Now that the community package is deprecated, what is the recommended architectural pattern moving forward? Specifically:

  1. For Mainstream Integrations: Should we strictly migrate to standalone partner packages (e.g., langchain-openai, langchain-chroma)? Is there a definitive index or mapping available for where all the components moved?

I want to ensure my team builds clean, maintainable, and future-proof agent applications without relying on frozen or archived legacy dependencies. Any guidance, official migration docs, or architectural advice from the maintainers or community would be greatly appreciated!

Thanks in advance.

2

Hello @VaibhavBhinge welcome to langchain community.

Yes. LangChain’s v1 model is one provider = one package (e.g. langchain-openai, langchain-chroma, langchain-tavily, langchain-mongodb). These are independently versioned and are the supported path for models, embeddings, vector stores, and many tools. For production agents, use dedicated partner packages + langchain-core/langchain

Where to find the mapping:

Also please see: Sunsetting `langchain-community` · Issue #674 · langchain-ai/langchain-community · GitHub