Migration considerations

A migration is a content and recovery project, not just a package upload.

Choose the outcome

Define why the site needs to move and which reader tasks must keep working. Compare a supported upgrade, an extension replacement and a rebuild against the real requirements. This website does not sell migration packages or promise compatibility.

Make the inventory

• Important pages, categories, media and downloadable files.
• Public URLs and the intended redirect or retirement decision.
• Templates, extensions, languages and access rules.
• Forms, stored entries, integrations and their authorized owners.
• Backups, service isolation and the rollback decision.

Rehearse a representative set

Test difficult content as well as the homepage. Exercise restricted and anonymous views, mobile navigation and real image delivery. Compare counts and sample records after transfer, then verify the public routes. Do not move private records merely because a migration tool supports them.

Follow the right official route

The official migration index separates historical upgrade paths. Read the route for your starting version and verify target requirements and vendor support. Do not assume the newest installation archive is a universal update package.

Read the migration planning guide · Assess extension dependencies

Reviewed 4 November 2026. Planning guidance; each installation needs its own technical assessment.