Odoo 16 Migration Guide

Starting with Bahmni Standard 1.0.0, Odoo 16 is the default version integrated and shipped out of the box with Bahmni Docker. Further details about this initiative can be found here.

Note: The migration to Odoo 16 will differ from a typical backup and restore process. This guide outlines the approach of setting up a fresh Odoo 16 environment and subsequently importing the necessary metadata/master data, along with minimal transactional data such as stock information and outstanding invoices. If your implementation includes additional Odoo modules or customizations, we recommend thoroughly reviewing the features available in Odoo 16 to identify and incorporate relevant modules in the new version.

Preparation for upgrade

Explore and get familiarised with Odoo 16: Before beginning the migration, take time to explore and understand the new features and enhancements in Odoo 16. This includes reviewing the user interface changes, new functionalities, and any updates to existing modules. Familiarising yourself with the new version will help in identifying the benefits and potential impacts on your business processes. Refer this page quickly setup a local environment using docker or you can try out on one of the demo environments.
Understand the data that needs to be imported: Identify the specific data sets that need to be transferred to the new Odoo 16 instance. This includes essential metadata, master data such as customer and vendor information, company information, and key transactional data like stock levels and outstanding invoices. Understanding what data is critical will help in planning the migration process and ensuring data integrity.
Think of a timeline for migration: As Odoo primarily supports billing and accounting operations, it's crucial to plan a timeline for the migration and rollout. This will ensure that reporting and other business functions remain uninterrupted. Careful planning will help in managing the transition to Odoo 16 smoothly, avoiding disruptions in daily operations and maintaining continuity in financial activities.
Prepare additional hardware: To carry out the upgrade, we recommend setting up a test, pre-prod environment to verify the import process, sync with EMR and data validation. This will help migration with minimal downtime.

Basic Configurations in Odoo

Spin up only Odoo and Odoo DB (without starting Odoo connect) with a fresh database by following the steps below:

Update your .env file to use a fresh postgres database:
ODOO_DB_IMAGE_NAME=postgres:16.1

docker compose up -d odoo

Odoo should be accessible at http://localhost:8069 (or) http://<ip>:8069

Before commencing the data migration process, it is advisable to review the additional child pages within the Odoo Modules section to set up the necessary basic configurations for the Odoo system. This process should encompass, at the very least, the following essential items:

Company Information → Company Name, Currency, Round Off Value
Odoo Default Module Level Configurations → Sales Configurations (UoM, Price-lists), Invoicing Configurations (Default Sales, Purchase Tax), Inventory Configurations (Enabling Tracking by Lots, Stock Locations, Warehouses, Payment Methods)
Install any additional modules and configure those if your implementation uses/needs it.

Data Migration

Migration of essential data from your current Odoo implementations can be executed from both OpenERP 7 and Odoo 10. The migration procedure should be conducted in two distinct phases: first transferring the metadata and master data, then proceeding with the import of transactional data.

Phase 1: Masterdata Migration

Automated Migration using Custom Odoo Module

There are two custom modules developed for migrating the following data from OpenERP 7 or Odoo 10 implementations.

Unit of Measure Categories
Unit of Measure
Product Categories
Products
Customers (Patients)
Suppliers

If your current implementation is running on Odoo 10, then take a look at this page.

If your current implementation is running on OpenERP 7, then take a look at this page.

Manual Migration using Excel/CSV based import

Once you have completed the above steps, you can import a few other metadata using CSV-based import.

Stock Location Configuration

Odoo stock locations can be either manually created or can be imported. Create a CSV with the below format and import from Menu -> Inventory -> Configurations -> Locations -> Favorites -> Import Records

name	usage	location_id
Pharmacy	internal	WH

Shop Configuration

Bahmni's custom module introduces a concept known as a "shop," which facilitates the synchronization of quotations to specific stock locations based on Order Location and Order Types for order placed from Bahmni. This functionality can be accessed and utilised by navigating to Menu -> Bahmni -> Bahmni Masters -> Shop and importing the required data using the provided template.

Location	Shop Name	Warehouse
WH/Pharmacy	Pharmacy	My Company

Order Type Shop Configuration

The correlation between Order types and Bahmni Order Location names, along with Odoo shops, is accessible through Menu -> Bahmni -> Bahmni Masters -> Order Type - Shop Mapping. The import template is outlined below.

Order Type	Order Location Name	Shop	Location Name
Drug Order		Pharmacy	WH/Pharmacy
Drug Order	General Ward	IPD Store	WH/IPD Store

Syncable Units Mapping Configuration

The drug orders placed in Bahmni may have different units of measure stored in stock, which will be configured in Odoo. To facilitate the synchronization of quantities, a mapping can be established through Menu -> Bahmni -> Bahmni Masters -> Syncable Units Mapping. The template CSV for the import is provided below.

Bahmni Unit Name	Unit of measure
Unit	Units
Tablet(s)	Unit(s)