Roadmap for MongoDB support in Prisma v7

[fredericbahr]

Question

Is there a roadmap planned for when MongoDB is supported with Prisma v7.
Currently updating to Prisma v7 is not possible when using MongoDB.

A roadmap or a rough estimation when this will be supported would be awesome.

How to reproduce (optional)

No response

Expected behavior (optional)

No response

Information about Prisma Schema, Client Queries and Environment (optional)

No response

[aniruddhaadak80]

@fredericbahr Major version releases in the ecosystem often stagger database provider support, especially for connectors that require significant rewrite or have lower usage than SQL providers.

Currently, if you rely on MongoDB, sticking to v6 is the recommended stable path until an official Release Candidate (RC) explicitly mentions MongoDB parity for v7.
You can track the specific v7 milestone or connector/mongodb labels in the repo to see active PRs. Historically, "missing" support in a new major version just means "not ported/verified yet" rather than "dropped".

[fredericbahr]

@aniruddhaadak80 thanks for the answer. I see that there is an (not very transparent) roadmap layed out for MongoDB here: #29296

[nurul3101]

MongoDB Support will come with Prisma Next as mentioned in the issue you linked:

[siamakkarimi]

Hi! I have a project that uses both MongoDB and PostgreSQL with separate Prisma schemas and generated clients.

For now I'm using @prisma/client v6.4.1 for both databases:

• MongoDB → @prisma/client v6.4.1
• PostgreSQL → @prisma/client v6.4.1

The reason is that Prisma ORM v7 does not yet support MongoDB.

My question is: Is this the recommended approach for a production e-commerce application that uses both MongoDB and PostgreSQL?

Or would it be better to use:

• Prisma Client v6.4.1 for MongoDB, and
• Prisma ORM v7 for PostgreSQL

within the same project until MongoDB support is added to v7?

I'd appreciate any recommendations or best practices from the Prisma team. Thanks!