Migration of Odoo Community and Odoo Enterprise
How to always benefit from the latest features
3 September, 2020 by
Migration of Odoo Community and Odoo Enterprise
manaTec GmbH, Tom Pohling
 

Every year in October, Odoo releases a new version of its ERP system. In addition to the release of complete new modules, Odoo also publishes new features to existing modules. In doing so, Odoo not only benefits from the know-how of its community, but also from the feedback of its customers. With the regular migration of our database to the next higher Odoo version, we ensure that we always benefit from the latest modules and features. But how exactly does the migration work? That's what we're looking at in today's blog.

The migration of our Odoo database to the next generation runs through several process steps.
The migration of our Odoo database to the next generation runs through several process steps.

As soon as our customer has commissioned the Odoo migration, we start with the analysis phase. It is important for us to know which Odoo version our customer uses, which processes are mapped in Odoo and which customizations have been developed or which third-party apps are used. At the same time, we analyze which of these functions can be made available as standard in the next higher Odoo version and thus replaced in the legacy system.

This phase therefore also determines how much effort the migration will demand. The more customizations are available in the legacy system, the higher the migration effort, as these developments have to be adapted to the next higher version.

The next step is to create a backup of the current database. This ensures that our customer can continue working during the migration process and at the same time we have a database with which we can move forward with the migration process. If we have determined in the analysis phase that certain customizations or third-party apps can be replaced by new functions, these are now uninstalled as they are no longer relevant for the further process.

The further course of the migration process now depends on whether our customer works with Odoo-Community or Odoo-Enterprise. However, the basic rule for both models is that we can only start the actual migration once Odoo has released its process to the customer.

Database migration from Odoo Community

So, if our customer is using Odoo-Community, we have to wait for Community to migrate the scripts for the modules that our customer also needs. Then we run the Odoo Community Association (OCA) migration scripts on the database we want to migrate. Alternatively, these migration scripts can also be written by Odoo partners such as us, the manaTec GmbH.

In addition to the database migration of the community version, the customizations are then also adapted to the new version.

The database migration of the Community version is done by Odoo partners like us, the manaTec GmbH.
The database migration of the Community version is done by Odoo partners like us, the manaTec GmbH.

Data base migration of Odoo Enterprise

The main difference to the database migration of Odoo-Community is that the database migration of the Enterprise version is performed by Odoo itself. In doing so, we prepare the database as described at the beginning and send the database to Odoo. There, the database is migrated to the next higher version and sent back to us. At the same time, we work on the migration of the customizations to make them functional for the new Odoo version.

The database migration of the Enterprise version is done by Odoo itself.
The database migration of the Enterprise version is done by Odoo itself.

Following the database migration, we now have the first draft of the new Odoo version, and the test phase follows. We test not only the modules, features and functions within the customer-specific processes, but also the user interface and in particular the various user groups. The results of the tests are documented in detail by us.

If we detect errors within the migrated database, a second iteration of the database migration follows, analogous to the procedure already described. The database of the community version is migrated again by us and the database of the enterprise version is migrated again by Odoo. If we discover errors within the migration of customizations, these will also be corrected by us.

Once the migration of the database and the customizations has been completed without errors, the final migration of the live database is performed. Subsequently, we carry out further extensive tests based on the findings of the first testing. The last step is the final configuration and transfer of the updated database, as well as customizations to our customer by importing them onto the appropriate server. Through extensive workshops and training of our customer's key users, we ensure after the successful migration that our customer uses the new modules or features optimally.

By supporting the Odoo migration, we ensure that our customers always work in the current Odoo version and thus benefit not only from the latest features, but also from minor module adjustments. In this way, we enhance the user experience through the use of the latest technologies and thus drive the growth of our customer companies.

Regardless if you use the community or enterprise version, we support our customers with our experienced team of Odoo specialists throughout the entire migration process, from planning, to execution, to successful completion.

Do you want to migrate your Odoo instance to the next higher version and need professional support? No problem! Check out our online shop right now or contact us now and we will be your reliable partner for your Odoo migration!


Sources: www.odoo.com

 
Software Testing
Quality control in software development projects