A TYPO3 website can be moved to a new hosting provider without downtime through a staged migration. Keep the current website available while you prepare and test the new hosting environment. Switch the domain only after the new copy is ready. Website migration requires technical knowledge, but the person or team managing the transfer can complete the work. Learn more about the technical knowledge needed for migration.
Table of Contents
Plan the migration before changing the live website
Start by listing every part of the TYPO3 installation that must move. Include the website files, database, Composer dependencies, TYPO3 configuration, extensions, environment variables, scheduled tasks, caches, domain settings, and email-related settings.
Migration affects more than the visible page files. A TYPO3 project may depend on Composer packages, extension code, configuration files, environment-specific values, and database content. Treat these as separate migration items and record how each one is transferred to the new provider.
Prepare a rollback plan before the DNS change. The existing hosting environment should remain available until the new website has passed testing. If the new environment has a problem after the domain switch, the rollback plan defines which domain settings and hosting environment should be restored.
Build a separate TYPO3 staging copy
- Prepare the new hosting environment. Create the destination environment without changing the live domain. Use a temporary hostname or another isolated address for testing.
- Transfer the TYPO3 files. Copy the project files and the web-accessible files required by the installation. Keep the existing site online during this step.
- Transfer the database. Import a copy of the current TYPO3 database into the new environment. The database and files must represent the same point in time as closely as possible.
- Install Composer dependencies. Rebuild the project dependencies in the new environment using the project’s Composer definition and lock information. Confirm that the installed packages match the project requirements.
- Move the configuration. Transfer the TYPO3 configuration that is common to all environments, then set the new provider’s environment variables and connection values. Check database access, file paths, domain values, and other settings that differ between hosting environments.
- Set up extensions. Confirm that the required TYPO3 extensions are present and that their configuration is available in the new environment. Test extension features that affect forms, searches, authentication, content output, or integrations.
Test the new TYPO3 environment before the DNS cutover
Test the staging copy through its temporary address before directing the public domain to it. Check the homepage, key page types, navigation, images, downloads, forms, search, login areas, and extension-driven features used by the website.
Review the TYPO3 backend as well as the public site. Confirm that editors can access the backend, content can be opened and saved, and the database contains the expected records. Check the environment variables again if a feature works in one environment but not another.
Scheduled tasks also need a deliberate setup. List the tasks used by the TYPO3 project, configure their equivalent execution on the new provider, and confirm that they do not run twice during the transition. Keep the old scheduled tasks under review until the new environment becomes active.
Rebuild caches and check generated content
Clear and rebuild TYPO3 caches in the new environment before the domain switch. Then open important pages as a visitor and review the generated output. This helps reveal problems caused by stale configuration, missing dependencies, incomplete files, or extension settings.
Do not treat a successful homepage load as a complete test. Check several content types and functions so that cached pages, uncached pages, backend actions, and scheduled processes are all considered.
Prepare the domain and email settings
Review the domain settings before the cutover. Confirm which records direct web traffic to the new provider and identify the records used for email. Web hosting and a domain are separate services: the domain is the address that points to the hosting environment, while hosting stores and serves the website.
Keep email settings unchanged unless the email service is also moving. If email is moving, prepare the required mail settings at the same time and test mailbox delivery separately from website access. A web migration should not unintentionally change the service that receives mail for the domain.
Switch the domain with a rollback plan
- Complete the staging tests and confirm that the new TYPO3 copy is ready.
- Record the current domain settings so they can be restored if needed.
- Change the web-related domain settings to point to the new hosting environment.
- Keep the old hosting environment available while the change spreads.
- Monitor both the new website and the domain during the transition.
DNS propagation typically takes a few hours, although it can take longer depending on the domain registrar and network conditions. During this period, some visitors may still reach the old environment while others reach the new one. This is expected behaviour, so avoid making different content changes on the two environments during the cutover. Careful preparation helps reduce downtime during a server migration.
Verify the live TYPO3 website after the move
After the domain begins resolving to the new provider, repeat the critical checks on the live domain. Review public pages, forms, search, login areas, media files, backend access, extension features, and scheduled tasks. Rebuild caches again if the domain change or environment values require it.
Check redirects and important URLs after the switch. Existing URLs should continue to lead to the intended content. If a URL structure changed during the migration, configure the required redirects and test both the old and new addresses.
Also verify email delivery, domain resolution, database writes, file uploads, and any external service connected to the TYPO3 website. Keep the previous hosting environment available until these checks are complete and the rollback window has ended.
Migration and search engine visibility
Moving a website to a new server does not usually harm its search engine ranking. The migration still needs careful preparation and post-migration checks, especially for domain settings, redirects, and continued access to the website. Read more about server moves and search engine ranking.
When to involve technical support
Ask for technical help when the TYPO3 project cannot be rebuilt, the database cannot be connected, an extension fails, scheduled tasks do not run, the domain does not reach the new environment after propagation, or the rollback needs to be performed. Provide the migration time, the affected domain, the failing function, and whether the issue affects the old environment, the new environment, or both.