Simplify your stack and build anything. Or everything.

Content Management System

Create with a minimal, powerful editing experience. Extend effortlessly.

Enterprise App Builder

Build sophisticated enterprise tools while reducing development costs.

Headless E-commerce

Manage all your content, alongside your products, in a single, powerful editing experience.

Digital Asset Management

Ensure brand consistency by seamlessly managing digital assets within your CMS.

Build tomorrow’s web with a modern solution you truly own.

For Marketing Teams

Advanced features like Visual Editing and Live Preview are giving a head back to the headless CMS.

Learn how Payload delivers for software consultancies with a content framework that can build anything.

Built with React & TypeScript, depart restrictive “no-code” options and write code you’re proud of.

Code-based nature means you can build on top of it to power anything.

Resources

Documentation Examples Templates GitHub

Community

Roadmap Discord Community Help

Payload Cloud

Deploy your entire stack in one place with Payload Cloud.

Login Cloud Pricing

It’s time to take back your content infrastructure.

Schedule a Demo

Enterprise Features

SSO Publishing Workflows Visual Editor AI Translations AI Writing Assistant

Customer Stories

Microsoft Hello Bello Hope Network Tekton My290

Featured Customer Story

Microsoft chose Payload to tell the world about AI.

Read the case study

New project Login

New project Login

Best Practices for DB migrations?

adam-mroziklast year

1 1

Hey,

Do you have some examples/tips/best practices for when we change our collections?
I would assume I could use something like mongoose-migrate, but not sure how to use it with Payload CMS collections

Selected Answer
adam-mroziklast year
OK, found similar topic, please disregard: #857

Continue the discussion in GitHub

Star

Chat on Discord

Discord

online

Can't find what you're looking for?

Get help straight from the Payload team with an Enterprise License.