Hi everyone,
I’m in the process of rebuilding a website currently based on TYPO3 with over 10,000 entries in a MySQL database. These entries include articles, legal rulings, tips, news items, and event documentation, some of which are managed using the TYPO3 news module, if anyone is familiar with it. All of this content will need to be ported over to the new system. There will also be several user roles to manage different parts of the website. The content is mostly in one language, but some parts may be translated in the future.
Given the scale and variety of the content, I’m wondering which database would be the most suitable for this project with Payload CMS: MongoDB, PostgreSQL, or SQLite? I’m particularly interested in performance, scalability, and ease of migration. Any insights or experiences would be greatly appreciated!
Thanks in advance!
#Best Database for Migrating 10,000+ Entries from TYPO3 to Payload CMS?
1 messages · Page 1 of 1 (latest)
Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:
Documentation:
Hey @cinder geyser,
Oh dear lord typo3...
I think at ~10k entries the database isn't really the concern - any of them will work well out of the box at that scale as long as you're not doing something unusual. But then again that's entirely up to your orchestration. I've used both mongodb and postgres in client projects and it's been pretty smooth sailing on my end. I think you should think about your data models - Payload makes it easy to forget that each database has their own use-case in practice.
Haven't worked much with SQLite in Payload at least, so I will reserve my thoughts on that front.
Dear @still drift, thanks for the quick feedback! Since I primarily come from a frontend background, I'm still a bit unsure how to make the final decision for this project. Considering that the current system uses MySQL, I assume migrating to PostgreSQL might be simpler, but I'm open to try MongoDB if it offers significant benefits. Any more advice how to flip the coin?
I think you'd be correct in that a migration from MySQL to Postgres would be easier since you could use something like pgLoader to help. Let me see if I can find a guide online.
See this guide from DigitalOcean: https://www.digitalocean.com/community/tutorials/how-to-migrate-mysql-database-to-postgres-using-pgloader#step-5-migrating-the-data