You are reading this section because you are considering migrating your Odoo deployment(s) to Run-odoo. We are recommending you follow the below recommendation and timeline to optimize your migration costs and delays.
¶ Prepare your migration
¶ Odoo Core version and addons
Odoo version: Make sure the Odoo deployment you wish to migrate runs on version 13 or superior. Run-Odoo accepts both the Community and the Enterprise versions.
NB: In case you wish to migrate an older Odoo version (between 8 and 12), please contact our Run-odoo migration team.
Odoo customized and third-party addons: If you have purchased, developed, and integrated specific addons that are not bundled as as standard with the odoo core, make sure you can provide them. Ideally, having them already located in a dedicated GitHub or GitLab branch will be greatly helpful in the deployment of your Odoo instance.
¶ Picking your Odoo workers
¶ You are migrating from a bare-metal or virtualized instance
Look up the number of CPUs of the server/instance / VM you wish to migrate to Run-Odoo and multiply it by 2 to obtain the number of workers you need to subscribe. Then, apply the rules explained in the below example.
Example: You are running your solution on an 8 Core CPU server/VM:
- Calculate 8 X 2 = 16 Workers
- CASE 1: Your previous server had high specs CPUs and/or your deployment was slow in its previous environment, we are recommending applying a 30% boost on the number of workers. In this case, for instance, we would apply the following calculation rule: 16 X 1.3 =20.8. We shall round up this result and obtain a value of 21.
- CASE 2: Your previous deployment was running smoothly and your previous infrastructure had average specs, you can keep 16 as a base of reference.
- Depending on your case, you shall pick an offer proposing more than 16 or 21 workers.
¶ You are migrating from OdooSH
Look up the number of workers you had contracted with OdooSH and apply the following rules:
- CASE 1: Your OdooSH deployment was running smoothly before you migrated it. Keep the number of workers and look for an equivalent number of workers inside the Run-Odoo VALUE or PERFORMANCE packages.
- CASE 2: Your OdooSH deployment was a bit slow or presented slight performance issues. In this case, try to pick a PERFORMANCE offer with the equivalent number of workers.
- CASE 3: Your OdooSH deployment was very slow with major performance issues: Pick a PERFORMANCE OFFER and make sure you are properly assessing the good number of workers. Read the dedicated sections to make the right pick.
¶ Pick the adequate storage
¶ You are migrating from a bare-metal or virtualized instance
You need to collect 2 values:
- Database size: This value is the size of your Odoo database when it runs on your instance. As “psql” user, run the following inside your SSH console:
psql -c 'select t1.datname AS db_name, pg_size_pretty(pg_database_size(t1.datname)) as db_size
from pg_database t1 order by pg_database_size(t1.datname) desc;'
db_name | db_size
-----------+---------
odoo_db | 16 GB
postgres | 8537 kB
template1 | 8409 kB
template0 | 8385 kB
(4 rows)In this case, the database size is 16Gb.
- File storage size: This is the size of the file store where all documents, attachments, and Odoo backend interface fixed assets are located. The location of this file store can be specified inside the odoo configuration file with the “data_dir = /new/path/filestore” setting. If it is not specified, its default location will be the “odoo” user account “~/.local/share/Odoo/filestore/ODOO_DB_NAME” subfolder.
Example: If Odoo is running under 'odoo' user and its home directory is /opt/odoo, then, the filestore location is /opt/odoo/.local/share/Odoo/filestore/your_odoo_db_name
In this case, we will type the following inside the SSH console as user “root”:
root@odoo:/root# du -hs /opt/odoo/.local/share/Odoo/filestore/odoo_db/
6.2G /opt/odoo/.local/share/Odoo/filestore/odoo_db/We can see that the filestore here is 6,2 GB
Therefore here, the total space used by the database and the filestore equals the sum of both values:
Total Odoo space = 16Gb + 6,2 Gb = 22,2 GB
Take this value of 22,2 and multiply it by 2,2. You shall obtain the minimum required space on the Run-Odoo instance as follows:
Total Run-odoo required storage space = 22,2 X 2,2 = 48,84 GB
In this case, you are required to book an instance with a minimum storage size of 48,84 GB
TIP: It is also possible to assess your Total Odoo space by downloading the Odoo backup from the Odoo database manager and proceeding as follows:
- Download your backup from the Odoo database manager.
- Save the compressed archive to your local computer disk
- De-compress the archive inside a folder.
- check the folder size (it should contain both the DB SQL file and the filestore files combined)
- Take this value and multiply it by 2,2. You shall obtain the minimum required space on the Run-Odoo instance.
Retrieve your existing deployment backup with the Odoo Database Manager. You can access it on the following URL:
https://YOURODOOURL/web/database/manager
Pick your Database and click on the BACKUP button. You will be required to input the master password and a name for the archive before they can be downloaded.
¶ You are migrating from OdooSH
Download your backup from the OdooSH interface. You should see a screen similar to the example below:
- Pick the value indicated as “Production Database” size as indicated by the RED arrow in this screenshot.
- Multiply it by 2,2. You shall obtain the minimum required space on the Run-Odoo. In this present case, for instance, we are to multiply 330 X 2 = 660. The minimum space required is 660 GB
¶ Select your Run-odoo offer
If you have followed the above recommendations, you should already know whether you need to pick a VALUE or a PERFORMANCE offer. For more details on these, you can additionally look up their specifics in this dedicated section.
All instance prices for both the VALUE and PERFORMANCE offers are available on the tariff page.
You can follow the procedure to subscribe and set up your instance here.
¶ Migrate your data to the new instance
Once you have completed the subscription of your new Run-odoo instance, you can proceed with the data migration.
¶ Using the Odoo database manager
It is possible to use the Odoo database manager to restore your data into the new Run-odoo instance. Before doing so, you must disable the CloudFlare protection of your instance since CloudFlare blocks any large upload to prevent malicious DDoS and injection attempts.
Use the “TURN OFF CLOUFLARE PROXY” button.
NB: Disabling the CloudFlare Proxy features triggers changes whose propagation can take a few minutes.
You can access the restoration flow by clicking on the “Restore a database” link from the database manager screen. You can access the database manager interface at all times at your standard Odoo URL followed by “/web/database/selector”.
Example: https://yoursubdomain-dev.run-odoo.com/web/database/selector
Master Password: This password is provided inside the activation email. It is necessary at all times to create, backup, restore and delete your Odoo database(s)
File: Browse the backup archive (in Zip format) you wish to restore.
Database Name: Enter the name you wish for this restored database.
NB: This can be a different name from the previous one.
Neutralize: A neutralized database is a non-production database on which several parameters are deactivated. This enables one to carry out tests without the risk of launching specific automated processes that could impact production data (e.g., sending emails to customers). Live access is removed and turned into a testing environment. More details here.
This database is a copy / was moved: This field is important since it determines whether the database you are restoring is being used simultaneously in a different instance. In the case you are restoring an Enterprise version of Odoo, the “is a copy” option implies that a new database ID will be created and shall require another activation. In the case you are selecting the “database was moved” option, the database ID shall remain the same with its activation valid.
Press the “Continue” button once everything has been filled in.
¶ Run-odoo migration team free service
It is possible that the size of the existing data you wish to migrate or the lack of specific Odoo expertise prevents you from achieving the migration process by yourself. In that case, the Run-odoo migration team can be of assistance free of charge.
Before contacting us, please make sure you have the following items ready:
- Your Odoo Core Enterprise or Community version or files if you are using a specific version (modified or legacy core)
- Your Odoo extra addons (if any.)
- Your Odoo backup archive file(s) containing the database dump and the complete filestore.
You can then contact our team to organize the migration.