How to migrate data from Odoo version 13 to 15?

Odoo is rapidly evolving, with new features that improve performance. The nature of the current and target Odoo versions, installed apps, the breadth of customising Odoo, data volume, and requirements for new modules may, in certain situations, cause an Odoo upgrade to be delayed.

Upgrading Odoo 15 is not a simple operation, but it is required to keep your business up to date with the newest features and security patches. It is a good idea to upgrade your customised instance to ensure that everything is working properly. If you skipped an Odoo version and wish to update to the newest version, use the checklist below.

Here is a list of things to look for before upgrading:

Make certain that your critical data is kept in a secure location.

You should execute the migrations if you have a large amount of customised data that is not yet on a migration path. If you wish to execute a migration before upgrading, you need enable the migration path in Odoo v.13's instance menu's "Modules" menu.

1. Run the migration, which will save your data in the "_MODULE MIGRATION DATE_" tables.

2. Your data will be in the same table in both versions, making the upgrade considerably easier.

3. In Odoo v.13, go to the "Reports" menu to view the migration path. If you see a "Migration path" item, it signifies that the migration path is active.

4. If you have essential data in your custom code that is not in any migration path, you must carefully review that code before upgrading.

5. For example, if you have a report written in code, ensure that it will still work in the updated version.

Examine custom modules

Your modules must be compatible with the new version when you update. But how can you know which modules to examine? You're good to go if you have a list of custom modules that you know you'll require. However, if you want to test all of your modules, a simple script may be used.

1. Navigate to the console ("/console") on your Odoo instance and choose "Scripts." You will be presented with a list of Python programmes that you may utilise. Select "find custom modules" and then "Run on all."

2. This script will locate all of your installed modules and display their versions in the console.

3. If you see any red "Incompatibilities" in the list, you know you need to determine which modules are incompatible and change them before upgrading.

Contrast your existing database structure with the new one.

1. Before updating, compare your customised database schema to the new structure and make any required modifications.

2. If you customised your tables and columns, check the "Migration path" report to determine if your modifications are included in the migration path.

3. If your modifications are not in the migration route, ensure that they will not create any issues after the update. If you have added more tables, ensure sure they are no longer required following the upgrade.

4. If you've introduced more columns to the primary tables, make sure they're not being utilised by any core or other modules.

5. If your adjustments generate difficulties, you should devise a plan for dealing with them. You can maintain them in a different database or set of tables, or you can alter the new tables to accommodate your changes.

Use the Odoo 13 to 15 data migration tool to migrate your data.

If you have previously configured your database schema in v.13, you should run the Odoo v.13-to-v.15 data conversion tool on v.13.

1. The data migration tool assists you in populating the new tables with the necessary data, as well as filling the tables with any existing data found in the "_MODULE MIGRATION DATE_" tables.

2. To use the migration tool, navigate to your Odoo v.13 instance's "Admin" menu and select "Tools." There, pick "Database" and then "Upgrade to 15."

3. If you don't have an Odoo v.13 instance, you may run the migration tool in a "sandbox" instance on your PC.

Manual involvement is necessary for database changes during the Odoo 13 to 15 upgrade.

If you altered your database structure (new or removed tables and/or columns) or added more data to your tables after the update, you may need to make the adjustments manually.

1. The "Migration route" report will show you what has changed in the database.

2. It is advisable to document any changes and devise a strategy for dealing with them.

3. You should also document what modifications you made to the database and where you added data.

4. Remove any data that has been added to fields that are not used by any core or other modules before upgrading.

Examine the Odoo update procedure.

You may test the updating process if you have a test environment. A "sandbox" instance can also be used (an Odoo instance that you can create and destroy easily). If you have a lot of specialised data, you should probably employ a test environment. If you only need a few more users, a "sandbox" instance should suffice.

Conclusion

Check your modifications, data, and database structure to ensure they are still compatible with the latest version. Then, before updating, you may test the update process, compare your current database schema to the new one, and make any necessary adjustments.

Technical updates to an existing Odoo version may be considered by the user, either through in-house assistance or through partners. Migrating to the latest version may be a time-consuming and error-prone operation due to a lack of Odoo update expertise. Our consultants are available to discuss your current situation, perform analysis, recommend optimal migrating approaches, and assist you in taking advantage of the most recent release.