Leaving Joomla? What to Export Before You Rebuild

Your Joomla site still brings in enquiries, but updates feel uncertain and the person who built it has moved on. Someone offers to put the pages into WordPress or rebuild everything as a static site. Before choosing either route, you need to know what the current site contains and which parts your business still uses.

The main risk is assuming that moving visible text also moves the working business: forms, document permissions, subscriptions, orders and search addresses. This guide gives you an owner-level inventory and acceptance plan. For other platform decisions, our website upgrade guides cover the costs and trade-offs separately.

1. Decide whether an exit is necessary

An old-looking site is not automatically an obsolete platform. Record the installed Joomla version, PHP version, template and essential extensions. As of 2026, Joomla's technical requirements vary by release; have the maintainer compare your actual version and intended upgrade against the matching documentation, rather than changing PHP blindly.

The reason to stay is strongest when Joomla's editing workflow, permissions and extensions already suit your team. Updating a supported installation may preserve more working behaviour than a platform move. The case against staying is an essential abandoned extension, an editing process nobody can maintain or requirements that no longer fit the current setup.

Joomla's migration self-assessment highlights custom templates, extension compatibility and constantly changing user data as areas requiring care. Those issues matter during a Joomla upgrade as well as a move away from it. Ask for separate options: maintain and upgrade, replace one problematic component, or migrate the entire site.

If the underlying software is unsupported, start with our PHP and CMS version check. An unsupported component deserves a repair plan, but it does not tell you which replacement platform is right. Keep the reason for leaving in one sentence so a redesign preference does not quietly expand the migration scope.

2. Preserve a restorable source before exporting content

Joomla's backup guidance covers both the database and the files. They serve different jobs: the database stores structured records, while files include images, documents, installed software and configuration. Copying the page text or downloading a theme is not a complete backup.

Get owner-controlled access to hosting, the domain, Joomla administration and relevant external services. Use named accounts where possible. Record who can change DNS and who receives password resets, because a successful content export does not prevent a delayed launch caused by inaccessible hosting.

Ask for a dated database export and a matching copy of the site files, then a restore test on an isolated environment. That test should prove the restored copy can load representative pages and that its administration works. Disable outgoing mail, scheduled jobs and payment actions on the copy before testing; a rehearsal must not contact customers or process real transactions.

Store backups in a protected location outside the public website, with access limited to the people doing the work. Configuration and database files can contain credentials or personal records. Agree a retention and deletion plan instead of sending an unrestricted archive around by email.

A hosting snapshot is convenient, but its limitation is retention and portability. Check how long it survives, whether it covers the database, and whether you can retrieve it independently. Keep a separate copy when you need the ability to recover after switching hosts.

3. Map content and functions as separate workstreams

There is no universal “Joomla export” that proves every feature will work on another platform. An importer can understand articles yet miss an extension's custom tables. Treat each item below as a requirement with an owner and a test.

For a small brochure site, carefully copying reviewed content may be cheaper than adapting an importer. The case against manual transfer is the risk of omissions across many pages. Automated transfer becomes useful when repeatable mappings save work, but its results still need inspection.

Before purchasing a migration tool, check documented support for your exact source version, destination and required data. Run a sample containing a normal article, a document download, a custom-field page and an extension-driven page. Confirm images and links survive, rather than judging only whether the article count looks plausible.

Customer accounts deserve a separate plan. Password formats and permissions may not transfer directly, so agree whether resets are required and how you will communicate them. A store also needs stock, tax, payment and order-history checks. Do not treat an active shop as a brochure migration with extra pages.

4. Choose a destination your team can maintain

Keeping Joomla is a valid option when the supported platform still meets the brief. Its limitation is the ongoing need to maintain the software and verify extension compatibility. Replacing the CMS purely because a vendor prefers another one can create avoidable retraining and data-conversion work.

WordPress can suit teams that want a familiar editing interface and available integrations. Its case against is that a new plugin stack creates its own update and compatibility obligations. Choose it for a demonstrated workflow, rather than the assumption that changing the name of the CMS removes maintenance.

A static site can suit a small public information site with infrequent edits and no account system. Its limitation is the editing and deployment workflow, plus the separate handling of forms or other dynamic functions. Our WordPress and static-site comparison helps weigh those practical requirements.

The Simply Jems Joomla rebuild is a relevant recorded example, but its store was retired, not migrated. It demonstrates a smaller scope and a static publishing workflow; it does not demonstrate moving active customer accounts or checkout.

For planning, a small content-site inventory typically takes 1-3 working days, and migration typically takes 2-8 weeks with a CAD 2,000-10,000 allowance. These editorial ranges assume a modest site and bounded functionality. Commerce, memberships, custom integrations and extensive content cleanup require a separate estimate. Compare quotes against the inventory, rather than page count alone.

5. Make launch and rollback acceptance conditions

The new site is ready when it preserves the required customer journeys and data, rather than when the homepage looks finished. Keep a written acceptance list and name the person responsible for each check.

1. Inventory public URLs from navigation, available search reports and a crawl if you have one. Choose a destination for each retained page; follow the redirect checklist for changed addresses.
2. Protect staging from public access and indexing, then test representative pages, downloads and permission boundaries. Record the temporary protection so launch checks remove it intentionally.
3. Verify contact and newsletter delivery, mobile layouts, keyboard navigation and essential integrations. Test using designated accounts and clearly marked messages.
4. Agree a content freeze or final synchronisation plan. For changing orders or user records, specify how updates after the first export reach the replacement and how they will be reconciled.
5. Take a final backup, confirm who controls DNS, and document how to restore the old site. If the replacement accepts new transactions, rollback also needs a plan for those new records.
6. After cutover, check key URLs, redirects, public access, sitemap output and enquiry delivery again. Monitor recorded errors and customer reports during the first days of operation.

Keep the old environment privately available for the agreed recovery period. Do not leave it as a second public site or delete it merely because DNS has changed. Close the migration when the agreed checks pass and the team can make its routine edits without outside rescue.

— Editorial team. Facts current as of 2026; we revise guides when the ground shifts.