Moving EspoCRM to another server¶

Follow these steps to move EspoCRM to another server.

Step 1. Backup files¶

Open a file manager or login via SSH to archive all available files from the EspoCRM directory. See more details.

Step 2. Backup your database¶

The data stored in the database (MySQL, MariaDB or PostgreSQL) should be backed up. Follow this recommendation.

Step 3. Copy files and database backups to another server¶

Copy the backups of files and your database to a new server.

Step 4. Unarchive backup files¶

To unarchive the backup files, you can use Archive Manager or this instruction. Note: Files need to be placed in the web-server directory.

Step 5. Configure a server¶

Configure a new server based on the recommendations here.

Step 6. Correct permissions¶

Set proper permissions and file ownership, see here.

Step 7. Import your database backup¶

First, you have to create a new database with a user in MySQL/MariaDB/PostgreSQL. To import your database from the backup, follow these instructions.

Step 8. Correct EspoCRM configurations¶

After successfully importing and configuring the server, correct EspoCRM config parameters in the files data/config-internal.php and data/config.php.

Database connection settings:

'database' => [
    'driver' => 'pdo_mysql',
    'dbname' => 'YOUR_DATABASE_NAME',
    'user' => 'YOUR_USER',
    'password' => 'YOUR_DATABASE_PASSWORD',
    'host' => 'localhost',
    'port' => '',
],

Site URL, if your domain name (URL) has changed:

'siteUrl' => 'https://new-link.com',

Default file owner (only if the new web server has a different user/group):

'defaultPermissions' => [
    'user' => 'www-data',
    'group' => 'www-data',
],

where www-data is your web-server user.

Step 9. Setup a crontab¶

Setup a crontab.

Note

it should be configured under your web-server user.

Now, your EspoCRM instance is running on the new server.

Misc¶

MariaDB to MySQL migration¶

When migrating from MariaDB to MySQL, a database dump incompatibility arises. The problem is that MariaDB supports default values for TEXT column but MySQL does not. To solve this problem, you can manually remove default values for text columns in the dump file. Usually, there are not many.