Knowledge Base

Appendix B: Adjusting Web Applications

When you migrate websites with web applications installed, the
applications must be adjusted on the destination server to work
correctly. You can adjust them manually or have Plesk Migrator do it for
you.

Note: Plesk Migrator applies most fixes necessary for web applications to
continue working after migration. However, it cannot cover all
possible cases, especially custom configurations. If your web
application does not work after migration, you need to fix the issue
manually.

During migration, Plesk Migrator automatically adjusts the following web
applications:

WordPress
Joomla!
Drupal (only version 7.x and later)
PrestaShop
Magento
Generic ASP.NET applications that use web.config files (for
example, DotNetNuke)

Plesk Migrator adjusts web applications by:

Changing hostnames or IP addresses of database servers in
applications’ configuration files.
Changing paths inside .html, .php, .aspx files.
(Plesk for Windows) Updating the web.config file (for example, if
the source server had .NET 2 installed, while the destination has
.NET 4).

Here’s what application configuration files are changed by Plesk
Migrator:

Web application	Configuration file
WordPress	`wp-config.php`
Drupal (only version 7.x and later)	`settings.php`
Joomla!	`configuration.php`
PrestaShop	`settings.inc.php`
Magento	(Magento 1) `app/etc/local.xml` (Magento 2) `app/etc/env.php`
Generic ASP.NET application which uses `web.config` files Example: DotNetNuke	Name ends with “`.config`”