Import an application from another server with Softaculous

A little-known feature of the Softaculous application auto-installer is that it can migrate an application automatically (as long as the app is in the auto-installer's own catalogue) using the source's connection details, provided the installation meets the remote import requirements.

To compare this method with a manual copy or a plugin, see how to migrate WordPress to another hosting.

Softaculous can copy the files and database of a supported application. It does not guarantee that every extension or external setting will be adapted. Prepare an independent backup and an empty destination directory; also check PHP compatibility, space and web access to the source.

Running a migration

The first thing to do is find the application in the Softaculous catalogue, available in cPanel.

Once on the application's page, use the Import option.

Open the page for the same application the source uses; do not start a new installation on top of another website.

Then go to the From Remote Server tab.

Option names may vary depending on the language and version.

You will see a form. The first part asks for the FTP connection details for the remote server. These are basic parameters, domain, FTP server, FTP user... The two that can be confusing are FTP Path and Installation Directory.

If, for example, you have WordPress installed on dominio.com and its internal directory is www, then FTP Path would be /www, and Installation Directory would be left empty, because it is in the root of the account.

But if the app were at dominio.com/blog, FTP Path would still be the same, /www, while Installation Directory would be blog.

FTP Path is relative to what the user sees when connecting. If that user goes straight into the web root, it may be /, even though the absolute path on the server is different. Check the visible content before starting the import and use an encrypted connection if the form and the source support it.

The next step is to say where you want the migrated application to be installed: choose the protocol (always preferably https://), domain and directory.

If you want the app to be moved to the root, dominio.com, leave the directory empty; if you want it at dominio.com/blog, the directory field would be blog.

Choose HTTPS when the destination has a valid certificate. Do not confuse the destination directory with the source's FTP path.

Softaculous will copy the application and its database to the destination you gave. If the domain or directory changes, then check the URL, internal paths and the application's serialised data: the official documentation does not guarantee that every component or extension will rewrite its own values correctly.

When you have checked both ends, click Import. The process continues in the background; follow the task from Task List and do not consider the migration finished until it reaches 100% and shows Import Completed.

What the process moves

The remote import copies the source's files and prepares the database specified for the destination. For this, the source installation must be accessible both with the credentials provided and from the web throughout the process. The internal implementation may change between versions and you do not need to leave any copy script on the source by hand.

When it finishes, check files, the database connection, URL, admin area, forms, scheduled tasks and any external data directory. Softaculous only moves the supported application; it does not copy mailboxes, DNS or other account settings on its own.

Limitations of the process

Because of how the process works, the website being migrated must be working and accessible over the web.

The process can fail if the source blocks the connection, limits execution time, does not allow temporary writes to the installation or the website is not publicly accessible. It may also be unsuitable for very large applications or those with data outside the specified directory.

Check the message in Task List before repeating the operation. Do not raise limits blindly or leave helper processes exposed; if the source does not let the import complete, contact us to assess a manual migration.

The official Softaculous remote import guide describes the fields in detail. After testing, synchronise the latest changes before pointing the domain to the destination, and revoke temporary access.