Project Name
Migrating a Poultry and Agribusiness Operation From Microsoft Dynamics NAV 2013 to Odoo 18 Community
Our client is one of India’s largest integrated poultry companies, founded in 1985 in Haryana, with operations spanning broiler and layer breeding, hatcheries, feed milling, poultry processing, grandparent stock, and contract farming across North India and West Africa.
The client has a subsidiary operating in Ghana, running a 500,000 MT per year feed mill at Apedwa in the Eastern Region, a breeder farm, a hatchery capable of producing 4 million chicks per year, and mechanised maize farming. The Ghana operations involve procurement of raw materials, such as maize and soybean, from local and international vendors, poultry feed production, and sales to local farmers under the Lay More feed brand.
Initially, all operations were managed through Microsoft Dynamics NAV 2013, and Ksolves was engaged to migrate and modernise onto Odoo 18 Community Edition.
Every ERP migration comes with its own set of challenges, from managing data and processes to ensuring business continuity.
- Odoo 18 Community Edition Missing Core Accounting Features: Odoo 18 Community Edition does not include full accounting features such as Balance Sheet, Profit and Loss, Trial Balance, and multi-currency accounting. Since the operation handles both USD and GHS transactions, this gap needed to be addressed without moving to a costly Enterprise licence.
- Automated USD to GHS Currency Conversion Required: International procurement is handled in USD, while local transactions are managed in GHS. Daily vendor payments, bank transfers, and financial reporting required an automated and reliable USD-to-GHS conversion process.
- Complex Multi-Warehouse Hierarchy Migration From NAV 2013: The existing NAV 2013 setup included multiple warehouses such as the Main Warehouse, Feed Mill, Breeder Farm, and Hatchery, along with dedicated scrap and egg leakage locations. The challenge was to replicate this structure in Odoo while preserving existing reference codes and workflows.
- User Continuity at Risk During Platform Migration: Changes to field names, workflows, and processes could disrupt daily operations. The migration therefore needed to retain familiar naming conventions and workflows, helping the 6–8 user team transition to Odoo with minimal disruption.
Ksolves, an AI-first Odoo development company, delivered the migration through five structured milestones – Discovery and Analysis, System Setup and Core Implementation, Customisation, Data Migration and Training, and UAT and Go-Live.
- Hybrid Accounting Architecture – Odoo Mates Integration: Ksolves integrated the vetted Odoo Mates accounting module, om_account_accountant, to extend Odoo 18 Community Edition with essential accounting features including Chart of Accounts, Balance Sheet, Profit and Loss, Trial Balance, Aged Partner Balance, tax configuration, and department and branch-level budgets.
- USD to GHS Multi-Currency Resolution: A vetted third-party Community module was integrated to enable USD-to-GHS conversion, multi-currency vendor payments, and bank reconciliation. This eliminated manual currency conversion for international procurement and local transactions.
- Multi-Branch Warehouse Hierarchy Mapped to Odoo Locations: The NAV 2013 warehouse structure was mapped into Odoo, covering the Main Warehouse, Feed Mill, Breeder Farm, and Hatchery while preserving existing reference codes such as AF-034, ALBF-022, and HAT-001. Push and pull routes were also configured for automated Farm-to-Hatchery transfers.
- Custom Batch Consumption Journal for Manufacturing: Ksolves built a custom grid view for manufacturing orders to record actual feed consumption against the BOM in bulk. This replaced Excel-based tracking with a structured, system-integrated process.
- Core Business Flows Implemented End-to-End: Key workflows were configured from CRM and Sales, with credit limits to Purchase, quality checks, weighbridge integration, vendor billing, and Accounting. This replaced manual Excel-based tracking with connected, end-to-end processes.
Technology Stack
| Category | Technology |
|---|---|
| Platform | Odoo 18 Community Edition |
| Accounting Extension | Odoo Mates — om_account_accountant |
| Multi-Currency | Third-Party USD/GHS Currency Module |
| Infrastructure | Client On-Premise AWS Server |
| Modules | CRM · Contacts · Sales · Purchase · Inventory · Manufacturing · Accounting · Dashboards |
The migration transformed a decade-old NAV 2013 setup with Excel-based gaps into a fully operational Odoo 18 Community Edition platform supporting the entire Ghana operation.
- Successful Migration From NAV 2013 With Minimal User Disruption: The migration to Odoo 18 CE preserved key field names and workflows, helping users transition with minimal disruption at go-live.
- Multi-Currency Operations Enabled in Community Edition: USD and GHS transactions are now managed directly in Odoo CE through the integrated third-party module, eliminating the need for an Enterprise upgrade.
- End-to-End Purchase-to-Pay Process Digitised: The purchase-to-pay workflow is now managed in Odoo, from purchase indents and approvals to quality checks, weighbridge integration, and vendor bill deductions, replacing Excel-based tracking.
- Financial Reporting Available Directly in Odoo: Balance Sheet, Profit and Loss, Trial Balance, and Aged Partner Balance reports are now generated directly in Odoo, with department and branch-level budget tracking.
- Multi-Warehouse Hierarchy Preserved With Reference Code Continuity: The NAV 2013 warehouse structure was successfully replicated in Odoo, with existing location codes preserved and automated Farm-to-Hatchery transfers enabled.
The migration from NAV 2013 to Odoo 18 Community Edition gave the Ghana operation a modern ERP platform without compromising its existing workflows, financial requirements, or warehouse structure. Ksolves addressed the Community Edition accounting and multi-currency gaps while preserving critical processes and reference codes. With purchase-to-pay workflows digitised, financial reporting enabled, and custom manufacturing processes integrated into Odoo, the business now has a more connected and maintainable system built around its actual operational needs.
Is Your Agribusiness or Manufacturing Operation Still Running on a Legacy ERP?
