Migrating to and from Exponential #

This is the hub for moving a website to Exponential 6, from Exponential 6 to another product of the Exponential family, and away from Exponential to another system. It starts with a table of the Exponential products as they really are published today, then helps you choose a path, and links to one detailed guide per path. Every guide has the same parts: what you can export, how it maps to Exponential's content model, the tools that exist, where you need your own script, URLs and redirects, search engine metadata, testing, cut-over, rollback and a checklist.

Looking for migrations of one site? Schema and content changes written as files under version control and applied to every installation with ./console exp:migration:migrate are a different job: Migrations versus migrating a site, Migrations.

Installation book contents · Start with: The common migration checklist

Contents #

• 1. The Exponential products and their versions (verified)
• 2. Which path fits?
• 3. Migrations within the Exponential family
• 4. Migrations from and to other systems
• 5. Shared references
• 6. How the facts on these pages were checked

1. The Exponential products and their versions (verified) #

Exponential is a family of products maintained by 7x. Their names are similar, and their version numbers do not always say which platform generation they carry, so check this table before you plan anything. Every row was read on 2026-10-18 from the product's GitHub repository under github.com/se7enxweb: the default branch, the branches, the releases (gh release list), the tags, and the composer.json of the default branch or of the release tag named. Where a fact could not be verified it says so.

1.1 The products #

The names you may have heard and what they mean:

1.2 The release lines of Nexus and Platform Legacy #

Read from the composer.json of each release tag:

1.3 What each product has, in the terms of a migration #

The column "Platform" lists what the composer.json files require. Anything not listed there is not part of the product, even where the upstream product it was forked from had it.

2. Which path fits? #

Answer the questions in order; the first "yes" gives your guide.

Rules of thumb that hold for every path:

• Content first, presentation second. Move the content into the target's content model, keep the old site running, and build the new templates against the migrated content on a staging copy.
• One change at a time. Do not change product, PHP version, database engine and design in one cut-over. Move to the closest target first, let it settle, then change the next thing.
• Keep every old address working. A migration that loses addresses loses search ranking and links. Every guide has a URL section; the checklist has the steps.
• Rehearse. Run the whole migration at least twice on copies before the real cut-over, and time it.

3. Migrations within the Exponential family #

4. Migrations from and to other systems #

5. Shared references #

6. How the facts on these pages were checked #

• Exponential products: GitHub repositories of se7enxweb, read on 2026-10-18 (default branch, branches, releases, tags, composer.json of the default branch and of the release tags). Versions move on; check the repository again before you pin one.
• Exponential tools: the source of this repository and of the extensions it requires in composer.json; each tool page names the file it was read from.
• Other systems: the vendors' own public documentation, linked from each guide. Where a vendor's documentation did not confirm a feature, the guide says "not verified" and does not describe it.
• History: eZ Publish was the product this kernel descends from; its creator discontinued it after almost 18 years. The old name appears on these pages only to identify the releases you migrate from.

This page is part of the Exponential documentation and is free documentation under the GNU Free Documentation License 1.3 or any later version (the license of this documentation).