Skip to the content
Documentation
Help Start
Reading in:
  • German: 9,059 of 9,059 pages
About the help in other languages
All help pages

FAQ: migration from older systems

Answers to the migration questions public bodies ask - moving from older eZ Publish era sites, from eZ Platform or Ibexa, or from other systems such as WordPress, Drupal or static HTML to Exponential, what is kept, what…

Download as PDF

Address: https://doc.exponential.earth/exphelp/viewer/help/government/faq/migration-faq.md

On this page

FAQ: migration from older systems

This page answers the migration questions public bodies ask when they bring an old website to Exponential. The answers come from the migration chapters of the installation book (chapters 14 to 17) and the migration hub.

Contents

  1. What is the history of the code base?
  2. We run an old 4.x or 5.x site. Can we move to Exponential?
  3. What stays the same, and what changes?
  4. We run eZ Platform or Ibexa. Can we move?
  5. We run WordPress, Drupal or another system. Can we move?
  6. How do we keep old addresses working?
  7. Is there training for a migration team?

What is the history of the code base?

Exponential continues the code base of eZ Publish, which its creator discontinued after almost eighteen years of service (Who is 7x?). 7x carried that code forward to PHP 8 as Exponential 6 (Who is the Exponential Foundation?). Sites built in that era can therefore move to Exponential without changing systems.

We run an old 4.x or 5.x site. Can we move to Exponential?

Yes, and those lines are no longer supported, so you should (SECURITY.md). Chapters 14. Migrating from the 4.x line and 15. Migrating from the 5.x legacy stack take such sites to 6.0; the database is brought up with the update files rather than exported and re-imported (11. Upgrading).

What stays the same, and what changes?

The database schema family, the content datatypes, rich text (ezxmltext), the template language and the extension API stay the same. What changes is mainly PHP 5 to PHP 8 (your own PHP code is the largest piece of work), components installed by Composer, and removed old JavaScript libraries (14.1 What changes, and what does not).

We run eZ Platform or Ibexa. Can we move?

Yes; chapter 16. Migrating from eZ Platform and Ibexa covers it, and 17. Migration reference holds the mapping tables. The Exponential Platform distributions are another route (Exponential Platform).

We run WordPress, Drupal or another system. Can we move?

Yes, with a content migration: guides exist for WordPress, Drupal, Joomla, static HTML and others in the migration hub. Map content types to content classes first (Content model mapping).

How do we keep old addresses working?

With redirects: URL wildcards and custom URL aliases in Exponential, or rules on the web server (Redirects and moved content, URL wildcards). Build the list from the old site before switching.

Is there training for a migration team?

Yes: Migrating to Exponential, 25 lessons, from planning to leaving, with a capstone migration plan. Use the migration checklist for the project.

Become an Exponential Partner

Partners share their information, provide funding, contribute back and develop the products with us, and that is how Exponential grows. A partner website and dashboard are planned for mid-2027: please become a partner today to speed up our growth rate and land new features faster.

Something wrong on this page? Report an error

Documentation license

This documentation is free documentation, licensed under the GNU Free Documentation License 1.3 or later.

Exponential Copyright © 1998-2026 Exponential Foundation and 7x