MODX hosting migration mistakes can leave a migration appearing complete while the website still has broken URLs, missing media, login failures, database connection errors, permission errors, or old cached content. These problems often come from differences between the old and new hosting environments, not from the file transfer alone. Before switching DNS, validate both the public website and the MODX Manager in the new environment.
Table of Contents
Why a completed file transfer is not enough
Moving a website involves more than copying its files and database. The hosting environment, management interface, and resource model can be different after the move, so tasks that worked on the old host may behave differently on mybox. This applies when moving from cPanel or Plesk to mybox. See what changes when moving from cPanel to mybox and what changes when moving from Plesk to mybox.
For MODX, check each part of the working site separately. A successful upload does not prove that the database connection, domain settings, permissions, URLs, and cached output all match the new environment.
Check the MODX configuration and database connection
An incorrect configuration can make the site connect to the wrong database, fail to connect, or load data that does not match the transferred files. The database and website files must belong to the same migration state. A mismatch can make a transfer look partial even when both files and a database were copied.
- Open the site on the destination hosting environment before changing DNS.
- Confirm that the front end loads rather than showing a database connection error.
- Open several existing pages and confirm that their content matches the transferred database.
- Open the MODX Manager and confirm that administrator access works.
- Check that changes made in the Manager appear on the destination site when the site is tested there.
If the front end and Manager show different content, stop the DNS change and compare the database and files used by the destination. The migration environment must be checked as a complete set, not as separate uploads.
Review permissions when files or media fail
Permissions are one of the factors that can cause missing images after a migration. Other causes include incomplete website files, database references that do not match the new location, or domain settings that still point elsewhere. In that situation, the website may load while the browser cannot find or use specific assets. The missing images after migration article describes these causes.
Validate permissions through the destination hosting interface and inspect the visible result from the browser. Check the home page, a page with images, and a page that uses other media. A page that loads without its images is not a completed migration.
Test URLs and domain settings before DNS changes
URL problems can affect page links, media references, or access to the Manager. Check both direct page access and links generated by the site. Open the home page, at least one deeper page, and links to media that were present before the move.
- Check that the destination responds for the intended domain.
- Open a deeper page directly instead of reaching it only through the home page.
- Follow internal links and confirm that they lead to the expected pages.
- Open image and media links and confirm that they resolve on the destination.
- Test the Manager address and confirm that the login page opens.
Domain settings are part of the migration, alongside files, database references, and permissions. If the website or its assets still point to the old environment, the transfer can seem successful while visitors receive broken pages or missing media.
Clear stale cache and repeat the tests
Old cached output can make a corrected migration appear broken. It can also make a page show content from before the move. Treat cache clearing as a separate validation step. After clearing the relevant MODX cache through the Manager, reload the front end and repeat the page, URL, media, and login checks.
Compare results after a fresh reload rather than relying on a page that was already open during the migration. Test more than the home page because cached content or references may differ between pages.
Final validation before switching DNS
Use this sequence on the destination environment before the domain is switched:
- Confirm that the expected database content is visible.
- Confirm that the front end loads without database errors.
- Open the home page and deeper pages directly.
- Check internal links, friendly URLs, images, and other media.
- Open the MODX Manager and complete a login test.
- Confirm that permissions allow the site and its assets to work.
- Clear stale cache and repeat the front-end and Manager checks.
- Switch DNS only after these checks pass on the destination.
DNS propagation typically takes a few hours, although it can take longer depending on the domain registrar and network conditions. During that period, some visitors may still reach the previous environment. This is expected behaviour. The destination should still pass the full MODX checklist before the DNS change begins.