Case Study
View Case StudyTray.ai
Migrating hundreds of thousands of pages, re-platforming and extending for the leading composable AI integration platform
From Tina CMS to Joomla
We are the Tina CMS to Joomla migration experts
Last verified:
Challenges with Tina CMS
Key pain points
Tina's biggest limitation is that it's fundamentally tied to the React ecosystem. If you want visual editing, you need a React-based framework like Next.js. Basic content editing works with Astro, Hugo, SvelteKit, and others, but the flagship visual experience is React-only. There's been talk of Vue support for years, but nothing has materialised. This is a hard blocker for agencies like us that work across different tech stacks. The platform has also had a notable history: SSW acquired the project in May 2024, and a security breach in late 2024 involved compromised AWS keys via the CI/CD pipeline. These events, combined with the relatively small community, are worth weighing when evaluating Tina for long-term enterprise projects.
On the practical side, developers report frustrating instability in the dev environment. The admin interface can break without any changes to your codebase because it depends on externally loaded assets that update independently. Error handling is weak — forms fail to save silently, and the GraphQL layer doesn't surface errors cleanly. Self-hosting removes the TinaCloud dependency but comes with its own gaps: no search functionality, no Git LFS support, and reference fields can timeout on large collections.
The editing experience, while impressive in demos, can feel fragile in production. Multiple developers have reported losing work in the editor, and features like branch-based editing are locked behind paid tiers. For agencies managing multiple client projects, the React-only constraint and relatively small community (compared to Sanity, Strapi, or Contentful) mean fewer resources, fewer integrations, and more time spent solving problems yourself.
Visual editing limited to React
TinaCMS supports many frameworks including Astro, Hugo, Jekyll, SvelteKit, and Nuxt for basic content editing. However, the visual/inline editing experience, which is Tina's main selling point, only works with React-based frameworks like Next.js.
Unstable development environment
The dev server can break unpredictably because it loads external assets that change independently of your codebase. This makes local development feel unreliable and hard to debug.
Poor error handling and silent failures
Forms can fail to save without any visual indicator, and GraphQL errors aren't surfaced clearly. Losing work without warning is a real risk, especially for content editors.
Branch editing requires paid tier
Multi-branch support isn't available out of the box — it's locked behind the paid editorial workflow feature. You can't test content changes in deploy previews without paying up.
Self-hosting gaps
The self-hosted backend lacks search functionality, Git LFS support, and pagination on reference fields. Large collections can cause network timeouts.
Small ecosystem
Compared to established players like Sanity or Contentful, Tina has a smaller community and fewer plugins. Since the SSW acquisition in May 2024, the project has been actively maintained with regular releases, but the ecosystem is still catching up.
Benefits of Joomla
Key advantages
Trying to convince someone to use Joomla in 2026 feels like recommending Internet Explorer. But hey, if you must use it, there are a few redeeming qualities. Joomla does have some genuinely solid features. Native multilingual support without plugins is impressive. Its permission system is more detailed than most enterprise platforms, and the modular structure gives developers a lot of freedom to architect complex, multi-section sites. If you've got a big team with lots of editors and need granular control, Joomla won't fall apart on you.
If you’re absolutely set on Joomla (and we can’t stop you), we’ll point you toward an agency that still proudly builds 2008-core-web-vital-failing templates. Or you can talk to us, and we’ll at least make sure you don’t regret every step of the journey.
Native multilingual support
Joomla ships with multilingual features baked in, so you don’t need a plugin graveyard just to run a site in five languages. It handles translations cleanly and is genuinely one of the few CMSs that gets this right out of the box.
Granular user permission system
Its ACL system is its biggest bragging right. You can lock down roles, workflows, and access rules with a level of control that most CMS platforms still envy.
Custom field capabilities
Joomla gives you solid flexibility with custom fields, letting you shape structured content without hacking together a dozen extensions. It’s powerful enough for complex layouts and multi-section content.
Active developer community
The community isn’t massive, but the people who are there are dedicated, technical, and still shipping useful extensions and documentation. If you're deep in Joomla land, it’s a lifeline.
Strong security foundation
When properly maintained, Joomla is known for being stable and secure. Regular updates and a security-focused core give it an edge over many older open-source CMS setups.
Modular architecture flexibility
Its module-based layout system lets you build multi-section portals, dashboards, and content-heavy sites without bending the platform backward. If you know what you're doing, it’s flexible enough to scale.
Common questions
Tina CMS to Joomla migration FAQs
Answers to the most common questions about Tina CMS to Joomla migration
How do we migrate content out of Tina CMS?
Tina stores content as markdown and MDX files in your Git repository, which makes extraction the easiest part of any CMS migration we do. Your content is already files on disk. The work is in transforming those markdown files into the structured format your new CMS expects. Rich text blocks, custom components embedded in MDX, and frontmatter fields all need mapping. For a blog or docs site with 100 to 500 pages, we typically complete the migration in 2 to 4 weeks.
Why are teams leaving Tina CMS?
Three issues come up repeatedly. First, the React-only constraint for visual editing blocks teams that want to use Astro, SvelteKit, or other frameworks. Second, the development environment is unstable. The admin interface loads external assets that update independently of your codebase, so it can break without you changing anything. Third, the 2024 security breach involving compromised AWS keys shook confidence in the platform's operational maturity. Teams with enterprise compliance requirements found that hard to overlook.
Is it worth self-hosting Tina instead of migrating away?
Self-hosting removes the TinaCloud dependency, but it introduces its own gaps. There's no search functionality, no Git LFS support, and reference fields timeout on large collections. If you're already frustrated with Tina's instability, self-hosting adds more operational burden rather than solving the root problems. We've found that teams considering self-hosted Tina are usually better served by migrating to a platform with proper managed hosting and a more mature editorial experience.
How much does it cost to migrate from Joomla to a modern CMS?
For a typical Joomla site with 500 to 2,000 pages, expect $15,000 to $60,000 depending on complexity. The content extraction itself is manageable since Joomla uses MySQL, but the real cost is rebuilding custom extensions, templates, and workflows in a modern stack. Most Joomla sites have accumulated years of plugins that need equivalents or replacements. We've found the migration typically pays for itself within 12 months through reduced hosting costs, faster page loads, and eliminated maintenance overhead from outdated PHP dependencies.
How long does a Joomla migration take?
Plan for 6 to 12 weeks for a full migration. Content extraction from Joomla's MySQL database takes a few days. The bulk of the timeline goes toward rebuilding your frontend, replacing extension functionality, and migrating SEO equity (URLs, redirects, metadata). Joomla's version upgrade issues actually work in your favour here. If upgrading between Joomla versions already means a near-rebuild, you might as well migrate to a platform that won't put you through the same pain again in 3 years. We handle the full process including 301 redirect mapping so you don't lose search rankings.
Why are companies finally leaving Joomla?
Performance and developer availability. Joomla sites on shared hosting consistently score poorly on Core Web Vitals, which directly hurts search rankings. Finding developers who still want to work with Joomla's older PHP conventions is getting harder and more expensive every year. The extension ecosystem is shrinking as maintainers move on to other platforms. Companies that delayed migration are now facing a compounding problem where the longer they wait, the fewer resources exist to help them. High cost-per-click on "Joomla migration" search terms tells you everything about how urgently companies want out.
Get in touch
Fill out the form below and we'll get back to you
