I’ve been planning to switch to Payload CMS for a while now. Currently working with WordPress, Craft CMS, and Webflow, but I want to dive deeper into NextJS development. Payload looked like the perfect solution until I heard about the recent acquisition news. I was planning to make Payload our go-to CMS at my development agency, but now I’m having second thoughts. With the IPO plans and Figma Sites launching, I’m concerned they might discontinue the open source project or switch to a commercial license model. I’ve heard similar things happened with other acquisitions in the past. What are your thoughts on this situation? Should I proceed with the migration or look for alternatives?
Honestly, I wouldn’t panic yet. Payload’s team seems committed to keeping the open source version alive, and Figma needs developers on their side. Rushing into another migration right now might be premature - maybe wait a few months to see how things play out?
I went through the same thing when Adobe bought Figma - tons of uncertainty about where things were headed. From what I’ve seen with other acquisitions, companies typically keep open source projects running for 12-18 months before making big changes. Plus Payload has solid community adoption, so switching costs would be huge for existing users. I’d start small - test Payload on a non-critical project instead of making it your agency’s main CMS right away. That way you can check out the tech and see how the acquisition plays out without risking everything. Keep WordPress and Craft as backups while you test it. The NextJS integration benefits might still be worth the acquisition risk depending on what you need.
Switched to Payload 6 months ago and love the developer experience. The acquisition caught me off guard too, but I’m cautiously optimistic for a few reasons. Figma Sites needs a solid CMS backend to compete with Webflow, and Payload’s perfect for that. Plus, killing the open source version would upset the very developer community they need for integrations and adoption. I’m still using Payload but avoiding vendor lock-in where I can. Keeping my content structure portable and documenting everything well so I could migrate later if needed. The NextJS integration’s fantastic, and even if things go south, the productivity boost I’m getting now makes the risk worth it for my projects.