Setting the file. One moment.
Chapter 06 · Prisma MongoDB Upgrade
Subchapter 6.5
references/verify-cutover-checklist.mdMarkdown3 KBView on GitHub
Verification checklist for a v6 → Prisma Next cutover: the data never moves — only the code does.
CRITICAL
A v6 → Next migration is a client and workflow migration against the same MongoDB database — there is no data export/import step, and introducing one (or pointing the new stack at a fresh database) turns a code migration into an outage. The checklist below keeps the cutover observable and reversible.
mongodb@^7
driver rejects — validate the URL with the driver first).mongodb-memory-server), emit
the contract, run plan → migrate → verify → sign, and confirm verify passes against
data copied from production shape. Verification failures here are contract-mapping bugs,
not database problems.db.collection.getIndexes())
and confirm the Next contract declares the same set — v6 db push may have created
indexes the new contract must re-declare, or verification and query performance will
diverge.$jsonSchema validators by default;
confirm legacy documents (extra fields, drifted shapes) pass them on the staging copy
before applying to production.db.orm.users), not model names (see schema-contract-mapping.md).$transaction; each hit gets a
driver-session equivalent (the mongodb driver is directly available; the façade wrapper
is expected soon — see client-api-mapping.md).$runCommandRaw / findRaw / aggregateRaw call
has an explicit Next-side replacement (mongoRaw(...) lane or pipeline builder).After cutover, install and follow Prisma Next’s own skills for ongoing work (see the
hand-off rule in SKILL.md).
a2791c5dd59d579b4b3052942ae7f8fe5e2ee852