Odoo 13 Migration – Why and How to Migrate to Odoo 13

Who needs to migrate to Odoo 13?

As a matter of fact, anyone can migrate to Odoo 13 irrespective of whether you are already using Odoo or not.

More specifically, if you are using Odoo version 10 or lower, then it’s high time that you migrated to Odoo 13.

While Odoo 10 was based on python 2.7, Odoo 13 is built upon python 3.6 and higher keeping in terms with the advancements in the software.

‘Out with the old and in with the new’

 If you are using Odoo 11 or 12, you would still need to consider moving to Odoo 13 because of a couple of reasons. Rich UI, Better Features and Performance Optimizations, to name a few.

Moreover, Odoo 13 is highly optimized for the user especially in terms of inventory and stock management. The Multi-table dependencies of many fields have been reduced to ease the working load.

Consequently, it offers better trackability of various operations.

The reporting and analysis matrix has been greatly enhanced through improvements in module dashboards and, the introduction of clear graphs and tables.

Considering to migrate to Odoo 13 isn’t so bad after all irrespective of where you are coming from….

Once you decide to migrate to Odoo 13… Next is How!

What are the Different scenarios Of Odoo 13 Migration?

Typically, there are three cases that need to be considered:-

• Moving From a Different Platform to Odoo

Most of the clients wish to move from a different platform to Odoo because it offers a ready-to-go solution to their business.

In this type of request, we do a GAP analysis to assess which of the features present in the client’s platform are already available in Odoo. Next, we sought the absent features in the already designed Webkul odoo modules.

At last, the remaining features are customized for the client in the new Odoo.

• Server migration without changing the version.

In this, the client just wants to move his Odoo from one server to another. This step includes moving data while keeping the Odoo version the same.

• Upgrading To New Version i.e. Odoo 13.

Since the topic in hand is upgrading your Odoo version. We will discuss the details about the parameters and process of Odoo 13 migration in the following sections.

Different Migration Types?

Once you have decided to upgrade your version Odoo 13, there are two possibilities:

• Static Migration
• Dynamic Migration

Static Migration

This type of migration to Odoo 13 would involve moving the static data. In simple terms, the type of data that does not depend on other data. For example customers, catalog data – products, attributes, categories; etc.

Static migration requires architecture design in Odoo 13 to make the data compatible with the client’s current version. This type of migration is used when one wants to have a clean slate in their migrated Odoo version.

Dynamic Migration

This process entails moving both static and dynamic data to Odoo 13. Dynamic data includes data involving relation fields like invoices, orders, bills, accounting, inventory data, etc.

This is a little trickier than the former process. One also needs to consider the flow of data in the Odoo.

Different Parameters To Account for Before Migrating?

1.) Existing Odoo Version

This step is important as the efforts would depend upon how different is the present Odoo version of the client from Odoo 13.

It is self-evident from the fact that the UI and code of Odoo have undergone dramatic changes with time.

So if you are at Odoo 10 or lower versions, a lot of features might have been replaced or removed from subsequent versions. So they all would need to be adjusted as per your data.

Also, the Postgres version of your Odoo is needed to design the architecture for the new version for the client.

2.) Size of current DB

The size of data in your current Odoo version determines the efforts and path to be undertaken for Odoo 13 migration.

3.) Server information of the client

Whether the server on which Odoo 13 will run is a self-hosted server or a cloud-hosted server such as AWS.

In the case of a cloud-hosted server, you can provide us with your AWS credentials. Or we can suggest the best configuration according to the requirements. Contact Us Now.

4.) Estimated Downtime

Although it is kept to a minimum, downtime is inevitable when the data is added to a new Odoo version. The same is true while migrating to Odoo 13.

This depends upon the type of migration and along with other factors.

What Are the Different stages Of Odoo 13 Migration?

Once the analysis is done from our team the plan is drawn adumbrating the process to migrate your DB to Odoo 13.

To avoid interruptions the entire process is first done in QC DB (test DB) and then moved to the original DB of the client.

This helps with the testing and timely rectification of errors beforehand, and to minimize downtime.

Though the exact process varies on a client-to-client basis, the general process that is followed is as follows:

1.) Modules Migration

The first step is to migrate all your modules to Odoo 13. There are three types of modules

• Core modules

These are default modules that Odoo provides innately such as sales, inventory, e-commerce, etc.

Some modules have been removed or changed with the later versions. So this step needs analysis to check compatibility with the migrating version to know the efforts.

• Webkul Modules

These modules are presented by us and are almost present for Odoo 13 version. But sometimes may need customization as per individual needs.

• 3rd Party Modules

These include the core modules which have been customized and/or the modules purchased from any other 3rd party. We need to study these modules to see if they or similar are present in Odoo 13. If not, then they need to be designed from scratch requiring more effort.

2.) Data migration

Next comes data migration, the type – static or dynamic depending upon the client. We first put the data in test DB to run tests and quality checks. It is then transferred to the client’s DB.

3.) Testing

There are two types of testing procedures:

• Smoke Testing

This is a mandate. Smoke testing involves checking UI and architecture to remove any errors from the user’s point of view.

• Scenario testing

This is a situation-based testing process done on the client’s request. It involves sketching various scenarios and situations to test the code compatibility in the DB. Subsequent measures are implemented to rectify the errors.

4.) Quality check in Developer DB

Quality checks ensure that the flow of data is properly oriented in Odoo 13. The quality team checks that the correct data is pulled in the new DB for every operation. So, no irrelevant fields are present in the views.

This is to say that everything is in its correct place.

5.) Moving Everything To Client’s Odoo 13 DB

Once the migration is successfully completed on QC DB and quality checks get the green signal, the migration is transferred to the real live DB.

The client DB may face downtime during this step, which is kept as short as possible.

Once done, the DB is successfully migrated to Odoo 13.

Important points before moving to Odoo 13 migration

Data Backup

A backup dump is always created at our end to restore and prevent data. Backup is necessary to roll back the changes if needed.

Security Measures

Adhering to the GDPR compliance, we do not store any client data at our end.

Get the best possible advice Regarding Odoo Migration

Are you in a dilemma about whether to migrate to Odoo 13 or not? It can be a mammoth task to map it all out on your own. So, you can hire Odoo developers to solve your dilemma related to migration and ease the Odoo 13 migration job.

If you have any queries or issues regarding Odoo 13 migration, please raise your queries to our dedicated team of 100+ developers.

We are here to provide the optimal solution to your ERP needs.

You can send your queries to our support team at support@webkul.com