In this article (5)
We decided to migrate our Keltawebagency to a proprietary CMS that we saw built by our colleagues, and it's amazing (in a good way). Why is that?
A migration from Joomla to a proprietary CMS should also be assessed through what the site carries with it: addresses, content, modules and the habits of whoever updates it. Our Kelta Web Agency website offers a concrete example to start from. On the public pages, references to the Joomla ecosystem coexist with a presentation of KeideaCMS. Reading these elements correctly helps distinguish a platform choice from the results that still need to be proven.
The short answer: a reference to Joomla in the code and a mention of another CMS are not enough to certify a completed migration. Deciding whether to switch platforms requires an inventory of features, clear maintenance responsibilities and evidence of how the site actually works. The same criteria apply when the site in question belongs to a web agency.
What our website shows
In the check of public pages on 26 October 2026 we found the path /templates/ja_morgan/favicon.ico and a link to the sitemap with the parameter option=com_jmap. In the News section there are also CSS resources under /media/com_jchoptimize/. These are references traceable to the Joomla ecosystem: they indicate technical elements to be recorded, but they alone do not describe everything that runs on the server.
On the homepage we also present KeideaCMS as a platform that centralizes infrastructure, updates and support. This is a commercial proposal visible to the reader. On its own, it is not proof of the platform that serves every page of the domain.
For a company evaluating a redesign, this distinction has a practical consequence: a demonstration of the new interface does not replace a report of the work actually carried out. It is necessary to know which content has been transferred, which functions have been rebuilt and which elements still depend on the previous environment.
The starting point is the website's legacy
Our menu includes service pages, contacts and a news section. These are paths with different purposes. A service page must help evaluate an offer; a news item can keep receiving visits long after publication; the contact page must get a request to whoever handles it.
Transferring only the text leaves these responsibilities open. To assess a move to another CMS, I would therefore start from three questions about the existing site:
- Which paths must keep working? Service pages, articles, images and documents have addresses that may already be shared.
- Which functions depend on specific components? An extension should be described by what it does for the business, before looking for a replacement.
- Who uses the panel, and to do what? Publishing a news item, updating a service and managing a request may require different permissions and steps.
This is the kind of analysis to request before approving a quote: a list of functions to be kept makes proposals comparable, while the CMS label alone leaves room for interpretation.
Switching to a proprietary CMS changes responsibilities
The possible advantage of a managed platform is concentrating in the provider activities that would otherwise need to be coordinated among several parties. This advantage should be translated into verifiable commitments: who updates the software, who checks for incompatibilities, who checks the backups and who steps in when a module stops delivering requests.
Maintenance continues to exist. What changes is who carries it out and how they are accountable to the client. For security, moreover, the distinction between open and proprietary software is not enough: what matters is updates, access management, configuration and recovery capability.
When evaluating an offer, I would ask to see a complete publication in the panel and an example of content export. I would also ask how customizations are handled: a function available today must have a maintenance path when the product changes. A fee can look understandable on paper and still leave the excluded interventions undefined.
Addresses are part of the delivery
A legacy path or a parameter in the link are not sufficient reasons to change a URL. If the page retains its function and content, keeping the address can avoid an additional step. When the address does change, a relevant destination must be identified.
Google Search Central, in the guide How to move your site, updated in 2026, recommends mapping old URLs to new ones, using permanent server-side redirects and updating internal links. It also warns that ranking fluctuations can occur during the move.
For our website, as for a client's, I would ask for a readable check: previous address, destination and content found. An HTTP 200 code, which signals a successful response, would not be enough: opening a page different from the one expected would still be an error for the visitor. This check concerns continuity of service, without promising a position in search results.
When to consider KeideaCMS and when to keep Joomla
A Joomla site with functions suited to the business, sustainable maintenance and an available technical lead may have good reasons to stay on its own platform. A migration introduces work and risks: rebuilding functions, training and checking transferred data should all be part of the decision.
A managed platform, on the other hand, deserves consideration when the company wants to entrust infrastructure and updates to a defined point of contact, provided the necessary functions are available and the exit conditions are clear. Before choosing, I would ask which data can be exported, in what format, at what cost, and which parts of the project would need to be rebuilt elsewhere.
Kelta Web Agency and KeideaCMS belong to the same ownership. To learn more about the offer, the direct comparison with Joomla is available: it is a page from the provider, to be considered alongside a check of your own site and explicit contractual terms.
Before authorising the switch, ask for a concrete deliverable: included features, responsibilities, planned tests and exit procedures. These are the elements on which you can decide whether the new CMS will really simplify your company's work.